We are in the final stages of upgrading our render farm to Max2012 and Deadline 5.0. We are getting the following errors when we try to submit a job:
failed to find the file [regionManipulator.ms] in deadline repository. (error code: 1040)
failed to find the file [TileManipulator.ms] in deadline repository. (error code: 1042)
failed to find the file [submitMaxToDeadline_functions.ms] in deadline repository. (error code: 1004)
– runtime error: FileStream cannon creat: C\program Files\Thinkbox\deadline\bin\temp_TempDate.txt
– runtime error: FileStream cannon creat: C\program Files\Thinkbox\deadline\bin\logs\submitmaxtodeadline
We have checked the installed repository and it looks good. We have also made sure the permissions are set correctly on the repository folder. Any advice would be appreciated, thanks.
Out of curiosity, have you applied the Max 2012 Hot Fix before running with Deadline 5? There were some severe bugs in the original Max 2012 (specifically MAXScript) that made it impossible to support until the Hot Fix release last week…
Looking at the code, the error messages you are seeing would indicate that the script file was actually not found in the Repository. There is a more general error message worded “Failed To Load the file…” which would appear if an actual error happened within a try()catch() block expression. So it sounds like the Network path was not resolved correctly, but I could be wrong. If you ARE running Max 2012 with Hot Fix applied, I would like to help you debug the issue if you have time. This might require minor tweaks to the Deadline-SubmitMaxToDeadline.mcr script in order to print out the results of the Network Path resolution function to make sure SMTD is actually looking in the right folders.
Also, can you tell me what Operating System you are running?
We do not have the hot fix installed. The OS is win 7 on the slaves and Win Server 2008 for the repository. I think we will start there and see if that resolves the issue. Thanks for your quick response.
Hmm, the file locking issue should only affect Max 2012, so this must be a different issue…
Can you open a command prompt on your machine and run this command:
deadlinecommand.exe -getrepositoryroot
If you get an error that deadlinecommand.exe isn’t recognized, try reinstalling the Deadline Client software. If it prints out nothing, then use the Deadline Launcher to choose the shared path to your Deadline Repository root. If all of this is already set up properly, let us know and we’ll go from there.
I looked through the source code of the script and what you should be trying to run from the command line to check what is going on is:
deadlinecommand.exe -GetCurrentUserHomeDirectory
It appears that the result of this call on your machine is empty string “” and this produces an incomplete path “temp_tempDate.txt” which of course cannot be created because it does not exist relatively to the current directory.
Please run the above and tell us whether it returns a valid path or not.
On my Win7 machine, I get
When you ran the “deadlinecommand.exe -getrepositoryroot” and “deadlinecommand.exe -GetCurrentUserHomeDirectory” commands, how long did they take to run? They should only take 1-2 seconds each, so if they are taking significantly longer than that, that could explain the problem.
A few people have run into this “slowness” problem in the past, and each time the solution was to ensure that their Windows installation was fully updated.
Just to confirm, was running “deadlinecommand.exe -getrepositoryroot” and “deadlinecommand.exe -GetCurrentUserHomeDirectory” pretty fast, or did they take more than 10 seconds each to finish? I just want to confirm if that’s the problem or not before thinking of other things to try.
We run “deadlinecommand.exe -getrepositoryroot” and "deadlinecommand.exe -GetCurrentUserHomeDirectory"Response time More than ten seconds.
What is the problem or have a solution?
Thanks for confirming. Now we know what to focus on.
So your Windows 7 installation has all Windows updates applied, correct? If so, the only other thing I can think of is to try running the .NET 2.0 SP2 installer: microsoft.com/downloads/en/d … laylang=en
I really can’t think of what else to try. This issue has always been solved in the past by either upgrading .NET 2.0 or by applying all windows updates. Since you’ve tried both of those without any success, I’m not sure what else to do.
I guess we could start by gathering more info. Does this problem occur on all of your machines, or is it just one or two? I’m asking because if you have a “working” machine, perhaps you can use that to re-image the machine you’re having problems with. Sometimes that’s easier than trying to figure out what the actual problem is.