Network Job Assignment/Backburner Issue

[gordon]

I've just recently started experiencing complete crashes when I send certain jobs to render over our network though backburner.  The current job that is doing this was working perfectly fine a week or two ago.  Now, when I submit the job to render on the network I get to the Backburner dialogue box, setup my preferences, and hit submit (screenshot attached).  Backburner thinks for a bit, says that it's saving the scene, thinks some more then just quits (screengrab of error message attached).

I've tried merging my scene into an entirely new max scene, I've tried changing the computer that hosts the Backburner Manager, I've tried having a colleague send the job from his machine, all with the same result.

I've only had this happen with 2 different files so far.  I've also had other files that render perfectly fine on the network.

Has anyone else experienced this?  If so, is there a solution or a work-around that I can try?  I need to get this animation rendering ASAP and I don't want to have all of the frames rendering on my local machine.

[gordon]

I have to assume that there's something in my scene that is causing this, but I have no idea what it could be.  If anyone else has experienced this and figured it out, please let me know.

[jens.diemer]

it often helps to start a new .max file and merge all objects...

[gordon]

Hi Jens,

I did do that, with both of the affected scenes, and it still kicked out the error message.

[CAMedeck · Accepted solution]

Try sending it without the "Include Maps" option checked.  Maybe there is an issue with a corrupt or incompatible map?

[gordon]

That did it.  I can't believe I didn't think to try that.  Thank you very much!