Error: ExecuteScript: Timed out waiting for the lightning 3dsmax plugin to acknowledge the ExecuteScript command.
This seems to be a recurring issue. I have read through all the old posts I could find that seemed relevant and there is no solution.
I had this same issue on a deadline farm at my last job and we would just format and rebuild the machines when that happened. I dont want to do that any more.
I want to find out what is causing this.
We seemed to make a little progress if we deleted the user folder from windows and rebooted, but this causes other issues I dont like.
We see this error every day, often it prevents jobs from finishing unless we requeue the tasks that hang up.
Here is the job report
Job Report.txt (29.9 KB)
Here is the slave log for the slave that was responsible for the above report. I am not sure if this log covers the same period of time or not.
Job Report.txt (29.9 KB)
Slave Log (2).txt (50.7 KB)
Hi,
Here’s a few things we can try
-
Enable in “Monitor (super-user) --> Configure Plugins” --> “3dsmax” --> “Kill ADSK Comm Center” set to True (If this makes matters considerably worse, then revert back to False)
-
In SMTD, “Options” tab --> “User Options” --> Enable the “Delete Empty State Sets in the Submitted File” checkbox.
-
As an alternative to following step #2 above, please see the attached infographic which explains how to remove State Set references in your scene.
-
If none of the above make any difference OR seem to help, but not fully resolve the issue, then I have some experimental code which should help here, which is currently targeting to be released in the next v7.1 beta cycle which starts up in a few weeks time.
[attachment=0]How_To_Fix_State_Sets_Issue_3dsMax.png[/attachment]
OK,
i have done this. it may take some time before i can be certain if I have impacted the issue.
what happens if the scene is using state sets?
we are experimenting with state sets and batch rendering and I would hate if that were already a dead end, but it would be good to know.
thanks, as always, for your help!
Cool. Let us know the results!
The issue in Max2014 is that even with the latest service pack/product update, the state sets dialog will try to pop-up during network rendering. This is ok during normal network rendering, but not when being run as a service as GUI is not possible and causes 3dsMax to crash. I was hoping this was fixed in Max2015, but that doesn’t seem to be the case. Maybe Max2016? We support State Sets via SMTD and indeed batch rendering, it’s just an issue if running as a service due to a ADSK bug which I have reported some time ago…
I dont know if it impacts anything but we dont run the service on our slaves as we need the frame buffer. We pipe the frame buffer from the nodes to tvs on our production floor so our artists can see WiP and kill jobs before they finish rendering.
Ah, I might have missed an important line in your posted job reports. Re-reading your log reports, I’m thinking the real issue here is the hanging at the line entry where it’s executing our “customise.ms” maxscript file (which is perfectly fine and no issue there). So, by you following my previous instructions - point #1 (enabled ADSK kill switch), then you should see a marked improvement here (less errors of this exact kind, but not zero). However, this was always a hack based on as much real client feedback as I could gather. So, in upcoming v7.1 beta, I have a further improved and I really hope, ‘final solution’ to this issue, which has been proven to fix 2 large 3dsMax based studios that were previously suffering this issue. So, I suggest giving your current tweaked setup a run for a while and also trying out v7.1 beta 1 once we roll out the next beta program for customers. Fingers crossed. 
]another issue we frequently see is the machines hanging up on starting up the job.
they just sit there at 0 percent forever. If i remote into the node max has crashed and isn’t even open.
any ideas on this issue too, or should i post this as a separate thread?
i dont have the slave log for this period, but when i see then again I will get it.
If the error message is identical to the subject of this forum thread when you next get a full 3dsmax job log, then please do post it here as a continuation of this discussion. If not and it’s a new/different error that seems un-related, then feel free to post a new forum thread.
