Hi Guys!
I have this error message, simply don’t understand… This is an addon called ViewportControl. What is the connection between an unloaded addon and the render task?? Under XSI 7.0 this addon works fine, somehow under XSI 7.01 not. We use the same workgroup 6.x and above.
Bestr regards,
Csaba Kanal
[b]Error Message
An error occurred in StartJob(): // ERROR : Invalid procedure call or argument: ‘Left’ - [line 1438 in e:\preferences\Softimage\XSI_7.0\Addons\ViewportControls\Application\Plugins\ViewportControlsAPI.vbs] (FranticX.Processes.ManagedProcessAbort)
Slave Log
requested event has been installed with success:
0: STDOUT: // VERBOSE : 5322 - This plug-in has been successfully loaded:
0: STDOUT: //
0: STDOUT: //
0: STDOUT: //
0: STDOUT: // VERBOSE : 5322 - This plug-in has been successfully loaded:
0: STDOUT: //
0: STDOUT: //
0: STDOUT: //
0: STDOUT: // VERBOSE : 5322 - This plug-in has been successfully loaded:
0: STDOUT: //
0: STDOUT: //
0: STDOUT: //
0: STDOUT: // VERBOSE : 5320 - The requested event has been installed with success:
0: INFO: Waiting for XSI: 40 seconds remaining
0: INFO: Received response: Ready
0: STDOUT: // ERROR : Invalid procedure call or argument: ‘Left’ - [line 1438 in e:\preferences\Softimage\XSI_7.0\Addons\ViewportControls\Application\Plugins\ViewportControlsAPI.vbs]
Exception Details
RenderPluginException – An error occurred in EndJob(): // ERROR : Invalid procedure call or argument: ‘Left’ - [line 1438 in e:\preferences\Softimage\XSI_7.0\Addons\ViewportControls\Application\Plugins\ViewportControlsAPI.vbs] (FranticX.Processes.ManagedProcessAbort)
RenderPluginException.Cause: JobError (2)
Exception.Data: ( )
Exception.TargetSite: Void EndJob()
Exception.Source: deadline
Exception.StackTrace:
at Deadline.Plugins.ScriptPlugin.EndJob()
at Deadline.Plugins.Plugin.Dispose()
Scheduler Thread - Render Thread 0 threw an error:
Scheduler Thread - An error occurred in StartJob(): // ERROR : Invalid procedure call or argument: ‘Left’ - [line 1438 in e:\preferences\Softimage\XSI_7.0\Addons\ViewportControls\Application\Plugins\ViewportControlsAPI.vbs] (FranticX.Processes.ManagedProcessAbort)
Error Type
RenderPluginException
Error Stack Trace
at Deadline.Plugins.ScriptPlugin.StartJob(Job job)
at Deadline.Plugins.Plugin.StartJob(Job job)
at Deadline.Slaves.SlaveRenderThread.RenderCurrentTask()[/b]
After googling the error message, it appears that this error shouldn’t be fatal, but Deadline is seeing the “ERROR” message being printed out by XSI and failing the job. In 3.1, we will be adding the option to turn off this error checking because we keep seeing more and more of these “ERROR” messages being caught by Deadline that aren’t really fatal. By turning off error checking, Deadline is leaving the error handling to XSI, in which case it should return a non-zero exit code to indicate that something has gone wrong.
In the meantime, you can modify the XSI/XSIBatch plugins to turn off error checking if you wish. Do do this, open \your\repository\plugins\XSI\XSI.py and \your\repository\plugins\XSIBatch\XSIBatch.py in a text editor. Find this line in each file:
self.AddStdoutHandler( ".*ERROR :.*", self.HandleStdoutError )
put a ‘#’ in front of it like this:
#self.AddStdoutHandler( ".*ERROR :.*", self.HandleStdoutError )
This will make Deadline ignore this line of code, and thus no longer fail on general ERROR messages.
Cheers,
Hi Ryan!
I see!
Another question: I am testing V-ray with XSI 7.01 When I want’s to render with Mental Ray Deadline gives me this error message:
[b]Error Message
An error occurred in StartJob(): ’ ERROR : 2356 - This plug-in is not installed: VRay Options (FranticX.Processes.ManagedProcessAbort)
Slave Log
Version 7.0.609.0 <batch mode>
0: STDOUT: Copyright© 1998-2007 Avid Technology, Inc. All rights reserved.
0: STDOUT: ==================================================
0: STDOUT:
0: STDOUT: MSG .0 debug: WIN_NT: checking OS version (WIN32_RAYLIB_OS)
0: STDOUT: MSG .0 debug: WIN_NT: confirmed running Windows NT 5.1
0: STDOUT: MSG .0 debug: WIN_NT: initialising Windows Sockets API
0: INFO: Waiting for XSI: 50 seconds remaining
0: STDOUT: License information: using [XSI Batch Win]
0: STDOUT: ’ INFO : ms_xsiMetaballs plugin has been loaded.
0: INFO: Waiting for XSI: 40 seconds remaining
0: INFO: Received response: Ready
0: STDOUT: COMMAND: -script “C:\Documents and Settings\All Users\Application Data\Frantic Films\Deadline\slave\plugins\XSIBatchStartup.vbs” -main RenderMain -args -commandFilename “C:\Documents and Settings\All Users\Application Data\Frantic Films\Deadline\slave\jobsData\command0” -ackFilename “C:\Documents and Settings\All Users\Application Data\Frantic Films\Deadline\slave\jobsData\ack0”
0: STDOUT: ’ INFO : Command Filename: C:\Documents and Settings\All Users\Application Data\Frantic Films\Deadline\slave\jobsData\command0
0: STDOUT: ’ INFO : Ack Filename: C:\Documents and Settings\All Users\Application Data\Frantic Films\Deadline\slave\jobsData\ack0
0: STDOUT: ’ INFO : Executing command: OpenScene(C:/Documents and Settings/All Users/Application Data/Frantic Films/Deadline/slave/jobsData/earring_03.scn)
0: STDOUT: >Loading: C:\Documents and Settings\All Users\Application Data\Frantic Films\Deadline\slave\jobsData\earring_03.scn…
0: STDOUT: ’ INFO : 4034 - Loaded scene was created with build number: 7.0.2008.1125 - compatibility version: 700
0: STDOUT: ’ ERROR : 2356 - This plug-in is not installed: VRay Options
Scheduler Thread - Render Thread 0 threw an error:
Scheduler Thread - An error occurred in StartJob(): ’ ERROR : 2356 - This plug-in is not installed: VRay Options (FranticX.Processes.ManagedProcessAbort)
Error Type
RenderPluginException
Error Stack Trace
at Deadline.Plugins.ScriptPlugin.StartJob(Job job)
at Deadline.Plugins.Plugin.StartJob(Job job)
at Deadline.Slaves.SlaveRenderThread.RenderCurrentTask()[/b]
I need this plugin and I am trying to avoid uninstall/reinstall it. Can you give me a quick solution? (This was the same problem Fryrender beta too… I gave up testing it)
Best regards,
Csaba
Did you apply the fix I had suggested for your other error on this thread? That should cover this new error message as well.