Modo job fails with -2147483648

Deadline
1

I’ve got a weird issue with a scene where the tasks fail after the render files have been written out. This is causing the same frames to be rendered over and over again.

2018-02-07 08:57:40:  0: STDOUT: ! (renderProgress)     Frame Complete. | frameRenderTime:406.15 [6m 46.1s] |@:Wed Feb 07 08:57:40 2018
2018-02-07 08:57:40:  0: STDOUT: ! (renderProgress) Render complete | sceneRenderTime:406.149 [6m 46.1s] | @:Wed Feb 07 08:57:40 2018
2018-02-07 08:57:40:  0: STDOUT: ! (render) Render Failed
2018-02-07 08:57:40:  0: STDOUT: ! (renderProgress) Info | i:cleaningUp [Cleaning up...]| @:Wed Feb 07 08:57:40 2018
2018-02-07 08:57:41:  0: STDOUT: Command '!render.animation {*}' failed with -2147483648
2018-02-07 08:57:41:  0: Done executing plugin command of type 'Render Task'
2018-02-07 08:57:41:  0: An exception occurred: Error: Modo render failed to save output. Please make sure all defined output paths are accessible.
2018-02-07 08:57:41:     at Deadline.Plugins.PluginWrapper.RenderTasks(String taskId, Int32 startFrame, Int32 endFrame, String& outMessage, AbortLevel& abortLevel) (Deadline.Plugins.RenderPluginException)

I’ve scoured the scene to find any issues but I can’t find any. The paths are all correct and accessible, especially considering that it is actually writing out files. I’m unsure where the issue lies so I’m just doing my due diligence and asking all parties involved. :smiley:
BIOAD_04-Glow_v015_SF_2018-02-07_08-56-16_5a7b2fb07305ad13348c406e.txt (227 KB)

2

So I think I figured out what the issue is. File name length…or really max path length. Some of the outputs were surpassing the 260 character limit. I guess this is why it was complaining about not finding the file output path.

3

Oh reeeally? That’s an interesting situation. I’ll see if we can apply that thought to another client here…

4

Yeah, I’m actually writing in some sanity check code into our submission tool to catch this before it gets to the farm. But it’s a good thing to have documented.