the error message donst mean something special
its a default message if something goes wrong
most likely its out of memory
other posssible reason can be broken geometry
the machine has 12 GIGS of memory, the scene itself uses roughly 5 GIGs…renders fine on one set of manager/server but it does this on the other set of machines.
so it cant be broken geometry and it cant be memory
Try setting your “User Account Control” sensitivity on all of your Windows 7 Backburner nodes to their lowest setting. This was the solution for us when we switched to Windows 7 and encountered the same generic error message.
I have similar problems with net rendering. our three workstations aren’t render big scenes, but our renderslaves (Q6600) render fine. if I open the scene from the “job” folder of the manager my workstation crash (max)… I have read that the quadro cards have some problems to load scenes with big meshes. I hate this error, it make no sense at all. the other thing is if max crashes when loading a scene, then the scene won’t open anymore before you haven’t merged all the stuff into a new scene! the it works again, til the next crash. but I don’t know why it doesn’t render over net. any ideas?
hi themaxxer,
rendering went just fine overnight…so the conlusion in my case was unstable bios setting (voltage, CL timings)
check your memory and try removing viewcube and steering wheel from your standard max plugins (ive read this helps in some cases)
hope that helps
best regards
hm, nothing helped for me!!!
I don’t get it that my old comps are rendering fine while our new workstations wont. I have now another comp from a friend and it’s rendering too. all have win7 PRO 64bit, vray 1.5 SP5, 3ds max 2010 64bit, and all comps are loading the same plugins…
I have tested to increase the ram voltage and the tings with the viewcube.
If it’s Win7 and all of those new machines don’t render, try to start start server.exe on those machines with admin privileges and see if that helps. This happened to me too and I needed a while to find this out. Hope this helps.
I have found the source for the error… it’s the VFB, but only if I want to save the image! when the “save separate render channel” check box isn’t active, then the rendering starts without error.
I have tried everything to avoid this error, but I haven’t found a solution or workaround. and it’s still funny our old Q6600 render all the data without any error!
I’m having the same problem--and it just popped up. Everything was going fine until the other day. The only thing that I changed that I can remember is updating my video card drivers. And this incarnation of the problem is really bizarre (well, at least, I’ve never seen it):
I have one workstation (dual 6-cores, Max 2011, vray 1.5 sp5, 12 gigs ram) that use to send my jobs to my render slaves (almost identical specs). Whenever I build a pre-calculated light solution (IR+Lcache) and send the job to the backburner queue, the render slaves pick it up just fine. When I close max and start up server on my workstation, I get the dreaded ‘unexpected error’ almost immediately when backburner starts loading the vray .dlls. No matter what, the workstation that I use to send the job doesn’t render as a backburner server. But here’s the kicker--when I open the same file up and render it locally on my workstation, no problem.
I have been using the VFB, so I’ll try some tests using standard max buffer and see if that solves it, but I fear there’s something bigger going wrong here.
Way to go autodesk! Couple of hours wasted troubleshooting a problem with graphite modelling tools positioning that somehow causes backburner to become crashburner!