Hello,
I downloaded Deadline 3.0 SP1 from your website and set it up in free mode according to the instructions. I consistently get the Access Denied Error no matter what I do. The initial set up was 2 machines running Vista x64 with the repository on a NAS. No domain controller or anything. I gave the “Everyone” account permission to the NAS, as well as the Max and Deadline folders. When I got the access denied error, I tried several fixes including submitting it via 3dsCmd instead of Max, have the Salve, Launcher and the Max processes run as Admin etc. Nothing worked. I even installed everything on a single clean Vista x64 machine hoping it would work - no luck there either. I am logged in as a local Admin on all machines.
I hope there is some way to figure this out. I have spent the last three days on this issue 
.
Thanks!
Bob
Error Message
Exception during render: An error occurred in RenderTasks(): Failed to assign process “c:\Program Files\Autodesk\3ds Max 2009\3dsmaxcmd.exe” to job object: Access is denied.
(System.Exception) (Deadline.Plugins.RenderPluginException)
at Deadline.Plugins.ScriptPlugin.RenderTasks(Int32 startFrame, Int32 endFrame, String& outMessage)
Slave Log
regex “.Rendering -.”
0: INFO: Ignoring popup windows with titles matching regex “.Maxwell Translation Window.”
0: INFO: Handling popup windows with titles matching regex “.Microsoft Visual C++ Runtime Library.” by pressing “OK”
0: INFO: Handling popup windows with titles matching regex “.V-Ray warning.” by pressing “OK”
0: INFO: About: 3dsCmd Plugin for Deadline
0: Plugin rendering frame(s): 0
0: INFO: Stdout Handling Enabled: True
0: INFO: Popup Handling Enabled: True
0: INFO: Using Process Tree: True
0: INFO: Hiding DOS Window: True
0: INFO: Creating New Console: False
WARNING: an error occured while trying read stdout from the process: Cannot access a closed file. (System.ObjectDisposedException)
WARNING: an error occured while trying read stdout from the process: Cannot access a closed file. (System.ObjectDisposedException)
0: INFO: Enforcing 64 bit build of Max
0: INFO: Render Executable: “c:\Program Files\Autodesk\3ds Max 2009\3dsmaxcmd.exe”
0: INFO: Rendering to network drive
0: INFO: Render Argument: ““C:\ProgramData\Frantic Films\Deadline\slave\jobsData\deadline test 2009.max” -v:4 -start:0 -end:0 -w:640 -h:480 -pixelAspect:1.0 -atmospherics:true -renderHidden:false -effects:true -useAreaLights:false -displacements:true -force2Sided:false -videoColorCheck:false -superBlack:false -renderFields:false -skipRenderedFrames:false -outputName:”\192.168.1.100\remote\Renders\Output\a.jpg" -gammaCorrection:false -continueOnError -rfw:true -videopostJob:false"
0: INFO: Startup Directory: “c:\Program Files\Autodesk\3ds Max 2009”
Scheduler Thread - Render Thread 0 threw an error:
Scheduler Thread - Exception during render: An error occurred in RenderTasks(): Failed to assign process “c:\Program Files\Autodesk\3ds Max 2009\3dsmaxcmd.exe” to job object: Access is denied.
(System.Exception) (Deadline.Plugins.RenderPluginException)
at Deadline.Plugins.ScriptPlugin.RenderTasks(Int32 startFrame, Int32 endFrame, String& outMessage)
Error Type
RenderPluginException
Error Stack Trace
at Deadline.Plugins.Plugin.RenderTask(Int32 startFrame, Int32 endFrame)
at Deadline.Slaves.SlaveRenderThread.RenderCurrentTask()
Have you tried disabling UAC (User Account Control)? That has been known to help. We’re currently looking into a solution for this problem.
Cheers,
Hi,
Disabling UAC is not an option for us. Is there another workaround we could try? Such as permissions or running processes under another account? When do you expect to have a solution to the issue? Will the new 3.1 fix this?
Thanks.
Bob.
I’m not having the best of luck reproducing this. We have a Vista 32 and a Vista 64 test machine, and I’ve only seen this problem once on the Vista 64 machine, and a restart of the machine fixed the problem. We’ve tested with network and local admins and normal users, and with UAC on. Firewall is disabled because we use our own anti-virus software. We’re really not sure why it works fine for some people and not others, and the inconsistency of this problem really makes it difficult to diagnose and solve. We would love to get have this problem completely resolved for 3.1, but until we can reproduce it consistently, it’s difficult to give a time line.
The fact that you’re running as local admin makes the fact that this problem is happening really strange, as back when Deadline 2.7 was experiencing this problem, this was the only known workaround.
We’ll keep digging, but if you can think of anything else to send our way, let us know!
Ok, I’ve made some more progress, and I think it is UAC related, so we will probably have to make some changes to make the slave UAC compliant.
I have figured out how to reproduce the problem. I get the error in the following situations:
- If I start the slave from the Start Menu
- If I start the slave from the Launcher, and the Launcher was originally started from the Start menu
- If I start the slave by double-clicking on the deadlineslave.exe file in the Deadline bin folder
I don’t get the error in the following situations:
- If I start the slave from the command line (the Deadline bin folder is in the path, so I just have to type ‘deadlineslave’ and hit Enter)
- If I start the slave from the Launcher, and the Launcher was originally started from the command line
- If I start the slave from the Launcher, and the Launcher was originally started up when Windows started up (a startup process) - this would explain why a restart often fixed the problem
So the current workaround is to run the slave from the command line, or run the launcher from the command line and start the slave through the launcher. I’ll post more when I have more information.
Ok, I think we’ve been able to find a solution for this problem. We can now run the slave from the start menu as a normal user with UAC enabled without any problems. This fix will be included in the 3.1 release.
Cheers,
Wow, thanks for digging in on this. Outstanding customer service! Launching deadlineslave from the command line works! Cant wait to evaluate the rest of it. Thanks again Ryan!
Bob
Hi, same sort of issues here on Windows 7 x64.
I’m retiring my v2.7 setup and adding a new PC to a new v3.1 setup. I have two slaves (Win7x64 and WinXPsp3) and a third PC running the repository.
When I try to submit jobs on the Win7 system nothing works (AECS4, MAX, Submit to QT). In QT the job is submitted but fails. In MAX and AE the submit scripts fail.
If I shut off UAC then everything works okay. I have tried elevating all the programs to run as Admin but still no go. I did try the GUEST USER account suggestion, to no avail.
I have included a few log files of what is happening when I submit a QT job.
Thanks for your help.
-David
logs.rar (4.44 KB)
Hi David,
The errors in each log are actually unrelated, but both will be resolved in Deadline 4.0. We were finally able to trace the “failed to assign process” error back to Windows’ Program Compatibility Assistant (PCA), which means this message actually has nothing to do with user permissions. We think that in some cases, disabling UAC also disables PCA, which is why that works sometimes. When running the Deadline applications from the command line, it skips PCA entirely. Deadline 4.0 should be available before the end of the year, so hopefully one of the current workarounds (disabling UAC or launching apps from the command line) get you by for now.
The “error purging” message shouldn’t actually affect your renders, as Deadline is just purging the temp directory, but regardless, this feature will actually be removed from 4.0, since it may not always be desirable to purge the temp folder of a machine.
Cheers,
Thanks Ryan,
So if I get this right, I should launch the Launcher from a command line instead of having it load on boot?
-David
I’m having the same problem, however even launching from the command line doesn’t work (I have win 7 64bit , UAC disabled, running an administrator account).
Hmm, that’s strange. Launching the slave from the command line has always worked in previous cases. How are you launching the slave? Are you running “deadlineslave.exe”, or are you doing “deadlinelauncher.exe -slave”? The former should work fine, but the latter won’t work if there is already a launcher running on the machine.
That being said, the problem should be fixed in Deadline 4.0, so maybe consider checking out the beta to see if your problem persists:
viewtopic.php?f=10&t=2778
Cheers,