AWS Thinkbox Discussion Forums

Post Job script exception: Scope 'ScriptPluginScope0' DNE

Deadline 5.1 beta 3 ( 5.1.0.45496 )
Windows 7

We have a Post Job script that executes fine on our Render nodes, but on my machine I get

=======================================================
Error Message

Exception during render: An error occurred in RenderScript(): Scope ‘ScriptPluginScope0’ does not exist
Parameter name: scopeName
at Deadline.Plugins.ScriptPlugin.RenderScript(Job job, String scriptFilename, String& outMessage)

=======================================================
Slave Log

0: Loaded plugin: WtNuke
0: Task timeout is being ignored because this is a Post Job Script Task
0: Loaded job: AA_0001_comp_v044.001.nk (003_099_999_326057ae)
0: Plugin rendering frame(s): 99999
0: Executing Post Job Script: “\ISLAND\tools\deadline\postScripts\registerNkRenderDL.py”
0: INFO: Executing Script: \ISLAND\tools\deadline\postScripts\registerNkRenderDL.py
0: An exception occurred: Exception during render: An error occurred in RenderScript(): Scope ‘ScriptPluginScope0’ does not exist
Parameter name: scopeName
at Deadline.Plugins.ScriptPlugin.RenderScript(Job job, String scriptFilename, String& outMessage) (Deadline.Plugins.RenderPluginException)

=======================================================
Error Type

RenderPluginException

=======================================================
Error Stack Trace

at Deadline.Plugins.Plugin.RenderScript(Job job, String scriptFilename)
at Deadline.Slaves.SlaveRenderThread.RenderCurrentTask(TaskLogWriter tlw)

My machine has Visual Studio 2005/2008 installed and is definitely not as clean as our Render Nodes, but as far as I know was working fine with Deadline 4. If I get I chance, I’ll confirm that later today.

Thanks,
Paul

Hey Paul,

I think I found out why this occurs, and it’s definitely a bug. To confirm, is the only task that your workstation is processing a post job task? I think as long as the slave has processed at least one regular task, this error wouldn’t occur, which would explain why it works on your render nodes.

In any case, the source of this bug will be fixed in beta 4.

Cheers,

  • Ryan

Yes, I confirmed your theory.

I closed Slave and restarted it. If the first job it processes is a Post Job Task, the exception occurs.
If the Slave has processed a regular task first, all is well.

Glad you tracked that one down. That exception didn’t mean a whole lot to me!

-Paul

Privacy | Site terms | Cookie preferences