We have noticed since updating to Deadline 6.1 that we are getting a DLL error for AnchorHelperObject with every job we submit. State Sets was not used on any of these jobs and even if we set Deadline to ignore missing DLL Errors. Our workaround has been to modify the job properties to turn of the DLL errors and restart the job. After that, all is well. Has anybody else experienced this? We are running 3ds Max Design 2014 SP3.
Hi,
Are you running Deadline as an NT service?
Mike
Yes we are.
This missing DLL only shows itself when Backburner or Deadline or indeed any render management software is running as a NT service. It is thought that the error is caused when 3dsMax is run without it’s GUI & in NT service mode and the new State Sets UI which is based on the QT UI framework, makes a request for some part of the State Set UI framework, hence the missing “AnchorHelperObject” error message. Autodesk are aware of the issue via their beta program and if you or any other 3dsMax user are seeing this issue, I would very much encourage you to report it to Autodesk either directly (do you have access to the Autodesk beta site?) or via your Autodesk reseller, as we are all stuck waiting for Autodesk to hopefully get to the bottom of this issue and resolve it for all users. A defect report was submitted some time ago to the Autodesk beta site, highlighting this issue. Other beta users have also reported this issue is still outstanding in Max2014. (I should add that this issue is present even if you don’t use State Sets or you think you have reset State Sets…it’s the Autodesk gift that just keeps on giving…) 
Oh and running in normal, non-NT service mode and everything is just fine. So, you could test this out if you want to resolve the issue immediately.
Thanks, Mike. Running without a service is not an option for us. Besides, running as a service provides much more RAM and system resources to the slaves than we see if running logged in (somewhere in the 512MB to 1GB range in RAM and about 5 to 10 percent system resources).
We got the same Problems here, and using max 2014 Sp4 brings us no solution. In these times we are forced to submit all our Jobs always checked with the “Ignore DLL Errors” Flag.
I had spend lots of hours to find the Problem, and where we used this mysterious AnchorObject. My findings are consistent with those of MikeOwen.
It´s a Bug from AutoDesk in Max2014 an they can´t solve it in the fourth ServicePack. Realy sad.
So i try to submit our Reports in the beta program and hope to get an answer from this big inaccessible company.
Does anyone a way in RPManager to load DeadlineSumbitPreset? So i would be able to distribute a Preset to all our artists with the checked “Ignore DLL errors”-Flag and some other mostly used Settings and load them in RPManager automatically for every new Pass?
Greetings
Dominik
IIRC, RPM loads in the entire SMTD functions/UI into it’s interface, so therefore our “defaults” & “sticky” INI file system should be working and applying whatever sticky/default settings have been applied in the 2 x INI files which reside in the Deadline repository:
/[deadline_repo_path]/submission/3dsmax/main/
“SubmitMaxToDeadline_Defaults.ini” & “SubmitMaxToDeadline_StickySettings.ini”
Before touching these files, I would highly recommend this tutorial which fully explains how the system works:
wow! thank you for that fast answer! i will try to implement your suggestion!
will these two files be copied/loaded every time when some artist use “Deadline”, or will they be loaded once only?
These 2 INI files are cached locally the first time the user opens the SMTD or RPM (with Deadline) in an instance of 3dsMax. So if you make a change on the global, server side files, you will need to re-open the SMTD/RPM to see the change.