Hopefully this may help you if you are having timeout issues with Backburner:

[ericbarlow21]

Hello All,

 

I know that some people are having issues with Backburner timing out on renderings, or not saving their settings. I just wanted to share a couple of our solutions incase you are experienceing these issues:

 

(assuming you are upgrading from Max 9 --> 2008 or 2008 --> 2009)

 

1.) completely uninstall the old backburner, and install the new one included with the new version of Max you are installing (even though they may be the same version or list no changes in the release log). I am not sure why, but making this change has been the difference in working correctly vs. not working in regards to our timeout issues.

 

2.) we once had issues with Backburner when upgarding to Max 2008, because our manager was running on 32 bit while 64 bit was being used on within our farm. Even though our manager is a 32 bit system, using the 64 bit software solved our issues. i dont know why, but it did.

 

Anyways, I know these solutions worked for us, so if you are having problems, you may want to give them a try.

 

Good luck!

[Nic H]

arrghhh this is such a pain in the ass

 

Iv tried everything...nearly. it used to work until last week when *something* changed on the farm and now it wont render past 600 mins

 

I hate you autodesk, this has been intermittently broken since 2006 and i have read every thread on the subject everywhere and no guaranteed fix.

 

Just wanted to say i hate you, in person.

[BrianKitts]

It's always been backwards with Autodesk to avoid timeouts.....you have to enable task timeout in the advanced settings (yes I mean turn it on) and then set it to a high value, (max is 70000) minutes..... to keep it from timing out.

 

leaving the task timeout disabled has never worked well.

[Nic H]

ah but my problem over this last weekend was that I was manually entering 2500 min (plenty enough time for my render) but it was timing out at 600 anyway. I think it has to do with having 32 bit max alongside 64 on my machine, well thats my theory until 7pm anyway.

 

i solved it by taking over the whole render farm and using DR today, just lucky nothing else was on

 

thanks.

[Brian Cassil]

I've encountered this problem many times over the last couple of years. I've done everything suggested here and last night a job timed out after 600 minutes. Seriously, can this be so hard to fix!?

[neil poppleton]

I appreciate this is an old thread.

 

In the past timeout has not been an issue but I have one file that has timeout enabled and set to 6000, but it crashes out on backburner with the dreaded timeout 600 error.

 

Has anyone fixes for this issue. I am using max2010.

[Matt McDonald]

I've read before, but not had a chance to verify, that in order to avoid timeouts you need to install Max on the machine running the manager. You don't have to authorize it but you need to do a full install.

 

'hope that helps.

[neil poppleton]

Appreciate your post elevation.. I did think earlier today that although I have updated all 19pcs to max 2010 at xmas, i have not updated the server with the latest back burner, so when their is a break in rendering i will update the server and fingers crossed.

[Brian Cassil]

I wouldn't hold out too much hope. I have a full install of max on the manager and I have the latest version of backburner and it is still a problem for me... I think. It has been a while since I've had a job go over the 600 minute limit so who knows maybe something magical happened with a service pack or something like that but I seriously doubt it.

[neil poppleton]

I wouldn't hold out too much hope. I have a full install of max on the manager and I have the latest version of backburner and it is still a problem for me... I think. It has been a while since I've had a job go over the 600 minute limit so who knows maybe something magical happened with a service pack or something like that but I seriously doubt it.

 

Cheers Brian, Will try install and report back soon...