Maya 2013 massive error messages

Hi there,
we have changed to deadline 5.2, using Maya 2013 with mentalray, opened an 2012-scene in Maya 2013, local rendering runs normal, if I render (up to 4 renderlayer) at the renderfarm, these errormessages apear (See also snapshot) - at the end the most frames are rendered ready, but some frames are not:

Error Message

Exception during render: An error occurred in RenderTasks(): Monitored managed process “MayaBatch” has exited or been terminated.
bei Deadline.Plugins.ScriptPlugin.RenderTasks(String taskId, Int32 startFrame, Int32 endFrame, String& outMessage)

=======================================================
Slave Log

3: Task timeout is disabled.
3: Loaded job: S02_HD - Cut1 (000_050_999_1c1258f4)
3: INFO: StartJob: initializing script plugin MayaBatch
3: INFO: About: Maya Batch Plugin for Deadline
3: INFO: Rendering with Maya version 2013.0
3: INFO: Starting monitored managed process MayaBatch
3: INFO: Any stdout that matches the regular expression “READY FOR INPUT” will be handled as appropriate
3: INFO: Any stdout that matches the regular expression “FLEXlm error: ." will be handled as appropriate
3: INFO: Any stdout that matches the regular expression “.3DL ERROR .” will be handled as appropriate
3: INFO: Any stdout that matches the regular expression "[\d+.?\d
\d+.?\d* \d+.?\d*]” will be handled as appropriate
3: INFO: Any stdout that matches the regular expression “Finished Rendering..([0-9]+).[^.]+" will be handled as appropriate
3: INFO: Any stdout that matches the regular expression “.Finished Rendering.” will be handled as appropriate
3: INFO: Any stdout that matches the regular expression “Constructing shading groups|Rendering current frame” will be handled as appropriate
3: INFO: Any stdout that matches the regular expression “.Error: .|.Warning: .” will be handled as appropriate
3: INFO: Any stdout that matches the regular expression “progr: +([0-9]+.[0-9]+)% +rendered” will be handled as appropriate
3: INFO: Any stdout that matches the regular expression “progr: +([0-9]+.[0-9]+)% +computing final gather points” will be handled as appropriate
3: INFO: Any stdout that matches the regular expression "progr: writing image file .
(frame ([0-9]+))” will be handled as appropriate
3: INFO: Any stdout that matches the regular expression “progr: +rendering finished” will be handled as appropriate
3: INFO: Any stdout that matches the regular expression “| render done” will be handled as appropriate
3: INFO: Any stdout that matches the regular expression “[PROGRESS] Completed frame*” will be handled as appropriate
3: INFO: Any stdout that matches the regular expression “.[PROGRESS] TURTLE rendering frame 100.00.” will be handled as appropriate
3: INFO: Any stdout that matches the regular expression “.Render complete.” will be handled as appropriate
3: INFO: Any stdout that matches the regular expression “[PROGRESS] Percentage of rendering done: (.)" will be handled as appropriate
3: INFO: Any stdout that matches the regular expression ".
[PROGRESS] TURTLE rendering frame ([0-9]+.[0-9]+)." will be handled as appropriate
3: INFO: Any stdout that matches the regular expression “.RIMG : +([0-9]+)%" will be handled as appropriate
3: INFO: Any stdout that matches the regular expression "V-Ray: Building light cache
” will be handled as appropriate
3: INFO: Any stdout that matches the regular expression "V-Ray: Prepass ([0-9]+) of ([0-9]+)
” will be handled as appropriate
3: INFO: Any stdout that matches the regular expression “V-Ray: Rendering image*” will be handled as appropriate
3: INFO: Any stdout that matches the regular expression “V-Ray: +([0-9]+)%” will be handled as appropriate
3: INFO: Any stdout that matches the regular expression “V-Ray: +([0-9]+) %” will be handled as appropriate
3: INFO: Any stdout that matches the regular expression “([0-9]+) % completed” will be handled as appropriate
3: INFO: Any stdout that matches the regular expression “V-Ray: Total frame time” will be handled as appropriate
3: INFO: Any stdout that matches the regular expression “V-Ray: Updating frame at time ([0-9]+)” will be handled as appropriate
3: INFO: Any stdout that matches the regular expression “V-Ray: Render complete” will be handled as appropriate
3: INFO: Any stdout that matches the regular expression “rfm Notice: Rendering .* at ([0-9]+)” will be handled as appropriate
3: INFO: Any stdout that matches the regular expression “[PROGRESS] ([0-9]+) percent” will be handled as appropriate
3: INFO: Any stdout that matches the regular expression “([0-9]+)%” will be handled as appropriate
3: INFO: Any popup windows with titles matching the regular expression “.entry point.” will be ignored
3: INFO: Any popup windows with titles matching the regular expression “.Entry Point.” will be ignored
3: INFO: Any popup windows with titles matching the regular expression “.Render history settings.” will be ignored
3: INFO: Any popup windows with titles matching the regular expression “.Render history note.” will be ignored
3: INFO: Stdout Handling Enabled: True
3: INFO: Popup Handling Enabled: True
3: INFO: Using Process Tree: True
3: INFO: Hiding DOS Window: True
3: INFO: Creating New Console: False
3: INFO: Enforcing 64 bit build of Maya
3: INFO: Render Executable: “C:\Program Files\Autodesk\Maya2013.5\bin\MayaBatch.exe”
3: INFO: Render Argument: -prompt -file “//gph3-server/Render/Maya/38_HG_Sodbrennen_2013/scenes/S02_HD.mb” -proj “//gph3-server/Render/Maya/38_HG_Sodbrennen_2013”
3: INFO: Startup Directory: “C:\Program Files\Autodesk\Maya2013.5\bin”
3: INFO: Process Priority: BelowNormal
3: INFO: Process Affinity: default
3: INFO: Process is now running
3: Plugin rendering frame(s): 611-620
3: INFO: Waiting until maya is ready to go
3: STDOUT: mental ray for Maya 2013
3: STDOUT: mental ray: version 3.10.1.11, Jul 26 2012, revision 177995
3: INFO: Deadline is ignoring error: “Warning: line 1: “dynGlobals1” already exists as a dynamics globals node. All other dynGlobals nodes will be ignored.” because plugin setting Strict Error Checking is enabled and this error is not usually fatal.
3: STDOUT: Warning: line 1: “dynGlobals1” already exists as a dynamics globals node. All other dynGlobals nodes will be ignored.
3: STDOUT: File read in 0 seconds.
3: STDOUT: Result: //gph3-server/Render/Maya/38_HG_Sodbrennen_2013/scenes/S02_HD.mb
3: STDOUT: mel: READY FOR INPUT
3: INFO: Rendering with mentalray
3: INFO: Rendering to network drive
3: INFO: Creating melscript to execute
3: INFO: Script contents:
3: INFO:
////////////////////////////////////////////////////////////////////////////
// Starting Mel program

proc renderIt(string $name) {

string $opt=""; string $rl=""; string $rp=""; int $renderThreads = 2; float $resize=-1.; miLoadMayatomr; miCreateDefaultNodes(); select defaultRenderGlobals; setAttr .renderAll 1;
removeRenderLayerAdjustmentAndUnlock .animation; setAttr .animation 1; removeRenderLayerAdjustmentAndUnlock .startFrame; setAttr .startFrame 611;
removeRenderLayerAdjustmentAndUnlock .animation; setAttr .animation 1; removeRenderLayerAdjustmentAndUnlock .endFrame; setAttr .endFrame 620;
removeRenderLayerAdjustmentAndUnlock .byFrameStep; catch(setAttr .byFrameStep 1);

removeRenderLayerAdjustmentAndUnlock .imageFilePrefix; catch(setAttr -type "string" .imageFilePrefix "<Scene>/<RenderLayer>/<Scene>_<RenderLayer>");
workspace -rt “images” “//gph3-server/Render/Maya/38_HG_Sodbrennen_2013/images”; workspace -rt “depth” “//gph3-server/Render/Maya/38_HG_Sodbrennen_2013/images”;

removeRenderLayerAdjustmentAndUnlock defaultResolution.width; catch(setAttr defaultResolution.width 1050);
removeRenderLayerAdjustmentAndUnlock defaultResolution.height; catch(setAttr defaultResolution.height 576);

global int $g_mrBatchRenderCmdOption_NumThreadAutoOn = true; global int $g_mrBatchRenderCmdOption_NumThreadAuto = true;
global int $g_mrBatchRenderCmdOption_MemLimitAutoOn = true; global int $g_mrBatchRenderCmdOption_MemLimitAuto = true;
global int $g_mrBatchRenderCmdOption_VerbosityOn = true; global int $g_mrBatchRenderCmdOption_Verbosity = 5;
$rl=“Cut1”;

setMayaSoftwareLayers($rl, $rp); miCreateMentalJobs(); setImageSizePercent($resize); mayaBatchRenderProcedure(0, “”, “”, “mentalRay”, $opt);

}

//
// Main part
//

string $sceneName = “//gph3-server/Render/Maya/38_HG_Sodbrennen_2013/scenes/S02_HD.mb”;

string $checkScene = file -q -sn;
if ($checkScene=="") {
error (“Cannot load scene. Please check the scene name.\n”);
} else if (catch(renderIt($sceneName))) {
error (“Render failed.\n”);
} else {
print (“Render completed.\n”);
}

// Ending Mel program

3: INFO: Executing script: C:\Users\gph-render\AppData\Local\Temp\tmp6782.tmp
3: INFO: Waiting for script to finish
3: INFO: Deadline is ignoring error: “mel: Warning: file: C:/Users/gph-render/AppData/Local/Temp/tmp6782.tmp line 13: The flag “-renderType” is obsolete and has been replaced by the “-fileRule” flag. Please use the new flag.” because plugin setting Strict Error Checking is enabled and this error is not usually fatal.
3: STDOUT: mel: Warning: file: C:/Users/gph-render/AppData/Local/Temp/tmp6782.tmp line 13: The flag “-renderType” is obsolete and has been replaced by the “-fileRule” flag. Please use the new flag.
3: INFO: Deadline is ignoring error: “Warning: file: C:/Users/gph-render/AppData/Local/Temp/tmp6782.tmp line 13: The flag “-renderType” is obsolete and has been replaced by the “-fileRule” flag. Please use the new flag.” because plugin setting Strict Error Checking is enabled and this error is not usually fatal.
3: STDOUT: Warning: file: C:/Users/gph-render/AppData/Local/Temp/tmp6782.tmp line 13: The flag “-renderType” is obsolete and has been replaced by the “-fileRule” flag. Please use the new flag.
3: WARNING: Monitored managed process MayaBatch is no longer running

=======================================================
Error Type

RenderPluginException

=======================================================
Error Stack Trace

bei Deadline.Plugins.Plugin.RenderTask(String taskId, Int32 startFrame, Int32 endFrame)
bei Deadline.Slaves.SlaveRenderThread.RenderCurrentTask(TaskLogWriter tlw)

Looks like maya is just crashing, but it’s not giving any helpful information explaining why.

Can you resubmit the job, but this time turn off the “use MayaBatch” option in the submitter? This will make Deadline perform a command line render with Maya, which might result in a better error message. Assuming you still get errors, please post one and we’ll have a look.

Thanks!

  • Ryan