We have a block of rendernodes which always fail their first attempt at running 3ds max renders:

[quote]
[/Error: The 3dsmax command line renderer, C:\Program Files\Autodesk\3ds Max 2016\3dsmaxcmd.exe, hung during the verification of the 3ds max install
at Deadline.Plugins.ScriptPlugin.StartJob(Job job, String& outMessage, AbortLevel& abortLevel)quote]

[code]/=======================================================
Error

Error: The 3dsmax command line renderer, C:\Program Files\Autodesk\3ds Max 2016\3dsmaxcmd.exe, hung during the verification of the 3ds max install
at Deadline.Plugins.ScriptPlugin.StartJob(Job job, String& outMessage, AbortLevel& abortLevel)

=======================================================
Type

RenderPluginException

=======================================================
Stack Trace

at Deadline.Plugins.Plugin.StartJob(Job job)
at Deadline.Slaves.SlaveRenderThread.a(TaskLogWriter A_0)

=======================================================
Log

2015-06-25 09:41:46: BEGIN - #################
2015-06-25 09:41:46: 0: Loaded plugin 3dsmax (\#####\deadlinerepository7\plugins\3dsmax)
2015-06-25 09:41:46: 0: Start Job timeout is disabled.
2015-06-25 09:41:46: 0: Task timeout is disabled.
2015-06-25 09:41:46: 0: Loaded job: #######PRVS#####_B08.03 (558b542fb5b7e16424e44bc1)
2015-06-25 09:41:46: 0: Skipping drive mapping because they have already been mapped for this job
2015-06-25 09:41:46: 0: INFO: Executing plugin script C:\Users#######\AppData\Local\Thinkbox\Deadline7\slave\Render-i7-08\plugins\558b542fb5b7e16424e44bc1\3dsmax.py
2015-06-25 09:41:46: 0: INFO: Slave Running as Service: True
2015-06-25 09:41:46: 0: INFO: About: 3dsmax Plugin for Deadline
2015-06-25 09:41:46: 0: INFO: The job’s environment will be merged with the current environment before rendering
2015-06-25 09:41:46: 0: INFO: Start Job called - starting up 3dsmax plugin
2015-06-25 09:41:46: 0: INFO: Sys Env Var PATH: C:\Program Files (x86)\Common Files\Intel\Shared Libraries\redist\intel64\compiler;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files\Common Files\Autodesk Shared;C:\Program Files (x86)\QuickTime\QTSystem;C:\Program Files (x86)\Autodesk\Backburner
2015-06-25 09:41:46: 0: INFO: Sys Env Var PATH length: 316
2015-06-25 09:41:46: 0: INFO: Backburner Path(s) Found in PATH: ‘C:\Program Files (x86)\Autodesk\Backburner’
2015-06-25 09:41:46: 0: INFO: Backburner server.exe version: 2016.0.0.1727
2015-06-25 09:41:46: 0: INFO: Rendering with 3dsmax version: 2016
2015-06-25 09:41:46: 0: INFO: Not forcing a build of 3dsmax because version 2014 and later is 64 bit only
2015-06-25 09:41:46: 0: INFO: Rendering with executable: C:\Program Files\Autodesk\3ds Max 2016\3dsmax.exe
2015-06-25 09:41:46: 0: INFO: Slave 3dsmax.exe version: 18.0.873.0
2015-06-25 09:41:46: 0: INFO: Slave 3dsmax.exe description: 3ds Max 2016 base install
2015-06-25 09:41:46: 0: INFO: Submitted from 3dsmax.exe version: 18.0.873.0
2015-06-25 09:41:46: 0: INFO: Submitted from 3dsmax.exe description: 3ds Max 2016 base install
2015-06-25 09:41:46: 0: INFO: Checking registry for 3dsmax language code
2015-06-25 09:41:46: 0: INFO: Language code string: ENU
2015-06-25 09:41:46: 0: INFO: Language sub directory: en-US
2015-06-25 09:41:46: 0: INFO: Fail on existing 3dsmax process: 0
2015-06-25 09:41:46: 0: INFO: Load 3dsmax timeout: 1000 seconds
2015-06-25 09:41:46: 0: INFO: Start job timeout: 1000 seconds
2015-06-25 09:41:46: 0: INFO: Progress update timeout: 8000 seconds
2015-06-25 09:41:46: 0: INFO: Progress update timeout disabled: 0
2015-06-25 09:41:46: 0: INFO: Slave mode enabled: 1
2015-06-25 09:41:46: 0: INFO: Silent mode enabled: 0
2015-06-25 09:41:46: 0: INFO: Local rendering enabled: 1
2015-06-25 09:41:46: 0: INFO: Running render sanity check using 3dsmaxcmd.exe
2015-06-25 09:42:02: 0: An exception occurred: Error: The 3dsmax command line renderer, C:\Program Files\Autodesk\3ds Max 2016\3dsmaxcmd.exe, hung during the verification of the 3ds max install
2015-06-25 09:42:02: at Deadline.Plugins.ScriptPlugin.StartJob(Job job, String& outMessage, AbortLevel& abortLevel) (Deadline.Plugins.RenderPluginException)[/code]

Is the windows firewall running? If so, exceptions are recommended:
docs.thinkboxsoftware.com/produc … iderations

From our 3dsMax docs - known error messages:

Has the machine been restarted since Backburner / 3dsMax 2016 was installed?

Finally, if you were to login to the machine and run “3dsmaxcmd” from a command prompt, does it give any more information?

It only happens once and then renders fine so I don’t think it’s firewall (which is off). And yes they’ve rebooted a number of times.

OK. 3dsMax seems to like being started at least once with a user account that has local admin rights. Does your service account your running Deadline as have local admin rights?

Alternatively, if this is a temp thing, you could disable the check in plugin options, by disabling “Run Render Sanity Check”, but that’s not ideal and I’d prefer to get to the bottom of the issue, which guess is Max2016 related? Does this happen in other versions?

docs.thinkboxsoftware.com/produc … figuration

Hi Mike

I was also getting this 3ds ‘hung during verification’ error so had a look into it.

I noticed that on a new EC2 instance started from an AMI it takes around 25 seconds to load 3dsmaxcmd the first time, even if on the original instance used to make the AMI 3dsmaxcmd has already been run. Deadline’s 3dsmax.py StartMax() timeout is only 15 seconds, so by upping this to 35 seconds the error disappears.

For anyone who wants to increase the timeout, locate the Deadline 3dsmax plugin (“C:\DeadlineRepository8\plugins\3dsmax\3dsmax.py”), open it, search for ‘timeout =’, which should be inside the StartMax method, and change the following number to the desired value. In Deadline 7 it’s in milliseconds I believe, so 35000 should be sufficient, in Deadline 8 it’s in seconds so 35 will do.

Cheers

David

Thanks for the tip David. I’ve made an issue internally here so we can discuss these timeouts and maybe tweak how long they run for. They’ve been around so long they predate me, and I’m curious what previous problems they solved.

That said, does anyone find these timeouts help you get past any issues in Max?

FYI. I have fixed this issue at the same time as fixing this forum user’s issue as well:
forums.thinkboxsoftware.com/vie … 695#p68695