Maya 2017 U3 batch render on render node fails

[Anonymous]

Hi,

just updated to Maya 2017 U3 and quite happy so far. But we have one big problem: We can not render on our render node anymore.

The following error message appears when we try to render via batch file:

Error: The transforms path found in the configuration file does not exist: C:/Users/Administrator/Documents/maya/2017/prefs/synColorConfig.xml
Error: The SynColor package is not installed: C:\ProgramData\Autodesk\Synergy\SynColor\2017
Warning: Parameter was not found: input_space
VP2 Warning : OpenGL is not supported when running Maya via a remote session, switch to DX11.
VP2 Warning : OpenGL is not supported when running Maya via a remote session, switch to DX11.
VP2 Warning : OpenGL is not supported when running Maya via a remote session, switch to DX11.
Initialized VP2.0 renderer {
  Version : 2016.3.71.11. Feature Level 5.
  Adapter : 
  Vendor ID: 0. Device ID : 
  Driver : .
  API : DirectX V.11. Using software WARP device due to failure to obtain a hardware device
  Max texture size : 16384 * 16384.
  Max tex coords : 32
  Shader versions supported (Vertex: 5, Geometry: 5, Pixel 5).
  Active stereo support available : 0
  GPU Memory Limit : 3991.66 MB.
  CPU Memory Limit: 23289.1 MB.
MultiDraw consolidation attempted to enable, but the graphics device does not support it.  MultiDraw will be disabled.
}
OpenCL evaluator is attempting to initialize OpenCL.
OpenCL evaluator failed to initialize clew.
pymel.core : INFO : Updating pymel with pre-loaded plugins: invertShape, mayaHIK, GamePipeline, curveWarp, CloudImportExport, tiffFloatReader, MASH, poseInterpolator, bifrostvisplugin, ATFPlugin, ikSpringSolver, ik2Bsolver, xgenToolkit, AbcExport, retargeterNodes, VectorRender, gameFbxExporter, renderSetup, OpenEXRLoader, lookdevKit, Unfold3D, Type, mayaCharacterization, fbxmaya
Warning: Parameter was not found: input_space
Warning: Parameter was not found: input_space
Warning: View transform name "sRGB gamma" is not defined in the transform collection. Using default value "sRGB gamma".
Error: Failed to apply color management settings on file open: View transform sRGB gamma is unknown..
Warning: Parameter was not found: input_space
Error: View transform sRGB gamma is unknown.
Stack trace:
  KERNELBASE.dll!RaiseException
  MSVCR110.dll!_CxxThrowException
  ExtensionLayer.dll!TcolorMgtFileRules::restoreDefaults
  Shared.dll!TcameraSetCmd::updateAttributeEditor
  Shared.dll!TcameraSetCmd::updateAttributeEditor
  CommandEngine.dll!TmetaCommandPtrArray::catenate
  CommandEngine.dll!TminMelArgList::nextDigit
  CommandEngine.dll!melScanDouble
  CommandEngine.dll!TminMelArgList::nextDigit
  CommandEngine.dll!TminMelArgList::nextDigit
  CommandEngine.dll!SophiaExecutable::evaluate
  CommandEngine.dll!TcommandEngine::sourceFile
  mayabatch.exe!TiteratorWrapperBidir<TscenePartitions::ConstIteratorDescriptor,TiteratorWrapper<TscenePartitions::ConstIteratorDescriptor> >::operator=
  ExtensionLayer.dll!Tapplication::start
  mayabatch.exe!TiteratorWrapperBidir<TscenePartitions::ConstIteratorDescriptor,TiteratorWrapper<TscenePartitions::ConstIteratorDescriptor> >::operator=
  kernel32.dll!BaseThreadInitThunk
  ntdll.dll!RtlUserThreadStart

Fatal Error. Attempting to save in C:/Users/ADMINI~1/AppData/Local/Temp/Administrator.20170325.1142.ma

The same scene and with the same software setup renders fine on our workstation.

License type is network license with one GUI license. 

Any hints?

Thanks in advanced,

Lars

[Stephen.Blair · Accepted solution]

Why is your synColorConfig.xml pointing to C:\ProgramData\Autodesk\Synergy\SynColor\2017 ?

rror: The transforms path found in the configuration file does not exist: C:/Users/Administrator/Documents/maya/2017/prefs/synColorConfig.xml
Error: The SynColor package is not installed: C:\ProgramData\Autodesk\Synergy\SynColor\2017

SynColor isn't in the the Synergy folder. In a default install, SynColor is in the Maya install folder (for example, C:/Program Files/Autodesk/Maya2017/synColor)

It looks the prefs on that machine were never set up, or they were set up incorrectly.

[Anonymous]

Hi Stephen,

just after writing the message I trashed the prefs and everything is fine.

Hm, the prefs were setup correctly and we had no problem with 2015 till 2016.5. 

So, for me the question is: Why did Maya 2017 screwed up the prefs?

Thanks for your immediately reply! Haven't used the forum for a while. Great support!

Nice day,

Lars