we've just set up a small network (6 machines) to render a mix of 3D Max and Combustion projects using Backburner. Our experiments have focused mainly on Combustion at this point, but I thought you guys in max land might have experience in these sorts of problems. Everything seems to be talking (you can send a combustion render out, and the manager grabs it, sends it out to the render machines (which are running backburner server), they seem to inialize, taking the job and get through as far as the "loading combustion3" part of the process, ....only to then crash and burn (coming up with a Microsoft error message about the windows application needed to close, do you wish to save report, ...that pesky message. I was wondering if it could be an issue with XP SP2, ...I know colleagues who refuse to run Combustion on XP (still running it on win2000 pro), due to stability issues. In our first attempts (before the crashes on the client machines), things didn't even seem to get that far, we got errors almost straight away within the manager (next to the render machine names) saying they couldn't write to a frame name that already exists (we didn't really solve that, the other error just seemed to take over from it).
Anyone have any ideas or tips?
With similar issues regarding 3ds max scenes that wont render on a given computer, I usually move the license to that computer to be able to start max and work there. Then I try to load the same scene there and make it render locally. This is just to be able to isolate problems and get to the cause of it. Maybe you could try to do something similar? Try to open the same Combustion project locally on that computer.