Launcher Thread - Launcher thread initializing...
Launcher Thread - Launcher thread listening on port 17080
Exception on Startup: An Unexpected Error Occurred:FranticX.Scripting.PythonNetException: ImportError : DLL load failed:
The specified procedure could not be found.
at FranticX.Scripting.PythonNetScriptEngine.a(Exception A_0)
at FranticX.Scripting.PythonNetScriptEngine.ExecuteFile(String scriptFile, String moduleName, Boolean optimizeCode)
at Deadline.Scripting.DeadlineScriptManager.CreateModuleFromFile(String scriptFilePath, String moduleName)
at a.a(String[] A_0)
Deadline Launcher will now exit.
Even reinstalling didn’t help. But if i uninstalled deadline7, and 8, then cleared all leftovers, then the programdata & users folders, then reinstalled, its good now. Not sure what might have caused it.
We do have a few machines like this, so if you have anything i could test, tell me!
Were those machines on an older beta version? At some point I re-jiggered where we kept our native Python modules that rely on Qt (on Windows), due to DLL-load issues. If you have this issue on other machines, you can try deleting ‘bin/Lib/site-packages/NativeThinkboxUI.pyd’ and ‘bin/Lib/site-packages/NodeView.pyd’. The *.pyd’s are now in the PyQt5 folder, where they can find/load the Qt DLLs properly.
Note that the NativeThinkboxUI.py and NodeView.py scripts should be left in site-packages, since they act as a thin loader for the ‘actual’ location of the libraries; this was so I didn’t have to change all the namespaces
Those can go, yeah. Short of explicitly loading the DLLs from a script, they shouldn’t be getting loaded to cause issues so it wouldn’t hurt to leave them there, but might as well keep it clean
Basically everything that’s in the PyQt5 folder on windows should no longer be in the root bin folder (this includes NativeThinkboxUIC++.dll, NodeViewC++.dll, and a couple of Qt dependencies)
OK, so I’m having the same issue on several render machines. None of them had the beta installed. I submitted a support email about it yesterday. But I saw this thread so I thought I’d give it a try. Unfortunately I don’t have those files in that location. Are there any other reasons for not being able to launch anything?
Yep, I scrubbed them clean. It’s weird because the machines it doesn’t work on are random. I can’t find any pattern that would point to why it works for one machine and not the other.