error "Cannot load scene. Please check the scene name. "

Deadline
1

Hello,

We are setting up a render cluster with Deadline. Currently we have 3 test render nodes . All of them have DeadlineRepository attached as network disk z:/ . during the rendering we are receiving the error Error: line 1: File not found: “Z:/input/The_Kings_Treasure.mb” and "Cannot load scene. Please check the scene name. "
We can’t handle this issue . File “Z:/input/The_Kings_Treasure.mb” exists and we can access it via Explorer. All render nodes have Windows 7 Operating System, Maya 2016 with arnold and Deadline 7.1 Please help with this issue. If any questions occur, please let us know. Detailed output you can find below:

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

Error: Strict error checking on, caught the following error or warning.
mel: Error: file: C:/Users/admin/AppData/Local/Temp/tmp713.tmp line 39: Cannot load scene. Please check the scene name.
If this error message is unavoidable but not fatal, please email support@thinkboxsoftware.com with the error message, and disable the Maya job setting Strict Error Checking.
at Deadline.Plugins.ScriptPlugin.RenderTasks(String taskId, Int32 startFrame, Int32 endFrame, String& outMessage, AbortLevel& abortLevel)

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

RenderPluginException

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

at Deadline.Plugins.Plugin.RenderTask(String taskId, Int32 startFrame, Int32 endFrame)
at Deadline.Slaves.SlaveRenderThread.a(TaskLogWriter A_0)

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

2015-06-01 15:30:08: BEGIN - RENDER3\admin
2015-06-01 15:30:08: 0: Start Job timeout is disabled.
2015-06-01 15:30:08: 0: Task timeout is disabled.
2015-06-01 15:30:08: 0: Loaded job: Untitled (556cdcc3f9a41c13747b20ad)
2015-06-01 15:30:08: 0: INFO: Executing plugin script C:\Users\admin\AppData\Local\Thinkbox\Deadline7\slave\render3\plugins\556cdcc3f9a41c13747b20ad\MayaBatch.py
2015-06-01 15:30:08: 0: INFO: About: Maya Batch Plugin for Deadline
2015-06-01 15:30:08: 0: INFO: The job’s environment will be merged with the current environment before rendering
2015-06-01 15:30:08: 0: INFO: Rendering with Maya version 2016.0
2015-06-01 15:30:08: 0: INFO: Not enforcing a build of Maya
2015-06-01 15:30:08: 0: INFO: Setting PYTHONHOME to C:\Program Files\Autodesk\Maya2016\Python for this session
2015-06-01 15:30:08: 0: INFO: Starting monitored managed process MayaBatch
2015-06-01 15:30:08: 0: INFO: Stdout Handling Enabled: True
2015-06-01 15:30:08: 0: INFO: Popup Handling Enabled: True
2015-06-01 15:30:08: 0: INFO: QT Popup Handling Enabled: False
2015-06-01 15:30:08: 0: INFO: WindowsForms10.Window.8.app.* Popup Handling Enabled: False
2015-06-01 15:30:08: 0: INFO: Using Process Tree: True
2015-06-01 15:30:08: 0: INFO: Hiding DOS Window: True
2015-06-01 15:30:08: 0: INFO: Creating New Console: False
2015-06-01 15:30:08: 0: INFO: Running as user: admin
2015-06-01 15:30:08: 0: INFO: Not enforcing a build of Maya
2015-06-01 15:30:08: 0: INFO: Executable: “C:\Program Files\Autodesk\Maya2016\bin\MayaBatch.exe”
2015-06-01 15:30:08: 0: INFO: Argument: -prompt -file “Z:\input\The_Kings_Treasure.mb” -proj “Z:/input”
2015-06-01 15:30:08: 0: INFO: Startup Directory: “C:\Program Files\Autodesk\Maya2016\bin”
2015-06-01 15:30:08: 0: INFO: Process Priority: BelowNormal
2015-06-01 15:30:08: 0: INFO: Process Affinity: default
2015-06-01 15:30:08: 0: INFO: Process is now running
2015-06-01 15:30:08: 0: Plugin rendering frame(s): 1
2015-06-01 15:30:09: 0: INFO: Waiting until maya is ready to go
2015-06-01 15:30:11: 0: STDOUT: Initialized VP2.0 renderer {
2015-06-01 15:30:11: 0: STDOUT: Version : 6.3.16.0. Feature Level 5.
2015-06-01 15:30:11: 0: STDOUT: Adapter :
2015-06-01 15:30:11: 0: STDOUT: Vendor ID: 0. Device ID :
2015-06-01 15:30:11: 0: STDOUT: Driver : .
2015-06-01 15:30:11: 0: STDOUT: API : DirectX V.11. Using software WARP device due to failure to obtain a hardware device
2015-06-01 15:30:11: 0: STDOUT: Max texture size : 16384 * 16384.
2015-06-01 15:30:11: 0: STDOUT: Max tex coords : 32
2015-06-01 15:30:11: 0: STDOUT: Shader versions supported (Vertex: 5, Geometry: 5, Pixel 5).
2015-06-01 15:30:11: 0: STDOUT: Active stereo support available : 0
2015-06-01 15:30:11: 0: STDOUT: GPU Memory Limit : 3836.16 MB.
2015-06-01 15:30:11: 0: STDOUT: CPU Memory Limit: 5835.71 MB.
2015-06-01 15:30:12: 0: STDOUT: }
2015-06-01 15:30:12: 0: STDOUT: OpenCL evaluator is attempting to initialize OpenCL.
2015-06-01 15:30:12: 0: STDOUT: OpenCL evaluator failed to initialize clew.
2015-06-01 15:30:14: 0: STDOUT: 00:00:00 257MB ERROR | [mtoa] [xgenTranslator] Could not find xgen_procedural in search path $ARNOLD_PLUGIN_PATH
2015-06-01 15:30:16: 0: STDOUT: pymel.core : INFO : Updating pymel with pre-loaded plugins: mayaHIK, GamePipeline, CloudImportExport, tiffFloatReader, bifrostvisplugin, ikSpringSolver, ik2Bsolver, xgenToolkit, AbcExport, retargeterNodes, gameFbxExporter, VectorRender, OpenEXRLoader, Unfold3D, mayaCharacterization, mtoa, fbxmaya
2015-06-01 15:30:16: 0: STDOUT: xgmNurbsPatch [u’containerBase’, u’entity’, u’dagNode’, u’shape’, u’geometryShape’, u’deformableShape’, u’controlPoint’, u’surfaceShape’, u’THsurfaceShape’, u’xgmPatch’, u’containerBase’, u’entity’, u’dagNode’, u’shape’, u’geometryShape’, u’deformableShape’, u’controlPoint’, u’surfaceShape’, u’THsurfaceShape’, u’xgmNurbsPatch’]
2015-06-01 15:30:16: 0: STDOUT: pymel.internal.apicache : WARNING : lineage for node xgmNurbsPatch is cyclical: [u’containerBase’, u’entity’, u’dagNode’, u’shape’, u’geometryShape’, u’deformableShape’, u’controlPoint’, u’surfaceShape’, u’THsurfaceShape’, u’xgmPatch’, u’containerBase’, u’entity’, u’dagNode’, u’shape’, u’geometryShape’, u’deformableShape’, u’controlPoint’, u’surfaceShape’, u’THsurfaceShape’, u’xgmNurbsPatch’]
2015-06-01 15:30:16: 0: STDOUT: xgmSubdPatch [u’containerBase’, u’entity’, u’dagNode’, u’shape’, u’geometryShape’, u’deformableShape’, u’controlPoint’, u’surfaceShape’, u’THsurfaceShape’, u’xgmPatch’, u’containerBase’, u’entity’, u’dagNode’, u’shape’, u’geometryShape’, u’deformableShape’, u’controlPoint’, u’surfaceShape’, u’THsurfaceShape’, u’xgmSubdPatch’]
2015-06-01 15:30:16: 0: STDOUT: pymel.internal.apicache : WARNING : lineage for node xgmSubdPatch is cyclical: [u’containerBase’, u’entity’, u’dagNode’, u’shape’, u’geometryShape’, u’deformableShape’, u’controlPoint’, u’surfaceShape’, u’THsurfaceShape’, u’xgmPatch’, u’containerBase’, u’entity’, u’dagNode’, u’shape’, u’geometryShape’, u’deformableShape’, u’controlPoint’, u’surfaceShape’, u’THsurfaceShape’, u’xgmSubdPatch’]
2015-06-01 15:30:16: 0: STDOUT: xgmArchiveGuide [u’containerBase’, u’entity’, u’dagNode’, u’shape’, u’geometryShape’, u’deformableShape’, u’controlPoint’, u’surfaceShape’, u’THsurfaceShape’, u’xgmGuide’, u’containerBase’, u’entity’, u’dagNode’, u’shape’, u’geometryShape’, u’deformableShape’, u’controlPoint’, u’surfaceShape’, u’THsurfaceShape’, u’xgmArchiveGuide’]
2015-06-01 15:30:16: 0: STDOUT: pymel.internal.apicache : WARNING : lineage for node xgmArchiveGuide is cyclical: [u’containerBase’, u’entity’, u’dagNode’, u’shape’, u’geometryShape’, u’deformableShape’, u’controlPoint’, u’surfaceShape’, u’THsurfaceShape’, u’xgmGuide’, u’containerBase’, u’entity’, u’dagNode’, u’shape’, u’geometryShape’, u’deformableShape’, u’controlPoint’, u’surfaceShape’, u’THsurfaceShape’, u’xgmArchiveGuide’]
2015-06-01 15:30:16: 0: STDOUT: xgmCardGuide [u’containerBase’, u’entity’, u’dagNode’, u’shape’, u’geometryShape’, u’deformableShape’, u’controlPoint’, u’surfaceShape’, u’THsurfaceShape’, u’xgmGuide’, u’containerBase’, u’entity’, u’dagNode’, u’shape’, u’geometryShape’, u’deformableShape’, u’controlPoint’, u’surfaceShape’, u’THsurfaceShape’, u’xgmCardGuide’]
2015-06-01 15:30:16: 0: STDOUT: pymel.internal.apicache : WARNING : lineage for node xgmCardGuide is cyclical: [u’containerBase’, u’entity’, u’dagNode’, u’shape’, u’geometryShape’, u’deformableShape’, u’controlPoint’, u’surfaceShape’, u’THsurfaceShape’, u’xgmGuide’, u’containerBase’, u’entity’, u’dagNode’, u’shape’, u’geometryShape’, u’deformableShape’, u’controlPoint’, u’surfaceShape’, u’THsurfaceShape’, u’xgmCardGuide’]
2015-06-01 15:30:16: 0: STDOUT: xgmSphereGuide [u’containerBase’, u’entity’, u’dagNode’, u’shape’, u’geometryShape’, u’deformableShape’, u’controlPoint’, u’surfaceShape’, u’THsurfaceShape’, u’xgmGuide’, u’containerBase’, u’entity’, u’dagNode’, u’shape’, u’geometryShape’, u’deformableShape’, u’controlPoint’, u’surfaceShape’, u’THsurfaceShape’, u’xgmSphereGuide’]
2015-06-01 15:30:16: 0: STDOUT: pymel.internal.apicache : WARNING : lineage for node xgmSphereGuide is cyclical: [u’containerBase’, u’entity’, u’dagNode’, u’shape’, u’geometryShape’, u’deformableShape’, u’controlPoint’, u’surfaceShape’, u’THsurfaceShape’, u’xgmGuide’, u’containerBase’, u’entity’, u’dagNode’, u’shape’, u’geometryShape’, u’deformableShape’, u’controlPoint’, u’surfaceShape’, u’THsurfaceShape’, u’xgmSphereGuide’]
2015-06-01 15:30:16: 0: STDOUT: xgmSplineGuide [u’containerBase’, u’entity’, u’dagNode’, u’shape’, u’geometryShape’, u’deformableShape’, u’controlPoint’, u’surfaceShape’, u’THsurfaceShape’, u’xgmGuide’, u’containerBase’, u’entity’, u’dagNode’, u’shape’, u’geometryShape’, u’deformableShape’, u’controlPoint’, u’surfaceShape’, u’THsurfaceShape’, u’xgmSplineGuide’]
2015-06-01 15:30:16: 0: STDOUT: pymel.internal.apicache : WARNING : lineage for node xgmSplineGuide is cyclical: [u’containerBase’, u’entity’, u’dagNode’, u’shape’, u’geometryShape’, u’deformableShape’, u’controlPoint’, u’surfaceShape’, u’THsurfaceShape’, u’xgmGuide’, u’containerBase’, u’entity’, u’dagNode’, u’shape’, u’geometryShape’, u’deformableShape’, u’controlPoint’, u’surfaceShape’, u’THsurfaceShape’, u’xgmSplineGuide’]
2015-06-01 15:30:16: 0: STDOUT: aiSkyDomeLight [u’containerBase’, u’entity’, u’dagNode’, u’shape’, u’geometryShape’, u’locator’, u’THlocatorShape’, u’SphereLocator’, u’containerBase’, u’entity’, u’dagNode’, u’shape’, u’geometryShape’, u’locator’, u’THlocatorShape’, u’aiSkyDomeLight’]
2015-06-01 15:30:16: 0: STDOUT: pymel.internal.apicache : WARNING : lineage for node aiSkyDomeLight is cyclical: [u’containerBase’, u’entity’, u’dagNode’, u’shape’, u’geometryShape’, u’locator’, u’THlocatorShape’, u’SphereLocator’, u’containerBase’, u’entity’, u’dagNode’, u’shape’, u’geometryShape’, u’locator’, u’THlocatorShape’, u’aiSkyDomeLight’]
2015-06-01 15:30:16: 0: STDOUT: aiSky [u’containerBase’, u’entity’, u’dagNode’, u’shape’, u’geometryShape’, u’locator’, u’THlocatorShape’, u’SphereLocator’, u’containerBase’, u’entity’, u’dagNode’, u’shape’, u’geometryShape’, u’locator’, u’THlocatorShape’, u’aiSky’]
2015-06-01 15:30:16: 0: STDOUT: pymel.internal.apicache : WARNING : lineage for node aiSky is cyclical: [u’containerBase’, u’entity’, u’dagNode’, u’shape’, u’geometryShape’, u’locator’, u’THlocatorShape’, u’SphereLocator’, u’containerBase’, u’entity’, u’dagNode’, u’shape’, u’geometryShape’, u’locator’, u’THlocatorShape’, u’aiSky’]
2015-06-01 15:30:16: 0: STDOUT: Maya 2016 importing module pymel 1.0.7 (C:\Program Files\Autodesk\Maya2016\Python\lib\site-packages\pymel_init_.pyc)
2015-06-01 15:30:21: 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.
2015-06-01 15:30:21: 0: STDOUT: Error: line 1: File not found: “Z:/input/The_Kings_Treasure.mb”
2015-06-01 15:30:21: 0: STDOUT: mel: READY FOR INPUT
2015-06-01 15:30:21: 0: INFO: Rendering with arnold
2015-06-01 15:30:21: 0: INFO: Rendering to network drive
2015-06-01 15:30:21: 0: INFO: Creating melscript to execute
2015-06-01 15:30:21: 0: INFO: Executing script: C:\Users\admin\AppData\Local\Temp\tmp713.tmp
2015-06-01 15:30:22: 0: INFO: Waiting for script to finish
2015-06-01 15:30:22: 0: STDOUT: mel: Error: file: C:/Users/admin/AppData/Local/Temp/tmp713.tmp line 39: Cannot load scene. Please check the scene name.

2

Hello,

I’ve answered your support ticket, and when we get to the answer, I’ll post it here.

3

We are getting a similar issue with Windows 7 clients, Maya 2014 and Deadline 7.1.0.35.

Was there a resolution to this?

Thanks

2015-06-11 12:36:34: 0: INFO: Auto memory detection for VRay disabled 2015-06-11 12:36:34: 0: INFO: Executing script: C:\Users\render\AppData\Local\Temp\tmpEB58.tmp 2015-06-11 12:36:35: 0: INFO: Waiting for script to finish 2015-06-11 12:36:36: 0: STDOUT: mel: Error: file: C:/Users/render/AppData/Local/Temp/tmpEB58.tmp line 39: Cannot load scene. Please check the scene name.

4

Hello,

Could you share here, or via the ticket system, the full job report? If you would rather share it via the ticket system just save out the job report and send it to support@thinkboxsoftware.com and reference this post. Thanks.

5

We run into this on Linux with random slaves, seemingly after they have been freshly rebooted. We are using a completely custom job plugin and render stack though, so it may not be related, but I would still love to know what the outcome of this ends up being in case it somehow applies to our situation as well.

6

Most often when we see this error, there is either something wrong in the scene which prevents if from loading, or the scene cannot be accessed. Running with MayaBatch off can often get the command used, which can be run from the command line to see how the scene runs on the slave outside of Deadline, and often enlightens the user to the actual issue.

7

had today a problem with xgen, vray and motionblur…
looks like if we use “submit maya scene” the xgen stuff is left behind…

unticking “submit maya scene file” solved the problem…
just a note…