>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
2024-01-19 15:31:47: Exception Details
2024-01-19 15:31:47: RenderPluginException -- Error: Renderer returned non-zero error code -1073741819. Check the renderer's output.
2024-01-19 15:31:47: at Deadline.Plugins.PluginWrapper.RenderTasks(Task task, String& outMessage, AbortLevel& abortLevel)
2024-01-19 15:31:47: RenderPluginException.Cause: JobError (2)
2024-01-19 15:31:47: RenderPluginException.Level: Major (1)
2024-01-19 15:31:47: RenderPluginException.HasSlaveLog: True
2024-01-19 15:31:47: RenderPluginException.SlaveLogFileName: C:\ProgramData\Thinkbox\Deadline10\logs\deadlineslave_renderthread_0-LWS03-0000.log
2024-01-19 15:31:47: Exception.TargetSite: Deadline.Slaves.Messaging.PluginResponseMemento d(Deadline.Net.DeadlineMessage, System.Threading.CancellationToken)
2024-01-19 15:31:47: Exception.Data: ( )
2024-01-19 15:31:47: Exception.Source: deadline
2024-01-19 15:31:47: Exception.HResult: -2146233088
2024-01-19 15:31:47: Exception.StackTrace:
2024-01-19 15:31:47: at Deadline.Plugins.SandboxedPlugin.d(DeadlineMessage bgq, CancellationToken bgr)
2024-01-19 15:31:47: at Deadline.Plugins.SandboxedPlugin.RenderTask(Task task, CancellationToken cancellationToken)
2024-01-19 15:31:47: at Deadline.Slaves.SlaveRenderThread.c(TaskLogWriter ajv, CancellationToken ajw)
2024-01-19 15:31:47: <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
This machine renders fine with maya 2023 and redshift, but refuses to work with maya 2024, it never launches.
The error code -1073741819 is equivalent to 0xC0000005, which represents a Memory Access Violation error. So Maya is running out of memory, or memory has become corrupt which Maya process is trying to access. If you find that your frames are still being rendered outside Deadline, you can modify the Maya plugin to ignore this error. To isolate the submission from Deadline try follow the below steps:
- To troubleshoot more submit the same job with MayaBatch disabled, there’s an option in the submitter “Use Batch Plugin” uncheck it. The job will now render via MayaCmd Plugin and will print the actual command line arguments to render the job out side of Deadline.
- Now Look for Full Command in the job report (right click the job> View Job Reports> See the errored tasks> Ctrl+F to search for the word “Full Command”).
- Copy this full command and run it on the same render node (by logging inside as the same user under which the render ran) which has failed the task via cmd/terminal.
- If you get the same error it means you are able to reproduce the issue outside of Deadline and the scene/assets/render node need to be fixed.
More info is here: Troubleshooting — Deadline 10.1.23.6 documentation
If the job render fines outside Deadline following the above steps, add the following function to the MayaCmd.py which can be found in [Repository]/plugins/MayaCmd:
def CheckExitCode( self, exitCode ):
if exitCode == -1073741819:
self.LogInfo( "Renderer reported an error with error code 1073741819. This will be ignored." )
elif exitCode != 0:
self.FailRender( "Renderer returned non-zero error code %d. Check the renderer's output." % exitCode )
Or you can submit a Mayabatch job with checking the below option at submission time:
https://docs.thinkboxsoftware.com/products/deadline/10.3/1_User%20Manual/manual/app-maya.html#submission-options
-
Use MayaBatch Plugin: This uses our MayaBatch plugin that keeps the scene loaded in memory between frames, thus reducing the overhead of rendering the job.
Maya never launches.
This is the complete log from deadline, with paths removed:
2024-01-19 15:31:40: 0: Executing plugin command of type 'Initialize Plugin'
2024-01-19 15:31:40: 0: INFO: Executing plugin script 'C:\ProgramData\Thinkbox\Deadline10\workers\<MachineName>\plugins\65aabf10114b3274b4a193ff\MayaCmd.py'
2024-01-19 15:31:40: 0: INFO: Plugin execution sandbox using Python version 3
2024-01-19 15:31:40: 0: INFO: About: Maya Cmd Plugin for Deadline
2024-01-19 15:31:40: 0: INFO: The job's environment will be merged with the current environment before rendering
2024-01-19 15:31:40: 0: Done executing plugin command of type 'Initialize Plugin'
2024-01-19 15:31:41: 0: Start Job timeout is disabled.
2024-01-19 15:31:41: 0: Task timeout is disabled.
2024-01-19 15:31:41: 0: Loaded job: <job name> (65aabf10114b3274b4a193ff)
2024-01-19 15:31:41: 0: Executing plugin command of type 'Start Job'
2024-01-19 15:31:41: 0: DEBUG: S3BackedCache Client is not installed.
2024-01-19 15:31:41: 0: INFO: Executing global asset transfer preload script 'C:\ProgramData\Thinkbox\Deadline10\workers\<machineName>\plugins\65aabf10114b3274b4a193ff\GlobalAssetTransferPreLoad.py'
2024-01-19 15:31:41: 0: INFO: Looking for legacy (pre-10.0.26) AWS Portal File Transfer...
2024-01-19 15:31:41: 0: INFO: Looking for legacy (pre-10.0.26) File Transfer controller in C:/Program Files/Thinkbox/S3BackedCache/bin/task.py...
2024-01-19 15:31:41: 0: INFO: Could not find legacy (pre-10.0.26) AWS Portal File Transfer.
2024-01-19 15:31:41: 0: INFO: Legacy (pre-10.0.26) AWS Portal File Transfer is not installed on the system.
2024-01-19 15:31:41: 0: Done executing plugin command of type 'Start Job'
2024-01-19 15:31:41: 0: Plugin rendering frame(s): 18
2024-01-19 15:31:41: 0: Executing plugin command of type 'Render Task'
2024-01-19 15:31:41: 0: INFO: Setting MAYA_DEBUG_ENABLE_CRASH_REPORTING environment variable to 0 for this session
2024-01-19 15:31:41: 0: INFO: Setting MAYA_DISABLE_CIP (ADSK Customer Involvement Program) environment variable to 1 for this session
2024-01-19 15:31:41: 0: INFO: Setting MAYA_DISABLE_CER (ADSK Customer Error Reporting) environment variable to 1 for this session
2024-01-19 15:31:41: 0: INFO: Setting MAYA_DISABLE_CLIC_IPM (ADSK In Product Messaging) environment variable to 1 for this session
2024-01-19 15:31:41: 0: INFO: Setting MAYA_OPENCL_IGNORE_DRIVER_VERSION environment variable to 1 for this session
2024-01-19 15:31:41: 0: INFO: Setting MAYA_VP2_DEVICE_OVERRIDE environment variable to VirtualDeviceDx11 for this session
2024-01-19 15:31:41: 0: INFO: Setting MAYA_RENDER_SETUP_INCLUDE_ALL_LIGHTS environment variable to 1 for this session
2024-01-19 15:31:41: 0: INFO: Setting REDSHIFT_FORCEQUITONINTERNALERROR environment variable to 1 for this session
2024-01-19 15:31:41: 0: INFO: Setting MAYA_ENABLE_LEGACY_RENDER_LAYERS environment variable to 0 for this session
2024-01-19 15:31:41: 0: INFO: Rendering with Maya version 2024.0
2024-01-19 15:31:41: 0: INFO: Setting PYTHONHOME environment variable to C:\Program Files\Autodesk\Maya2024\Python for this session
2024-01-19 15:31:41: 0: INFO: Stdout Redirection Enabled: True
2024-01-19 15:31:41: 0: INFO: Stdout Handling Enabled: True
2024-01-19 15:31:41: 0: INFO: Popup Handling Enabled: True
2024-01-19 15:31:41: 0: INFO: QT Popup Handling Enabled: False
2024-01-19 15:31:41: 0: INFO: WindowsForms10.Window.8.app.* Popup Handling Enabled: False
2024-01-19 15:31:41: 0: INFO: Using Process Tree: True
2024-01-19 15:31:41: 0: INFO: Hiding DOS Window: True
2024-01-19 15:31:41: 0: INFO: Creating New Console: False
2024-01-19 15:31:41: 0: INFO: Running as user: Juan Paulo
2024-01-19 15:31:41: 0: INFO: Rendering with Maya version 2024.0
2024-01-19 15:31:41: 0: INFO: Executable: "C:\Program Files\Autodesk\Maya2024\bin\Render.exe"
2024-01-19 15:31:41: 0: INFO: Rendering to network drive
2024-01-19 15:31:41: 0: INFO: Rendering with Redshift.
2024-01-19 15:31:41: 0: INFO: Argument: -r redshift -s 18 -e 18 -b 1 -rd <stripped this, project path>
2024-01-19 15:31:41: 0: INFO: Full Command: "C:\Program Files\Autodesk\Maya2024\bin\Render.exe" -r redshift -s 18 -e 18 -b 1 -rd <stripped this, project path>
2024-01-19 15:31:41: 0: INFO: Startup Directory: "C:\Program Files\Autodesk\Maya2024\bin"
2024-01-19 15:31:41: 0: INFO: Process Priority: BelowNormal
2024-01-19 15:31:41: 0: INFO: Process Affinity: default
2024-01-19 15:31:41: 0: INFO: Process is now running
2024-01-19 15:31:43: 0: INFO: Process exit code: -1073741819
2024-01-19 15:31:43: 0: Done executing plugin command of type 'Render Task'
2024-01-19 15:31:43: 0: Executing plugin command of type 'End Job'
2024-01-19 15:31:43: 0: Done executing plugin command of type 'End Job'
2024-01-19 15:31:47: Scheduler Thread - Render Thread 0 threw a major error:
2024-01-19 15:31:47: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
No other machine has this issue. We are using MayaCmd instead of mayabatch for stability reasons.
In this machine, only maya 2024 has this problem, which was freshly installed.
The error is the same as if the machine didn’t have maya 2024 installed, which is not the case at all.
If you run this:
"C:\Program Files\Autodesk\Maya2024\bin\Render.exe" -r redshift -s 18 -e 18 -b 1 -rd <stripped this, project path>
how does it behave? Does it crash immediately or successfully render?
The mentioned machine does nothing.
Other nodes or my machine proceed to render the frame loading the respective data and outputting info as the render progresses.
That’s a great test! So what we know is it’s not Deadline keeping Maya from firing up, it’s something amiss with either the machine or the Maya install.
And I bet if you read the exit code after nothing happens it’ll kick back -1073741819.
I’d see if a re-install of Maya sorts this out, or if Autodesk support have any advice.
I’ve kept checking, this node won’t launch if I use MayaCmd instead of mayabatch (both scripts launch the same .exe so this is odd) We cannot use deadline’s mayabatch implementation because it breaks our xgen workflow, mayacmd doesn’t.
I don’t know if this rings any bells to you.
No bells I’m afraid, I don’t know Xgen or its workflows well enough to know what would cause MayaCMD to not work for it.
If you can, I’d re-image the machine. If it’s just the one node I don’t know if it’s worth fighting it versus restarting from a known good state.
