Hi, Im having issues with getting my rendernode working through backburner, and i’m hoping it’s an easy fix:
The backburner manager is on my workstation and is giving me errors when the node starts picking up a job:
see attached “manager”
They’re both (workstation + rendernode) connected to backburner, no issues to “connect”:
see attached “submitting”
However, the node’s server is reporting the following when trying to boot the render process: A bunch of missing dll’s from corona followed with a could not read/write to type message…
see attached “node-server”
Both the workstation and rendernode are connected to a NAS through a router which I assume assigns and handles the IP. This is a pretty straightforward process in the past and has always worked, it sets itself up automaticaly. I’m also assuming it’s set up correctly because they’re actualy connected and I can see them both in the backburner monitor, so I have no reason to think it’s IP or v4 / v6 related…
I installed the corona render-NODE version and did the chaos licencing application, seems to work fine I reckon.
Any input appreciated.
Btw when using the workstation as a backburner server with the “normal” corona licence, it renders fine as a “node”.
at a first glance this looks to me as if the beast does not load Corona at all, or any old version. Can you post the max.log of the rendernode as well?
It’s a proof that Corona did not load at all. And at the end of the log (starting at 12:45:36) you can see a failed spawn attempt of the CoronaDRServer and a quite unambiguous line:
2023/09/22 12:45:59 INF: [14196] [25392] SYSTEM: Production renderer is changed to Missing Renderer. Previous messages are cleared.
Not sure what you mean here. Could it be that you only installed DrServer accidentally? DrServer is just a “spawner” that launches and controls Max. You need a Max with fully installed Corona for that version to use it as render node - no matter if using BB or DrServer or any other client/server setup. You’d have to tick “3ds Max 2023” if you do a custom install. Reinstalling with the correct options should solve it.
