AWS Thinkbox Discussion Forums

Deadline 10.1.23.6 Fail to render Maya 2023.2

So Deadline works fine with Maya 2023.1
But when I update to Maya 2023.2 then it cant create the output folder by it own
Therefore it stated folder not exists and stop rendering
I switched from MayaBatch to MayaCmd even using the commandline render generated by Deadline
I think there is an issue in Maya Plugin of Deadline

=======================================================
Error

Error: FailRenderException : Renderer returned non-zero error code -1073741502. Check the renderer’s output.
at Deadline.Plugins.DeadlinePlugin.FailRender(String message) (Python.Runtime.PythonException)
File “C:\ProgramData\Thinkbox\Deadline10\workers\USERPC\plugins\632cabd5264918b8e04c2687\MayaCmd.py”, line 1111, in CheckExitCode
self.FailRender( “Renderer returned non-zero error code %d. Check the renderer’s output.” % exitCode )
at Python.Runtime.Dispatcher.Dispatch(ArrayList args)
at __FranticX_GenericDelegate1`1[[System_Int32, System_Private_CoreLib, Version=4_0_0_0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]]Dispatcher.Invoke(Int32 )
at FranticX.Processes.ManagedProcess.CheckExitCode(Int32 exitCode)
at Deadline.Plugins.DeadlinePlugin.CheckExitCode(Int32 exitCode)
at FranticX.Processes.ManagedProcess.Execute(Boolean waitForExit)
at Deadline.Plugins.PluginWrapper.RenderTasks(Task task, String& outMessage, AbortLevel& abortLevel)

=======================================================
Type

RenderPluginException

=======================================================
Stack Trace

at Deadline.Plugins.SandboxedPlugin.d(DeadlineMessage bgj, CancellationToken bgk)
at Deadline.Plugins.SandboxedPlugin.RenderTask(Task task, CancellationToken cancellationToken)
at Deadline.Slaves.SlaveRenderThread.c(TaskLogWriter ajq, CancellationToken ajr)

=======================================================
Log

2022-09-23 04:34:34: 0: Loading Job’s Plugin timeout is Disabled
2022-09-23 04:34:34: 0: SandboxedPlugin: Render Job As User disabled, running as current user ‘user’
2022-09-23 04:34:36: 0: Executing plugin command of type ‘Initialize Plugin’
2022-09-23 04:34:36: 0: INFO: Executing plugin script ‘C:\ProgramData\Thinkbox\Deadline10\workers\USERPC\plugins\632cabd5264918b8e04c2687\MayaCmd.py’
2022-09-23 04:34:37: 0: INFO: Plugin execution sandbox using Python version 3
2022-09-23 04:34:37: 0: INFO: About: Maya Cmd Plugin for Deadline
2022-09-23 04:34:37: 0: INFO: The job’s environment will be merged with the current environment before rendering
2022-09-23 04:34:37: 0: Done executing plugin command of type ‘Initialize Plugin’
2022-09-23 04:34:37: 0: Start Job timeout is disabled.
2022-09-23 04:34:37: 0: Task timeout is disabled.
2022-09-23 04:34:37: 0: Loaded job: Video_12_v02_02 - RN_CAM (632cabd5264918b8e04c2687)
2022-09-23 04:34:37: 0: Executing plugin command of type ‘Start Job’
2022-09-23 04:34:37: 0: DEBUG: S3BackedCache Client is not installed.
2022-09-23 04:34:37: 0: INFO: Executing global asset transfer preload script ‘C:\ProgramData\Thinkbox\Deadline10\workers\USERPC\plugins\632cabd5264918b8e04c2687\GlobalAssetTransferPreLoad.py’
2022-09-23 04:34:37: 0: INFO: Looking for legacy (pre-10.0.26) AWS Portal File Transfer…
2022-09-23 04:34:37: 0: INFO: Looking for legacy (pre-10.0.26) File Transfer controller in C:/Program Files/Thinkbox/S3BackedCache/bin/task.py…
2022-09-23 04:34:37: 0: INFO: Could not find legacy (pre-10.0.26) AWS Portal File Transfer.
2022-09-23 04:34:37: 0: INFO: Legacy (pre-10.0.26) AWS Portal File Transfer is not installed on the system.
2022-09-23 04:34:37: 0: Done executing plugin command of type ‘Start Job’
2022-09-23 04:34:37: 0: Plugin rendering frame(s): 1-218
2022-09-23 04:34:37: 0: Executing plugin command of type ‘Render Task’
2022-09-23 04:34:37: 0: INFO: Setting MAYA_DEBUG_ENABLE_CRASH_REPORTING environment variable to 0 for this session
2022-09-23 04:34:37: 0: INFO: Setting MAYA_DISABLE_CIP (ADSK Customer Involvement Program) environment variable to 1 for this session
2022-09-23 04:34:37: 0: INFO: Setting MAYA_DISABLE_CER (ADSK Customer Error Reporting) environment variable to 1 for this session
2022-09-23 04:34:37: 0: INFO: Setting MAYA_DISABLE_CLIC_IPM (ADSK In Product Messaging) environment variable to 1 for this session
2022-09-23 04:34:37: 0: INFO: Setting MAYA_OPENCL_IGNORE_DRIVER_VERSION environment variable to 1 for this session
2022-09-23 04:34:37: 0: INFO: Setting MAYA_VP2_DEVICE_OVERRIDE environment variable to VirtualDeviceDx11 for this session
2022-09-23 04:34:37: 0: INFO: Setting MAYA_RENDER_SETUP_INCLUDE_ALL_LIGHTS environment variable to 1 for this session
2022-09-23 04:34:37: 0: INFO: Setting OCIO environment variable to C:/Program Files/Autodesk/Maya2023/resources/OCIO-configs/Maya-legacy/config.ocio for this session
2022-09-23 04:34:37: 0: INFO: Setting REDSHIFT_FORCEQUITONINTERNALERROR environment variable to 1 for this session
2022-09-23 04:34:37: 0: INFO: Setting MAYA_ENABLE_LEGACY_RENDER_LAYERS environment variable to 0 for this session
2022-09-23 04:34:37: 0: INFO: Rendering with Maya version 2023.0
2022-09-23 04:34:37: 0: INFO: Enforcing 64 bit build of Maya
2022-09-23 04:34:37: 0: INFO: Setting PYTHONHOME environment variable to C:\Program Files\Autodesk\Maya2023\Python for this session
2022-09-23 04:34:37: 0: INFO: Performing path mapping on ma scene file
2022-09-23 04:34:38: 0: INFO: Stdout Redirection Enabled: True
2022-09-23 04:34:38: 0: INFO: Stdout Handling Enabled: True
2022-09-23 04:34:38: 0: INFO: Popup Handling Enabled: True
2022-09-23 04:34:38: 0: INFO: QT Popup Handling Enabled: False
2022-09-23 04:34:38: 0: INFO: WindowsForms10.Window.8.app.* Popup Handling Enabled: False
2022-09-23 04:34:38: 0: INFO: Using Process Tree: True
2022-09-23 04:34:38: 0: INFO: Hiding DOS Window: True
2022-09-23 04:34:38: 0: INFO: Creating New Console: False
2022-09-23 04:34:38: 0: INFO: Running as user: user
2022-09-23 04:34:38: 0: INFO: Rendering with Maya version 2023.0
2022-09-23 04:34:38: 0: INFO: Enforcing 64 bit build of Maya
2022-09-23 04:34:38: 0: INFO: Executable: “C:\Program Files\Autodesk\Maya2023\bin\Render.exe”
2022-09-23 04:34:38: 0: INFO: Rendering to network drive
2022-09-23 04:34:38: 0: INFO: Rendering with Redshift.
2022-09-23 04:34:38: 0: INFO: Argument: -r redshift -x 1080 -y 1920 -s 1 -e 218 -b 1 -rd “B:/WORK/Test/images” -im “//” -cam “RN_CAM” -proj “B:/WORK/Test” “C:\ProgramData\Thinkbox\Deadline10\workers\USERPC\jobsData\632cabd5264918b8e04c2687\thread0_tempBbwSf0\Video_12_v02_02.ma”
2022-09-23 04:34:38: 0: INFO: Full Command: “C:\Program Files\Autodesk\Maya2023\bin\Render.exe” -r redshift -x 1080 -y 1920 -s 1 -e 218 -b 1 -rd “B:/WORK/Test/images” -im “//” -cam “RN_CAM” -proj “B:/WORK/Test” “C:\ProgramData\Thinkbox\Deadline10\workers\USERPC\jobsData\632cabd5264918b8e04c2687\thread0_tempBbwSf0\Video_12_v02_02.ma”
2022-09-23 04:34:38: 0: INFO: Startup Directory: “C:\Program Files\Autodesk\Maya2023\bin”
2022-09-23 04:34:38: 0: INFO: Process Priority: BelowNormal
2022-09-23 04:34:38: 0: INFO: Process Affinity: default
2022-09-23 04:34:38: 0: INFO: Process is now running
2022-09-23 04:34:38: 0: STDOUT: Starting “C:\Program Files\Autodesk\Maya2023\bin\mayabatch.exe”
2022-09-23 04:34:39: 0: STDOUT: // Maya exited with status -1073741502
2022-09-23 04:34:39: 0: INFO: Process exit code: -1073741502
2022-09-23 04:34:39: 0: Done executing plugin command of type ‘Render Task’

I’m running Maya 2023.2 and 10.1.23.6 on linux ok, are you sure the permissions are ok writing as the render user?

Yes I’m sure
because I rolled back to 2023.1 then resume the rendering then everything works fine
Really strange

It looks like Maya render process exited with an error code and failed the render if it returns a non-zero exit code. We can try isolate from Deadline and see if it render fine outside, it could be possible that we can script it to ignore the process exit code error and continue the render. Run the Full Command from the logs on the render node, as an example from the above logs we have in the thread below is the command that need to be grab and run on render node it failed on:

“C:\Program Files\Autodesk\Maya2023\bin\Render.exe” -r redshift -x 1080 -y 1920 -s 1 -e 218 -b 1 -rd “B:/WORK/Test/images” -im “//” -cam “RN_CAM” -proj “B:/WORK/Test” “C:\ProgramData\Thinkbox\Deadline10\workers\USERPC\jobsData\632cabd5264918b8e04c2687\thread0_tempBbwSf0\Video_12_v02_02.ma”

If the render completes successfully on the Command line, we can add the below code to ignore it in MayaCmd.py on line #1084

        elif exitCode == -1073741502:
            self.LogInfo("Ignoring exit code -1073741502")

An example of the patch is given under After Effects deadline docs: After Effects — Deadline 10.2.0.10 documentation

You can also run the MayaBatch job instead which doesn’t check for process exit code, and would render successfully.

If you’re also having this issue, at the end of the task report it shows the peak resource usages has the memory usage been maxed out? I’ve seen machines run out of RAM and crash Maya with a negative exit code in the past.

If that’s not the case I’d go through the troubleshooting guide to pull out the command the Worker is running to run the render, and test it on the render node in question.

If it fails then the issue is either in the flags we’re passing to the render.exe or in the scene file and not in the render sandbox the Worker runs Maya within so we can ignore the Worker.

It could be that in 2023.2 the flags Maya takes have changed and our plugin doesn’t account for them. I’m not seeing any changes called out in the Maya release notes with regard to rendering but those might be tracked somewhere other than here as these are more of the DCC-centric notes.

Assuming the previous test fails, I’d test redirecting the output to a local path on the machine to test if there’s a failure to write a directory on the network drive or a failure to write a directory anywhere. I haven’t found any explanation of what failure -1073741502 maps to so eliminating as many moving parts is going to be the best starting course of action.

Let us know if you have any questions!

1 Like

If using the command Deadline creates is regularly failing, I’d reach out to Autodesk support with it and the exit code as we haven’t been able to re-create this locally to better troubleshoot.

Given other folks aren’t having issues, have you tried testing without Redshift in the render? Maybe there’s a version incompatibility at play here.

My bad, my crash was due to an unmapped network location.

1 Like
Privacy | Site terms | Cookie preferences