Maya Error Messages And Meanings

1 Maya Error Messages And Meanings

This is a collection of known Maya error messages and their meanings, as well as possible solutions. We want to keep this list as up to date as possible, so if you run into an error message that isn't listed here, please email Deadline Support and let us know.

Exception during render: Error: (Mayatomr) : could not get a license

Mental Ray is reporting that it can't find a license. Mental Ray requires an additional license for network rendering, whereas renders such as mayaSoftware and mayaHardware simply uses your Maya license.

Certain versions of Maya come with satellite licenses for Mental Ray, but this requires some additional setting up to enable network rendering. It's probably best to contact the Maya support team about this.

Exception during render: Renderer returned non-zero error code, 211

When Maya prints this error message it usually means that Maya can't access a particular path because it either doesn't exist or it doesn't have the necessary read/write permissions to access it. This error tends to occur when Maya is either loading the scene or other referenced data or when saving the final output images.

When you get this error, you should check the slave log that is included with the error report. Often, Maya shows which path it wasn't able to access. Check to make sure that the slave machine rendering the job can see the path, and that it has the necessary permissions to read/write to it.

Exception during render: Error: Cannot find procedure "getStrokeUVFromPoly"

This error can occur when rendering with paint effects. When you write prerender/postrender scripts be sure to use maya commands and not function wrappers that the gui posts since a huge number of functions don't get loaded when rendering in batch mode.

For a quick fix, add the following before the call to the prerenderscripts main functions:

source "getStrokes";

Turtle: The system cannot find the path specified.

When Turtle is installed, it sets some environment variables. However, Deadline will not recognize these variables until the Deadline Launcher (the application in the Windows tray) is restarted. Restarting the Deadline Launcher will fix this problem.

Exception during render: Renderer returned non-zero error code, -1073741819

The error code -1073741819 is equivalent to 0xC0000005, which represents a Memory Access Violation error. So Maya is either running out of memory, or is touching memory that it shoudn't. If you find that your frames are still being rendered, you can modify the Maya plugin in Deadline to ignore this error.

Just add the following line of code to the Maya.dlinit file in //your/repository/plugins/maya. Note that the code below must be all on one line, and can be added after the "RenderStartupDir=..." line.

CheckReturnCode=if( ReturnCode() != 0 ) { if( ReturnCode() != -1073741819 ) { FailRender( "Renderer returned non-zero error code, " ..ReturnCode() ); } }

mental ray: out of memory

Try tweaking your Memory and Performance settings in the mental ray tab in the Maya Render Settings window. Try increasing the Physical memory setting (if you have the extra RAM). A common suggestion is to set it to 80% of your available RAM. You could also try tweaking the Acceleration method settings.

Another thing you can try is trimming down your scene so that is uses less memory.