AutoCAD 2010/2011/2012 DWG Format
Re: Error Autocad 2011:Adui1
Indeed, this error is a sign of a bad installation, as there are simply some needed files which are missing. If you were to copy the adui18res.dll into its correct location, you'd then go down a path of other files which cannot be found. Replacing them file-by-file would eventually lead to a situation where you'd just get an impassible error. The only solution I have found is to go through the complete and thorough removal, using the following link:
http://usa.autodesk.com/getdoc/id=TS45252
The above comments about verifying the .NET Framework installation are quite valid, and it's certainly a good thing to check before proceeding with any problematic AutoCAD installation.
When I ran into this problem on my own system, the key seemed to be removing the Autodesk Shared folder from C:\Program Files\Common Files. As there are some DLL files in use there, it can be difficult to remove. Start by setting Windows to show all file extensions. Next, rename the DLL extensions for all DLL files to some other extension (like OLD, for example). You'll need to do this for all DLL files in the root of the Autodesk Shared folder, plus any subfolders. A simple batch file can accomplish this. The syntax consists of one line, which is REN *.DLL *.OLD. I've attached such a batch file to this post. Please use it with caution and only within the confines of getting rid of the Autodesk Shared folder.
NOTE: I had to give the file a .LOG file extension so that I could attach it here. Remove the .LOG file extension so that it is a batch file, once you've saved it to your system.
Once the DLL files have all be renamed to *.OLD, reboot the system and you should be able to delete the Autodesk Shared folder (if not, try booting into Safe Mode to delete it). Then, run the installation for the AutoCAD product in question again and it should copy all of the installation content successfully.
Zac Travis
GCSO - Frontline Technical Support
Indeed, the software should install seamlessly, and in most cases it does. However, since you mentioned Group Policies, there are several technical support cases we have where the outlined process was not followed for Group Policies, and the result was the missing DLL messages upon running the program. There is a section of the documentation (included with the software) that details considerations and processes when Group Policies are in use.
Another thing which has been shown to result in the missing DLL errors is the usage of hard drive encryption software, as well as software which redirects user-specific folders. As there are many and varied softwares which perform those tasks, we do not test against such configurations. For the most part, our software installation testing is done within the confines of the most common (standalone and network) Windows scenarios. Since there are almost limitless amounts of combinations of Windows installation options and the various user/file/folder rights/permissions, it's not feasible to test within every conceivable scenario.
When 3rd party security softwares and other factors are included, there is another complete subset of potential real-world scenarios against which Autodesk software installations were never tested prior to their release.
To summarize, it's very rare that we find problems with installations of Autodesk software on machines which just have Windows (and MS Office) installed directly from disc and no other software loaded. I realize that it's uncommon to find such a system in the real world, but past that the sky is the limit for possible configurations. No software within any industry would ever get released to market if it were required that every possible combination of factors be tested against.
Zac Travis
GCSO - Frontline Technical Support
