I’ve been getting this message a lot on our nodes.
I have to force restart Max and the DR server before I can send any jobs to the node.
Is there anything I can do to stop this happening?
Using latest daily as 1.6 was stuck in a loop where it said it was either downloading or waiting for render start.
Might have to revert to 1.5 at this rate, but don’t really want to do that if possible.
The hotfix seems to have sorted this (for now at least) but we are still getting render nodes that are stuck on downloading scene and waiting for render start.
Do you have 1.6 hotfix installed on slaves? Could you please try to delete (or rename) the DrData folder and reinstall 1.6 hotfix on slaves?
Yes, hotfix installed on all nodes. Will delete folder and reinstall.
Removed folder and reinstalled on all nodes.
We are not getting the status:closed now but we are still getting the ‘waiting for render start’ message which never goes away. If you restart Max or the DR server, then it’s OK, but it’s a pain having to restart the nodes after each render.
Im still having this problem. It only started after I ended the trial and purchased the license. Do I need to uninstall corona and reinstall?
Just a random idea, but could you try removing the licensing files on the master machine and all nodes as instructed here https://coronarenderer.freshdesk.com/support/solutions/articles/12000015667 , and then re-activate Corona on all of them, preferably using the licensing server: https://coronarenderer.freshdesk.com/support/solutions/articles/5000618553 ?
This issue is very rare so I do not know how/if it could affect DR.