Cmdjob.exe is not working for us in 2014. We have given BB all the same freedom in our firewall as we have for years.
We are moving from Max 2012, where BB2008 works fine, to Max 2014 that doesn鈥檛 seem to play well with 2008.We have kept BB2008 because changes in cmdjob.exe in 2009 and onward did not work for us. Honestly I can鈥檛 remember if our issues back then are the same as what I鈥檓 seeing now.
I鈥檝e dropped obsolete options such as -jobNameAdjust and -leaveInQueue. I don鈥檛 see any syntax related errors.
No matter which executable I try to run with cmdjob, it returns the same:
Cannot create job: The system cannot find the file specified.
I鈥檝e confirmed the file name/location etc.
We have this same command string working now with BB2008 and hundreds of servers.
This is my command string:
鈥淐:\Program Files (x86)\Autodesk\Backburner\cmdjob.exe鈥?-jobName jonah-VRayDR2012 -manager ourManagerName -priority 50 -numTasks 1 -taskName 1 -timeout 6000 -servers ourServerNames -workpath 鈥淐:\Program Files\Autodesk\3ds Max Design 2014鈥?vrayspawner2013.exe
Does anyone else have issues or insights to share?
Thanks very much,
Jonah
Hi jonah, we just stumbled with a problem that looks like yours. Did you find any solution to this?
No, not yet. We cannot send command jobs from 2014.
What is your issue?
We can鈥檛 get a postrender script to run reliably. The script is supposed to execute after the render finishes and send a command job to BB so it handles a image conversion task.
We鈥檝e found that we can get to execute the commandjobs if instead of specifying the 鈥?servers鈥?parameter, we create a render group in BB and use 鈥?group鈥?parameter. But that only works for us sometimes.
Sometimes it鈥檚 like the manager 鈥渃hokes鈥?at night or there is a permission issue, because when I make a simple test it always works, but when we leave a large queue of long renders for a night they all fail. It鈥檚 hard to find the problem this way 鈥?/p>