in this days we are trying dedaline, on one of our render nodes the logs show up this:



0: STDOUT: ==================================================

0: STDOUT: SOFTIMAGE® | XSI® Batch Version 6.0.2006.1218

0: STDOUT: Copyright© 1998-2006 Avid Technology, Inc. All rights reserved.

0: STDOUT: ==================================================

0: STDOUT:

0: STDOUT: License warning: feature [XSI Batch Win] not available

0: STDOUT: License information: using [XSI Batch All]

0: WARNING: Program “c:\softimage\xsi_6.0\application\bin\xsibatch.bat” did not close cleanly. It is being terminated forcefully.

Scheduler Thread - Render Thread 0 threw an error:

Scheduler Thread - Exception during render: ’ ERROR : 2315 - Potential plug-in conflict detected. This plug-in cannot be loaded until conflict is resolved:

Exception Details
RenderPluginException -- Exception during render: ' ERROR : 2315 - Potential plug-in conflict detected. This plug-in cannot be loaded until conflict is resolved:
RenderPluginException.Cause: JobError (2)
Exception.Data: ( )
Exception.TargetSite: Void RenderTasks(Int32, Int32)
Exception.Source: DeadlinePluginLoader
Exception.StackTrace:
at Deadline.Plugins.PluginLoader.RenderTasks(Int32 startTask, Int32 endTask)
at Deadline.Plugins.Plugin.RenderTask(Int32 startFrame, Int32 endFrame)
at Deadline.Slaves.SlaveRenderThread.RenderCurrentTask()

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

is due to xsi licensing or a client configuration problem with deadline?

thanks
Patryk

Patryk,



I am not an XSI specialist, but what Deadline client is doing is calling the external program (XSI Batch All in this case) and then reporting what XSI returned when crashing. Deadline usually does not crash itself, it just brings you the bad news ;o)



So in this case, the error message XSI reported to Deadline was



Scheduler Thread - Exception during render: ’ ERROR : 2315 - Potential plug-in conflict detected. This plug-in cannot be loaded until conflict is resolved:



which means (is far as I can read English ;o) that some plugin is misconfigured (possible attempting to load twice?) and XSI cannot run correctly until you fix this. So you should google this problem or use the XSI manuals or post to an XSI board for help to see how to resolve it as it is not a Deadline problem.



Hope this helps.



Borislav “Bobo” Petrov

Technical Director 3D VFX

Frantic Films Winnipeg

Hi - Ryan pointed me to this thread. I’m getting the exact same error. It only occurs on the system that I use as my main workstation - all other machines run Deadline with no problem.





I’ll try rendering just with XSIBatch to see what happens.

A quick test of XSIBatch shows that I can indeed render with XSIBatch, but Deadline will not work.



Patryk, are you running the “Viewport Controls” plug-in by Chinny? That seems to not be compatible with XSI 6.5, so I’m seeing errors related to it.

Uninstalling Viewport Controls does NOT fix the problem.



At this point Deadline is dead in the water on my main workstation.



Paul

Hi Paul,



When you render from the command line, do you still see that error

message? Could you post the stdout from the command line render test you

did? If that error message isn’t fatal to the renderer, we could

possibly tweak the xsi plugin to ignore those error messages (currently,

Deadline will just fail the job whenever “ERROR” is printed out by xsi).



Cheers,

• Ryan
  
  
  
  –
  
  Ryan Russell
  
  Frantic Films Software
  
  http://www.franticfilms.com/software/
  
  204-949-0070
  
  
  

Yes - same errors:



// VERBOSE : 5320 - The requested event has been installed with success: <SaveSc

eneOptions>

// VERBOSE : 5320 - The requested event has been installed with success: <SaveSc

eneOptionsAutoSave>

// WARNING : 3263 - The name of this plug-in is unknown:

// <path: C:\Softimage\XSI_6.5\Application\Plugins\alienbrain for XSI6.dll>

//

// VERBOSE : 5320 - The requested event has been installed with success: <Collad

aExportEvent>

// VERBOSE : 5320 - The requested event has been installed with success: <Collad

aImportEvent>

// VERBOSE : 5320 - The requested event has been installed with success: <RSMBSe

lectionEvent>

// VERBOSE : 5320 - The requested event has been installed with success: <Transf

ormUVs_sionkeydown__Event>

// ERROR : 2356 - This plug-in is not installed: Isolate

// ERROR : 2356 - This plug-in is not installed: QuickFlix

// ERROR : 2356 - This plug-in is not installed: ViewportOptions

// ERROR : 2356 - This plug-in is not installed: ViewSwitcher

To have Deadline not error out on those error messages, navigate to

//your/repository/plugins/XSI and open XSI.dlinit. Find the line that

starts with “OutputRule0=” (there may be a similar line with a semicolon

at the beginning, which you should ignore). At the end of this line, you

should see this:



FailRender( GetRegExMatch(0) );



Simply change it to:



LogInfo( GetRegExMatch(0) );





Now Deadline won’t fail on the job anymore on stdout lines with ERROR in

them.



Cheers,

• Ryan
  
  
  
  –
  
  Ryan Russell
  
  Frantic Films Software
  
  http://www.franticfilms.com/software/
  
  204-949-0070
  
  
  

Hi Ryan,



That still does not fix the issue. Can I give Frantic a call today to go over the issue? I’m in the middle of an HD render and I really need to add my workstation to the render pool at night.



Thanks



Paul

Hi Paul,



The next thing to try would be to remove all the stdout parsing from the

XSI plugin (temporarily) to see if that allows you to render on your

workstation. To do this, open the XSI.dlinit file again and in front of

every line that begins with OutputRegEx# or OutputRule0#, place a

semicolon (which turns the line into a comment which is ignored). Let us

know if that works.



Cheers,

• Ryan
  
  
  
  –
  
  Ryan Russell
  
  Frantic Films Software
  
  http://www.franticfilms.com/software/
  
  204-949-0070
  
  
  

That did the trick.



Thanks!