I have setup a custom plugin for Maya 2013 - 2015 with one location for scripts/plugins and users… everything seems to render fine, however once my render completes the slave will just stop responding and close.
I’m running deadline 6.2 with a Win 7 environment.
Would love some help trying to diagnose this issue 
*attached is my custom maya batch plugin
MayaBatchHeckler.txt (124 KB)
Hello,
Thanks for including your script. Could I have you also send along a job report and slave log from the machine you tried this on? You can get the slave report by opening the slave or monitor, then going to help, and then explore log folder. For the job report, just right click the job, choose view job reports, then right click a report and click save report. Thanks.
Unfortunately I’ve had to revert back to Deadline 5.2 so I am unable to print out a node output log.
I do however have a working 5.2 custom MayaBatch script. Would love some help to modify this to work with 6.2.
attached are Deadline 5.2 MayaBatch script and custom Submission script.
MayaBatchHeckler.txt (105 KB)
SubmitMayaToDeadline_iw.txt (182 KB)
There were quite a few changes to the API to make it work better with Python.net. We really don’t want to break everyone’s hard work.
I looked over the changes to your custom scripts by diffing the two and there’s quite a bit that’s different, but the changes are subtle. I think it’s going to be slightly trickier to pick out all of the required changes because we added quite a bit between the version you based your changes on and what’s shipping in 6.2.
One thing to try while you’re working on migrating your scripts to 6.0 is to run them in ‘depricated mode’. See here:
thinkboxsoftware.com/deadlin … cated_Mode
That section deals with migration and pretty much mirrors this long winded post. 
The big difference in 6.0 is that we removed the global functions. Anything lingering around that looks like “IsCancelled()” or “VerifyMonitoredManagedProcess()” should be prefixed with the plugin object (usually “self.”). Some are now part of ClientUtils such as “GetDeadlineBinPath()”. If you do a side-by-side diff the differences stand out pretty clearly.
For testing, you’ll be able to run 6.2 and 5.2 on the same machine at the same time, so you can just put a 6.2 Repository and Database on your workstation and work on it there without stepping on anything. That’s what we all do over here.