Did a quick dig here. The plugin-level debugging is enabled which makes it a lot harder to read the messages coming from Houdini. I’ve simplified and it looks like this:
0: STDOUT: Detected Houdini version: (19, 0, 531)
0: STDOUT: ['C:\\ProgramData\\Thinkbox\\Deadline10\\workers\\THANOS\\plugins\\6441d137dd0997665cfa3772\\hrender_dl.py', '-f', '102', '102', '1', '-o', '$HIP/render/$HIPNAME.$OS.$F4.exr', '-g', '-d', '/out/comp1', '-tempdir', 'C:\\ProgramData\\Thinkbox\\Deadline10\\workers\\THANOS\\jobsData\\6441d137dd0997665cfa3772\\0_tempprHN40', '-arnoldAbortOnLicenseFail', '1', 'C:/Users/stephen.scollay/Documents/LocalFiles/DeadlineCompositeTest.hip']
0: STDOUT: Start: 102
0: STDOUT: End: 102
0: STDOUT: Increment: 1
0: STDOUT: Ignore Inputs: True
0: STDOUT: Output: $HIP/render/$HIPNAME.$OS.$F4.exr
0: STDOUT: Driver: /out/comp1
0: STDOUT: Input File: C:/Users/stephen.scollay/Documents/LocalFiles/DeadlineCompositeTest.hip
and what we caught on:
Error: Caught exception: The attempted operation failed.
Here’s one of those other threads:
Can you run some of that advice? We have some new advice on how to isolate Houdini:
Can you dig into that KB article and report back here? Also feedback on the KB is welcome!