Error in bm->OpenOutput()

im_thatoneguy · October 1, 2013, 9:13pm

[code]

Error

Error in RenderTasks: RenderTask: Unexpected exception (Error in bm->OpenOutput(): error code 1
2013/10/01 12:24:50 DBG: [03460] [00720] Interface8::LoadFromFile(C:/Users/renderadmin.SFS/AppData/Local/Thinkbox/Deadline6/slave/RENDER-I7-10/jobsData/524b1ef9b5b7e14848bee893/GLG_Note3-Black_0010_A01.04.max)
2013/10/01 12:24:50 INF: [03460] [00720] Starting to load file: C:/Users/renderadmin.SFS/AppData/Local/Thinkbox/Deadline6/slave/RENDER-I7-10/jobsData/524b1ef9b5b7e14848bee893/GLG_Note3-Black_0010_A01.04.max
2013/10/01 12:24:50 WRN: [03460] [00720] Missing dll: Built-in - AnchorHelperObject
2013/10/01 12:24:51 INF: [03460] [00720] Done loading file: C:/Users/renderadmin.SFS/AppData/Local/Thinkbox/Deadline6/slave/RENDER-I7-10/jobsData/524b1ef9b5b7e14848bee893/GLG_Note3-Black_0010_A01.04.max
2013/10/01 12:24:51 INF: [03460] [00720] SYSTEM: Production renderer is changed to V-Ray Adv 2.45.01. Previous messages are cleared.
2013/10/01 12:27:20 ERR: [03460] [00720] Could not read/write file type: C:\Users\renderadmin.SFS\AppData\Local\Temp\GLG_Note3_0010_Beauty-Black_A01.030007._MultiMatteElement
)
at Deadline.Plugins.ScriptPlugin.RenderTasks(String taskId, Int32 startFrame, Int32 endFrame, String& outMessage, AbortLevel& abortLevel)

Type

RenderPluginException

=======================================================
Stack Trace

at Deadline.Plugins.Plugin.RenderTask(String taskId, Int32 startFrame, Int32 endFrame)
at Deadline.Slaves.SlaveRenderThread.a(TaskLogWriter A_0)

=======================================================
Full Log

…

0: INFO: Lightning: CallCurRendererRenderFrame returned code 1
0: INFO: Lightning: Render done
0: INFO: Lightning: Saved image to W:\13035 GLG Note3 Model and 360\Shots\GLG\Renders\AOV\Black_Beauty\A01.03\GLG_Note3_0010_Beauty-Black_A01.03.0000.exr
0: INFO: Lightning: Checking render elements[/code]

MikeOwen · October 2, 2013, 9:43am

Possible reasons for the error:

StateSets is screwed again for your file:

Missing dll:  Built-in  - AnchorHelperObject

Try doing the reset method that previously helped you or this particular Slave is not running the same version of software as your other machines? incl. SP’s/PU’s/extensions?

1 or more Render Element’s have no image file extension defined in the RE’s or maybe these RE’s are defined in the StateSet UI?:

Could not read/write file type: C:\Users\renderadmin.SFS\AppData\Local\Temp\GLG_Note3_0010_Beauty-Black_A01.030007._MultiMatteElement

Have you created any RE’s, saving to a particular image file format and then saved the Max file a few times and then changed the file extension to a different image file format and then submitted the job to Deadline? If so, it’s a known Max bug. Delete all your RE’s, save the MAx file. Merge into a fresh scene, re-create the RE’s. Done.
Local Slave HD is full? - check: C:\Users\renderadmin.SFS\AppData\Local\Temp
Is your studio using Ephere’s Zookeeper at all?

im_thatoneguy · October 2, 2013, 5:48pm

I’ve discovered that the AnchorHelper warning is on every job. So I’m just going to ignore it. Nothing seems to get rid of it.

I’m not actually writing out render elements I’m just embedding them into the EXR as AOVs. So there is no file to read/write.
Sounds like it could be contributing to the problem.

The solution I found was to check “Do Not Save Render Elements” in the SMTD “render” tab.

I think this is a deadline bug though. It’s only failing when it attempts to check the output using OpenOutput() which I think is a lightning function isn’t it? I think it’s deadline checking the render. But since I’m not actually rendering files it’s crashing. The files are rendered fine. If I mark the tasks “completed” then it’ll error out on the next set and finish those successfully too. It’s just Deadline thinking it failed when the render actually succeeded.

MikeOwen · October 2, 2013, 7:51pm

Are you running your Deadline slaves in NT service mode? I think SS isn’t currently supported and hence the missing DLL.

im_thatoneguy · October 2, 2013, 7:58pm

Yes to service mode.

rrussell · October 2, 2013, 8:11pm

OpenOutput is a 3dsmax SDK function, but since you aren’t saving any files, Deadline probably shouldn’t be calling that.

Can you post a simple scene that reproduces this problem?

Thanks!

Ryan

im_thatoneguy · October 2, 2013, 11:23pm

Here is the job. Please delete when downloaded.

MikeOwen · October 3, 2013, 10:42am

Missing dll:  Built-in  - AnchorHelperObject

ADSK Defect BUG now logged as DEFECT-0287

unable to resolve various .NET asemblies in the Backburner STDout such as:

2013-10-02 18:07:17:  0: STDOUT: - 18:07:16.156 INFO: Begin resolve assembly 'Autodesk.Max.StateSets.XmlSerializers- 18:07:16.156 INFO: Cannot resolve assembly

ADSK Defect BUG now logged as DEFECT-0288

rrussell · October 3, 2013, 3:56pm

Thanks! I was able to reproduce the error in Deadline. However, if I open the same scene in Max and just press Render, I get the error “Error Creating Output File”, which is basically what that Error in bm->OpenOutput() means. So this looks like a more general max issue.

Note that I did change the main output path and RE output paths to valid paths before submitting.

Cheers,

Ryan

im_thatoneguy · October 3, 2013, 4:31pm

Weird. Ok. Well it’s strange though that it finishes rendering. Writes the output and then errors out after the fact. I’ll post a Max bug report.

MikeOwen · October 3, 2013, 4:44pm

Gavin - I’ve seen this issue a few times before and I’m pretty sure it’s related to my original reasons I gave in my first response to this thread.

More than likely, it’s one of the RE’s file extension or bitmap plugin it is using having gone funny on you in this scene file. If you like, I can narrow it down for you, if you want to send me the Max file. I don’t need any geo in the scene, just the scene file with its render settings intact. If you stick in a teapot in the now empty scene and it still pop’s up this error message when you render it locally as Ryan said; send it over and I’ll try and narrow it down for you. - At least then, you will have a nice error reproducible Max file to send to ADSK

(If you do, can you tell me what version of Max/VRay it is using?)

MikeOwen · October 9, 2013, 9:15am

FYI. Latest news from ADSK on the “Missing dll: Built-in - AnchorHelperObject” issue:

2012 PU10 - Success
2013 PU6 - ERROR: 3dsmax adapter error : Autodesk 3dsMax 15.6 reported error: Missing dll: Built-in - AnchorHelperObject
2014 SP3 - Success

So, the issue can currently be fixed with the latest PU/SP, unless you are running Max2013. I have asked ADSK if they can release a retro PU7 to Max2013 to resolve this issue. Awaiting feedback.