I am hoping to get some help on some strange, and annoying errors we have been getting since we updated to Deadline 8, from the old 5.2
We are gettings failed jobs on a daily basis with the error “Error: Timed out waiting for the next progress update.” , and we cannot find any info why. A resubmit solves the issue, and the job starts rendering just fine.
We have a number of slaves connected to the ques, all with the same setup.
Our jobs are being submitted to the que by the 3d-artist
attached is the info from 1 failed job just now, that worked just fine after i re-submitted it.
i have had 3 of them in under 15 mins now, and they are all working just fine again. They did fail on different QUE´s, so it should not be related to that.
I think I’ve remembered the root cause of this issue (logged somewhere in a dark place in my head). I think you need to startup 3ds Max on each of your rendernodes (which are typically also used as workstations with this given error) using “Admin” rights at least once and ensure these exceptions are in place on each machine if the Windows firewall is enabled: docs.thinkboxsoftware.com/produc … iderations
IIRC, this error message is due to file/directory permissions as well:
Make sure the user starting up 3ds Max via Deadline Slave is a “Power User” or higher. Alternatively, check file/dir permissions on anything under:
and make sure the user has access to these files.
Finally, try purging any “cached” thumbnail files from under: “C:\Program Files\Autodesk\3ds Max 2014\CachedThumbnails” as it could be a bad cache file somewhere.
ok, you have been able to successfully resolve your first issues! Now, for some more!
You must always run exactly the same version of 3ds Max on all your machines. Undesired render results will most likely happen otherwise. See here in your log this warning:
2017-04-19 13:19:27: 0: INFO: Slave 3dsmax.exe version: 16.5.277.0
2017-04-19 13:19:27: 0: INFO: Slave 3dsmax.exe description: 3ds Max 2014 + servicepack_sp5
2017-04-19 13:19:27: 0: INFO: Submitted from 3dsmax.exe version: 16.6.556.0
2017-04-19 13:19:27: 0: WARNING: Slave’s 3dsmax version is NOT the same as the 3dsmax version that was used to submit this job! Unexpected results may occur!
So, your Slave is on 2014 SP5, but you are submitting from a workstation running a newer version of 2014 SP6. Most likely this is the root cause of your issues.
Yea, the different version was news for me also? We push out our applications via a management utility, so the only way that there should be diffent versions is if the user have installed it manually. As this person had done when i checked with him
Thanks for the headsup, we are looking into to Deadline 9, but are not really ready to take the step yet. Will most likely start with updating to SP17.
I have tried to change the setting to kill autodesk comms center.
Huge thanks for the assistance ! Highly appreciated!
We have added the local admin user as a user with full access in the folder C:\Program Files\Autodesk\
UAC is not a valid option for us, because our IT dep resets the level from the domain top. But the added user seams to work.
That i suppose have sorted out the permission error.
Network team have verified that all is good in fw , and we start the app in admin mode once when it´s installed.
We have enable the setting to kill autodesk cooms center.
We have been running for 48 hours without any fails, coming from having several per day, this seams like a really really good way forward.
