Maya Batch Plugin "Cannot load scene" error

AlexV · October 22, 2018, 8:25pm

Hi everyone,

we’ve been facing an issue with running Maya Batch through Deadline and I haven’t been able to find any Documentation or help on this specific error so I thought I’d try my luck here!

The following error pops up whenever we try to run any Job with Maya Batch Plugin checked (regardless of whether submit Maya File is checked or not)

=======================================================
Error: Error: file: C:/Users/AERender/AppData/Local/Temp/tmpC23C.tmp line 43: Cannot load scene “C:/Users/AERender/AppData/Local/Thinkbox/Deadline10/slave/render08/jobsData/5bce2aafe36ed215ccbbb581/char_uv_review_v10.ma”. Please check the scene path, then try opening the scene on the machine which ran this job to troubleshoot the problem.
at Deadline.Plugins.PluginWrapper.RenderTasks(String taskId, Int32 startFrame, Int32 endFrame, String& outMessage, AbortLevel& abortLevel)

=======================================================

We’ve double checked user access permissions, whether the drives are mounted, whether the files are even being created on the Nodes (they are) and done as suggested, checked the path and opened the scene on the machine, all of which works just fine. This also isn’t an issue when rendering without maya batch.

We’re a bit at a loss with this one, any suggestion is appreciated!

mepp · October 23, 2018, 4:04pm

Few questions to start

What Deadline 10 version are you on?
What Maya version are you on?

Do you have any render logs you can share?

Is this a specific scene? Or is this for all your scenes? Can you reproduce this in a fresh test scene that you could pass over to us?

If you save that scene file as a Maya Binary (.mb) file and submit a new job with that, does it change anything?

Cheers

eamsler · October 23, 2018, 4:51pm

The reason for Morgan’s questions (and please do answer them!) is that “Cannot load scene” can be for many reasons. For example, if you’ve applied Product Update 4 to your workstations but not your nodes, Maya won’t understand the file format and it’ll fail to load.

With those answers for the questions above (especially a job report) we’ll be able to get a better idea why it failed.

AlexV · October 23, 2018, 5:47pm

Thanks for the fast replies guys!

We’re on Deadline 10.0.20.2
Maya 2018.2

This affects all our scenes currently. This is one of the recently failed error logs, slightly edited path names but the overall error message is still complete. I’ll do the other tests throughout the day as I find time for them.

Error: Error: file: C:/Users/AERender/AppData/Local/Temp/tmp69B8.tmp line 43: Cannot load scene "Y:/DRIVE/project/lighting/light_rigs/light_rig_v010.ma". Please check the scene path, then try opening the scene on the machine which ran this job to troubleshoot the problem.
   at Deadline.Plugins.PluginWrapper.RenderTasks(String taskId, Int32 startFrame, Int32 endFrame, String& outMessage, AbortLevel& abortLevel)

=======================================================
Type
=======================================================
RenderPluginException

=======================================================
Stack Trace
=======================================================
   at Deadline.Plugins.SandboxedPlugin.d(DeadlineMessage aog)
   at Deadline.Plugins.SandboxedPlugin.RenderTask(String taskId, Int32 startFrame, Int32 endFrame)
   at Deadline.Slaves.SlaveRenderThread.c(TaskLogWriter aem)

=======================================================
Log
=======================================================
2018-10-21 10:46:13:  0: Plugin will be reloaded because a new job has been loaded.
2018-10-21 10:46:13:  0: Loading Job's Plugin timeout is Disabled
2018-10-21 10:46:15:  0: Loaded plugin MayaBatch
2018-10-21 10:46:15:  0: Executing plugin command of type 'Sync Files for Job'
2018-10-21 10:46:15:  0: All job files are already synchronized
2018-10-21 10:46:15:  0: Synchronizing Plugin MayaBatch from \\DEADLINESERVER\DeadlineRepository10\plugins\MayaBatch took: 0 seconds
2018-10-21 10:46:15:  0: Done executing plugin command of type 'Sync Files for Job'
2018-10-21 10:46:15:  0: Executing plugin command of type 'Initialize Plugin'
2018-10-21 10:46:16:  0: INFO: Executing plugin script 'C:\Users\AERender\AppData\Local\Thinkbox\Deadline10\slave\render04\plugins\5bccbb5d4f3e963d3c4e53ba\MayaBatch.py'
2018-10-21 10:46:16:  0: INFO: About: Maya Batch Plugin for Deadline
2018-10-21 10:46:16:  0: INFO: Render Job As User disabled, running as current user 'AERender'
2018-10-21 10:46:16:  0: INFO: The job's environment will be merged with the current environment before rendering
2018-10-21 10:46:16:  0: Done executing plugin command of type 'Initialize Plugin'
2018-10-21 10:46:16:  0: Start Job timeout is disabled.
2018-10-21 10:46:16:  0: Task timeout is disabled.
2018-10-21 10:46:16:  0: Loaded job: light_rig_v010 - rs_rs_parker_grunge (5bccbb5d4f3e963d3c4e53ba)
2018-10-21 10:46:16:  0: Successfully mapped Y: to //keaton/Current Projects
2018-10-21 10:46:16:  0: Executing plugin command of type 'Start Job'
2018-10-21 10:46:16:  0: INFO: Executing global asset transfer preload script 'C:\Users\AERender\AppData\Local\Thinkbox\Deadline10\slave\render04\plugins\5bccbb5d4f3e963d3c4e53ba\GlobalAssetTransferPreLoad.py'
2018-10-21 10:46:16:  0: INFO: Looking for AWS Portal File Transfer...
2018-10-21 10:46:16:  0: INFO: Looking for File Transfer controller in C:/Program Files/Thinkbox/S3BackedCache/bin/task.py...
2018-10-21 10:46:16:  0: INFO: Could not find AWS Portal File Transfer.
2018-10-21 10:46:16:  0: INFO: AWS Portal File Transfer is not installed on the system.
2018-10-21 10:46:16:  0: INFO: Rendering with Maya Version 2018.0
2018-10-21 10:46:16:  0: INFO: Setting MAYA_DEBUG_ENABLE_CRASH_REPORTING environment variable to 0 for this session. Set to 1 if you need Maya debug log
2018-10-21 10:46:16:  0: INFO: Setting MAYA_DISABLE_CIP (ADSK Customer Involvement Program) environment variable to 1 for this session
2018-10-21 10:46:16:  0: INFO: Setting MAYA_DISABLE_CER (ADSK Customer Error Reporting) environment variable to 1 for this session
2018-10-21 10:46:16:  0: INFO: Setting MAYA_DISABLE_CLIC_IPM (ADSK In Product Messaging) environment variable to 1 for this session
2018-10-21 10:46:16:  0: INFO: Setting MAYA_OPENCL_IGNORE_DRIVER_VERSION environment variable to 1 for this session
2018-10-21 10:46:16:  0: INFO: Setting MAYA_VP2_DEVICE_OVERRIDE environment variable to VirtualDeviceDx11 for this session
2018-10-21 10:46:16:  0: INFO: Setting MAYA_ENABLE_LEGACY_RENDER_LAYERS environment variable to 0 for this session
2018-10-21 10:46:16:  0: INFO: Enforcing 64 bit build of Maya
2018-10-21 10:46:16:  0: INFO: Setting PYTHONHOME to C:\Program Files\Autodesk\Maya2018\Python for this session
2018-10-21 10:46:16:  0: INFO: Starting monitored managed process MayaBatch
2018-10-21 10:46:16:  0: INFO: Stdout Redirection Enabled: True
2018-10-21 10:46:16:  0: INFO: Stdout Handling Enabled: True
2018-10-21 10:46:16:  0: INFO: Popup Handling Enabled: True
2018-10-21 10:46:16:  0: INFO: QT Popup Handling Enabled: False
2018-10-21 10:46:16:  0: INFO: WindowsForms10.Window.8.app.* Popup Handling Enabled: False
2018-10-21 10:46:16:  0: INFO: Using Process Tree: True
2018-10-21 10:46:16:  0: INFO: Hiding DOS Window: True
2018-10-21 10:46:16:  0: INFO: Creating New Console: False
2018-10-21 10:46:16:  0: INFO: Running as user: AERender
2018-10-21 10:46:16:  0: INFO: Enforcing 64 bit build of Maya
2018-10-21 10:46:16:  0: INFO: Executable: "C:\Program Files\Autodesk\Maya2018\bin\MayaBatch.exe"
2018-10-21 10:46:16:  0: INFO: Argument: -prompt -file "Y:\DRIVE\project\lighting\light_rigs\light_rig_v010.ma" -proj "Y:/DRIVE/project/seq/sq1000/sh0120/light"
2018-10-21 10:46:16:  0: INFO: Full Command: "C:\Program Files\Autodesk\Maya2018\bin\MayaBatch.exe" -prompt -file "Y:\DRIVE\project\lighting\light_rigs\light_rig_v010.ma" -proj "Y:/DRIVE/project/seq/sq1000/sh0120/light"
2018-10-21 10:46:16:  0: INFO: Startup Directory: "C:\Program Files\Autodesk\Maya2018\bin"
2018-10-21 10:46:16:  0: INFO: Process Priority: BelowNormal
2018-10-21 10:46:16:  0: INFO: Process Affinity: default
2018-10-21 10:46:16:  0: INFO: Process is now running
2018-10-21 10:46:16:  0: Done executing plugin command of type 'Start Job'
2018-10-21 10:46:16:  0: Plugin rendering frame(s): 2
2018-10-21 10:46:17:  0: Executing plugin command of type 'Render Task'
2018-10-21 10:46:17:  0: INFO: Waiting until maya is ready to go
2018-10-21 10:46:23:  0: WARNING: Strict error checking on, ignoring the following unrecognized error or warning. If it is fatal, please email support@thinkboxsoftware.com with the error message.
2018-10-21 10:46:23:  0: STDOUT: Error: file: Y:/DRIVE/project/lighting/light_rigs/light_rig_v010.ma line 17: RuntimeError: file <maya console> line 1: Plug-in, "3delight_for_maya2012", was not found on MAYA_PLUG_IN_PATH.
2018-10-21 10:46:23:  0: WARNING: Strict error checking on, ignoring the following unrecognized error or warning. If it is fatal, please email support@thinkboxsoftware.com with the error message.
2018-10-21 10:46:23:  0: STDOUT: Error: file: Y:/DRIVE/project/lighting/light_rigs/light_rig_v010.ma line 18: RuntimeError: file <maya console> line 1: Plug-in, "lalAsset", was not found on MAYA_PLUG_IN_PATH.
2018-10-21 10:46:23:  0: WARNING: Strict error checking on, ignoring the following unrecognized error or warning. If it is fatal, please email support@thinkboxsoftware.com with the error message.
2018-10-21 10:46:23:  0: STDOUT: Error: file: Y:/DRIVE/project/lighting/light_rigs/light_rig_v010.ma line 19: RuntimeError: file <maya console> line 1: Plug-in, "rotatorNode.py", was not found on MAYA_PLUG_IN_PATH.
2018-10-21 10:46:23:  0: WARNING: Strict error checking on, ignoring the following unrecognized error or warning. If it is fatal, please email support@thinkboxsoftware.com with the error message.
2018-10-21 10:46:23:  0: STDOUT: Error: file: Y:/DRIVE/project/lighting/light_rigs/light_rig_v010.ma line 126432: The camera 'hdr_fill_rim:cameraShape1' has no '.rsStereoSphericalSeparation' attribute.
2018-10-21 10:46:23:  0: WARNING: Strict error checking on, ignoring the following unrecognized error or warning. If it is fatal, please email support@thinkboxsoftware.com with the error message.
2018-10-21 10:46:23:  0: STDOUT: Error: file: Y:/DRIVE/project/lighting/light_rigs/light_rig_v010.ma line 126432: setAttr: No object matches name: .rsStereoSphericalSeparation
2018-10-21 10:46:23:  0: WARNING: Strict error checking on, ignoring the following unrecognized error or warning. If it is fatal, please email support@thinkboxsoftware.com with the error message.
2018-10-21 10:46:23:  0: STDOUT: Error: file: Y:/DRIVE/project/lighting/light_rigs/light_rig_v010.ma line 126433: The camera 'hdr_fill_rim:cameraShape1' has no '.rsStereoSphericalFocusDistance' attribute.
2018-10-21 10:46:23:  0: WARNING: Strict error checking on, ignoring the following unrecognized error or warning. If it is fatal, please email support@thinkboxsoftware.com with the error message.
2018-10-21 10:46:23:  0: STDOUT: Error: file: Y:/DRIVE/project/lighting/light_rigs/light_rig_v010.ma line 126433: setAttr: No object matches name: .rsStereoSphericalFocusDistance
2018-10-21 10:46:23:  0: WARNING: Strict error checking on, ignoring the following unrecognized error or warning. If it is fatal, please email support@thinkboxsoftware.com with the error message.
2018-10-21 10:46:23:  0: STDOUT: Error: file: Y:/DRIVE/project/lighting/light_rigs/light_rig_v010.ma line 126434: The camera 'hdr_fill_rim:cameraShape1' has no '.rsStereoCubeSeparation' attribute.
2018-10-21 10:46:23:  0: WARNING: Strict error checking on, ignoring the following unrecognized error or warning. If it is fatal, please email support@thinkboxsoftware.com with the error message.
2018-10-21 10:46:23:  0: STDOUT: Error: file: Y:/DRIVE/project/lighting/light_rigs/light_rig_v010.ma line 126434: setAttr: No object matches name: .rsStereoCubeSeparation
2018-10-21 10:46:23:  0: WARNING: Strict error checking on, ignoring the following unrecognized error or warning. If it is fatal, please email support@thinkboxsoftware.com with the error message.
2018-10-21 10:46:23:  0: STDOUT: Warning: file: Y:/DRIVE/project/lighting/light_rigs/light_rig_v010.ma line 128464: Unrecognized node type 'polyDisc'; preserving node information during this session.
2018-10-21 10:46:23:  0: WARNING: Strict error checking on, ignoring the following unrecognized error or warning. If it is fatal, please email support@thinkboxsoftware.com with the error message.
2018-10-21 10:46:23:  0: STDOUT: Warning: line 1: Errors have occurred while reading this scene that may result in data loss.
2018-10-21 10:46:23:  0: STDOUT: File read in  1.1 seconds.
2018-10-21 10:46:23:  0: STDOUT: File read in  1.1 seconds.
2018-10-21 10:46:23:  0: WARNING: Strict error checking on, ignoring the following unrecognized error or warning. If it is fatal, please email support@thinkboxsoftware.com with the error message.
2018-10-21 10:46:23:  0: STDOUT: Error: line 1: Error reading file.
2018-10-21 10:46:24:  0: WARNING: Strict error checking on, ignoring the following unrecognized error or warning. If it is fatal, please email support@thinkboxsoftware.com with the error message.
2018-10-21 10:46:24:  0: STDOUT: Error: line 1: Error reading file.
2018-10-21 10:46:24:  0: STDOUT: mel: READY FOR INPUT
2018-10-21 10:46:24:  0: INFO: Importing Maya Batch Utils melscript: C:\Users\AERender\AppData\Local\Thinkbox\Deadline10\slave\render04\plugins\5bccbb5d4f3e963d3c4e53ba\MayaBatchUtils.mel
2018-10-21 10:46:25:  0: INFO: Waiting for Maya Batch Utils melscript to finish loading
2018-10-21 10:46:25:  0: STDOUT: mel: mel: READY FOR INPUT
2018-10-21 10:46:26:  0: INFO: Importing Maya Batch Functions python script: C:\Users\AERender\AppData\Local\Thinkbox\Deadline10\slave\render04\plugins\5bccbb5d4f3e963d3c4e53ba\DeadlineMayaBatchFunctions.py
2018-10-21 10:46:26:  0: INFO: Waiting for Maya Batch Functions python script to finish importing
2018-10-21 10:46:26:  0: STDOUT: mel: Result: 0
2018-10-21 10:46:27:  0: STDOUT: mel: READY FOR INPUT
2018-10-21 10:46:27:  0: INFO: >This is a Render Job
2018-10-21 10:46:27:  0: INFO: Rendering with arnold
2018-10-21 10:46:27:  0: INFO: Rendering to network drive
2018-10-21 10:46:27:  0: INFO: Creating melscript to execute render
2018-10-21 10:46:27:  0: INFO: Executing script: C:\Users\AERender\AppData\Local\Temp\tmp69B8.tmp
2018-10-21 10:46:28:  0: INFO: Waiting for script to finish
2018-10-21 10:46:28:  0: STDOUT: mel: Loading scene: Y:/DRIVE/project/lighting/light_rigs/light_rig_v010.ma
2018-10-21 10:46:28:  0: STDOUT: Error: file: C:/Users/AERender/AppData/Local/Temp/tmp69B8.tmp line 43: Cannot load scene "Y:/DRIVE/project/lighting/light_rigs/light_rig_v010.ma". Please check the scene path, then try opening the scene on the machine which ran this job to troubleshoot the problem.
2018-10-21 10:46:28:  0: Done executing plugin command of type 'Render Task'
2018-10-21 10:46:28:  0: An exception occurred: Error: Error: file: C:/Users/AERender/AppData/Local/Temp/tmp69B8.tmp line 43: Cannot load scene "Y:/DRIVE/project/lighting/light_rigs/light_rig_v010.ma". Please check the scene path, then try opening the scene on the machine which ran this job to troubleshoot the problem.
2018-10-21 10:46:28:     at Deadline.Plugins.PluginWrapper.RenderTasks(String taskId, Int32 startFrame, Int32 endFrame, String& outMessage, AbortLevel& abortLevel) (Deadline.Plugins.RenderPluginException)

eamsler · October 24, 2018, 2:47pm

Perfect! Best guess now:

Likely Deadline is running as a service, or your file server rebooted. In both cases, the “Y:” drive is likely unreachable. Best fix: Set up drive mapping so Deadline can (re)map those drives for you.

AlexV · October 26, 2018, 10:45pm

We had already tried all of that.

In the end we decided to run the Deadline update to the 10.0.21.5 version on all the machines and that fixed it temporarily, but now it’s been periodically coming back without us being able to pin it on a specific node or Workstation.

Still wondering how that happened though

eamsler · October 29, 2018, 10:01pm

Well, that error is coming from Maya and Deadline’s version shouldn’t matter here, but stranger things have happened.

If it’s intermittent, I usually find that it’s caused by performance between either the disks serving the assets out to the network or the network itself. We hit this often when we multi-threaded Krakatoa and killed people’s networks. You can usually confirm/deny that by checking your network gear if it’s a managed solution. It should have a section to show how many packets were dropped.

As a test, in Deadline you can try setting up a “fileserver” limit and assign it to all of your jobs as sort of a throttling mechanism. There’s an option to limit to a certain number of machines, but to release their stubs after a certain render percentage. That will guarantee they’ve loaded at least most of their files and have started rendering before another machine is allowed to take their place.