I’m trying to debug a bunch of Modo jobs that failed over night and they keep failing when I resubmit. All of the jobs are completed to varying degrees. They all have this same error message which is the only error message:
Error in RenderTasks: Command ‘!render.animation {*}’ failed with -2147483641. Check the meaning of this error code in the modo error codes message table, resource:msglxresult.cfg
at Deadline.Plugins.ScriptPlugin.RenderTasks(String taskId, Int32 startFrame, Int32 endFrame, String& outMessage, AbortLevel& abortLevel)
I’m checking on the Modo forums as well and I’m posting here to cover my bases.
James
This is the full job log for one of the failed tasks. They all match this for the most part.
Well, the exit code there ends up working out to 0×80000007 which is a standard Windows error. This handy page has a list of all of them:
msdn.microsoft.com/en-us/library … 81(v=vs.85.aspx
Which is… kind of weird. The error works out to:
ERROR_ARENA_TRASHED: “The storage control blocks were destroyed.”
Nothing makes sense based on that, so let me know what you get from running those frames through Modo’s user interface… I’m hoping it’s more helpful than what’s on the command line.
It looks like the problem was corrupted elements within Modo. One artist had a corrupted texture node, the other had a corrupted Motion Vector Render Output. I’m currently trying to find a way to get better error logging from Modo_cl. I’ll let you guys know if I find out anything better.
I think I can speak for the devs, and many of our customers, when I say that we would love a lot of applications having better error reporting.