Hello,
We have an issue when submitting vrscene to deadline through the Vray submitter in the monitor:
the following error is poping at each task
FailRenderException : [2023/Feb/7|17:59:55] [1096 MB] error: [] -1: Error parsing JSON data: (Invalid escape character in string.) at (409)
at Deadline.Plugins.DeadlinePlugin.FailRender(String message) (Python.Runtime.PythonException)
File "C:\ProgramData\Thinkbox\Deadline10\workers\mh13-2021-096\plugins\63e24aa4593ab720b0f7e16e\Vray.py", line 310, in handleStdoutError
self.FailRender( self.GetRegexMatch( 0 ) )
at Python.Runtime.Dispatcher.Dispatch(ArrayList args)
at __FranticX_Processes_ManagedProcess_StdoutHandlerDelegateDispatcher.Invoke()
at FranticX.Processes.ManagedProcess.RegexHandlerCallback.CallFunction()
at FranticX.Processes.ManagedProcess.e(String di, Boolean dj)
at FranticX.Processes.ManagedProcess.Execute(Boolean waitForExit)
at Deadline.Plugins.DeadlinePlugin.DoRenderTasks()
at Deadline.Plugins.PluginWrapper.RenderTasks(Task task, String& outMessage, AbortLevel& abortLevel)
at Deadline.Plugins.PluginWrapper.RenderTasks(Task task, String& outMessage, AbortLevel& abortLevel)
It seems to be a invalid character in a string, however, we checked our scenes and they are fine, we are able to render from command line directly from vray standalone.
we do not have any exotic character, nor spaces in our paths, and all the slashes are this one >> /
So i wonder what can be the souce of the issue.
we are using vraystd_adv_60020_x64_vc14 & deadline 10.1.23.6 Release (773a6289d)
the vray scene is genrated with houdini 19.5.403
The OS is win 10.
Every hint would be very appreciated.
Happy rendering to all.
Mathieu.
Looking at the Vray.py plugin file, it seems like plugin is failing the render as STDOUT handler calls the error handler if V-Ray returns any error in the logs. You can check the /[repo]/plugins/Vray/Vray.py #65:
def initializeProcess( self ):
self.StdoutHandling = True
self.AddStdoutHandlerCallback( ".*error: Error loading plugin library.*vray_BRDFSimbiont.dll.*LoadLibrary failed.*" ).HandleCallback += self.handleStdoutFailedLoadingDLL
self.AddStdoutHandlerCallback( r".*error: Cannot create output image file \"[^\"]*<[^\<]*>[^\"]*\": Invalid argument \(22\).*" ).HandleCallback += self.handleVRayArgumentError
self.AddStdoutHandlerCallback( ".*error:.*" ).HandleCallback += self.handleStdoutError
How did you isolate the submission from Deadline? I would expect V-Ray to return the same behavior outside Deadline, if you have run the commandline render on the same machine which failed the render. You can get the Full Command from the render log and run it on the command prompt of the render node. Here is a troubleshooting documentation: Troubleshooting — Deadline 10.2.0.10 documentation
Feel free to share the render log and command line logs from the test here to investigate or you can open a Support ticket with Thinkbox Team.
It seems that the issue is coming fom a path mapping rule,
we convert a netwok drive to an UNC path T:\ to \server\project
the issue does not occur when we render in a deadline region where we do not path map.
However we did not manage yet to find what cause trouble in our path map rule.
the path map is applied and the files are found by deadline & Vray and we still get the error
Are we missing a slash in front of the Server UNC path? The UNC path should be referred in '\\server\project' format.
Also can you check if you have recursive path mapping option enabled under Monitor > Tools Configure Repository Options > Mapped Paths > Recursively Apply Path Mapping Rules.
We figure out the issue.
In a vrScene, a block of the code describe the options of the vray frame buffer.
This block use JSON, and in our setup the VFB has an OCIO config pointing to network Drive Z:/config.ocio .
This one was path mapped too, and become \\server\folder, and this \ is an escape character in JSON causing the error.
We have change the path to //server/folder/config.ocio and it runs smoothly.
it was not the easiest issue to resolve 
3 Likes
Thanks @Mathieu_Arce for an update, I am glad you fixed the issue. I will create an internal runbook on your finding and would help us handling this issue in future.