Hi, Im running Deadline 8, trying to use the Job Submitter to render Redshift with Deadline.
This is the error that pops up when I try to use it, If I engage the job directly from Monitor, it works, and the PC renders just fine.
Any ideas?
Thanks
Error
Error: GetConfigEntry: Attempted to access non-existent config key RenderExecutable2018_0 (Deadline.Plugins.RenderPluginException)
en Deadline.Plugins.DeadlinePlugin.GetConfigEntry(String key)
en Python.Runtime.Dispatcher.TrueDispatch(ArrayList args)
en Python.Runtime.Dispatcher.Dispatch(ArrayList args)
en FranticX.Processes.ManagedProcess.PreRenderTasks()
en FranticX.Processes.ManagedProcess.Execute(Boolean waitForExit)
en Deadline.Plugins.PluginWrapper.RenderTasks(String taskId, Int32 startFrame, Int32 endFrame, String& outMessage, AbortLevel& abortLevel)
This is an age-old Deadline problem where we do not support the version you’re trying to use. The fix is to upgrade to a newer version. Supported software versions for each version of Deadline are listed in ‘Supported Software’ in the docs. Maya in Deadline 8 only went to 2017.
In detail, we store the values to the various render executable paths in the “Configure Plugins” section of the Monitor and Database. When we don’t have a key there yet, we pull the default from “[repo]/plugins/[plugin name]/[plugin name].param” and if it’s not there either, you get the error you saw.
So, now the next question is where is that key built and why did it make it to the plugin? Well, the key is built dynamically inside the integrated submitters. We usually do this by grabbing the major version of the application and throwing that in as they key, so in this case we took “RenderExecutable” and tacked in “2018_0” to the end of it. If you were on 2018.5 it would have been “RenderExectuable2018_5”.
Sitting down and thinking about this, we have ~90 plugins that could really be throwing a better error on this one. At that scale, it’s going to be a bit of a pain to deal with, so I’m hoping this forum thread can act as a workaround until we solve it, but if you’ve had this problem please heart or reply on this thread so I can gauge impact.
@masdim This error you are getting on your render node is mostly because you are trying to render on the DCC version which is not supported on the version of Deadline you are running on the Farm.
