This bug known since severals 3DsMax/Backburner version - link to threat - is still uncorrected.
A reminder since It’s a big lose of time (10h ++) when forgotten. Here’s how I got ride of it :

1st given solution :
- in the file “backburner.xml” , set <MaxRender> to a higher value than 600, for my present need I assume 1200 would be enough,
but BB still reports a Task Timeout and stops the rendering after 600 mn.

2nd given solution :
- in’Network Job Assignment dialog/Advanced Settings : enable the ‘Per Job Timeouts’
- and set ‘Wait for MAX to Render’ to an higher value, e.g. 1200.
I didn’t revert the “backburner.xml” file to default, so don’t know if the change made to it can be omitted.

Then BB could complete a 11 h job. I presume it will works with any value higher than 600.

Make sure 3dsmax is installed on the Manager Machine where you are editing the TaskTimeout.  Then it should work properly.

Make sure you stop Backburner Manager and Server before you change the setting, then restart both processes or applications.  I would do this to all servers if you can, just to make sure they all pick up the change properly.

http://usa.autodesk.com/adsk/ser...d=10088127&linkID=9241177

Maneswar Cheemalapati [FA]

I’m getting this problem, but only on 64bit versions of the software. I can’t install that version of max on the manager machine because it’s not 64bit.

Andy Engelkemier 27 August 2008 11:17 AM

I’m getting this problem, but only on 64bit versions of the software. I can’t install that version of max on the manager machine because it’s not 64bit.

We have the same problem, and ditching a new 64bit machine just to handle the BB manager while we have many 32 ones that could do the job perfectly fine isn’t the best solution.

well yeah. And also you kind of need a machine with Windows Server on it if you have more than 10 machines on your network. Otherwise if they all try and save at the same time (it happens more often than you think) or access files at the same time some of them fail.