Installation & Licensing

[#1]

Using Windows 7 x64 and running AutoCAD 2010/2011, you will get the following error:

Unhandled Exception E0434F4D(e0434f4dh) at address 7c81EB33h

Please find the solution in the AutoCAD section:

http://forums.autodesk.com/t5/AutoCAD-2006/Exception-in-acmgd-dll-ARX-Command/td-p/1599600

Add "Read" and "Read and Execute" to the local group "Users" for the file:

"C:\Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG\machine.config"

[#2 · Accepted solution]

To clarify, I had to change the file inside the Framework64 directory, not the Framework directory.

Path:  

C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG\machine.config

[#3]

I'm getting the same error on a user's Windows 7 64-bit laptop.  Trying to get support is like having a root canal.  I've had a support case open (06536905) since June 10 & have heard absolutely nothing from Autodesk.  For the price you have to pay for this product, you'd think they'd have a support team.  I've even sent several emails to Product Support, begging for a reply to my case.  The only response I got was priceless: Autodesk has upgraded our CRM system to Salesforce.com. As part of this upgrade, all open and recent Service Requests have been migrated to the new system. To update your issue, log into your online Autodesk portal and select the appropriate Case. All emails to this address will not be read by Autodesk.

I had to uninstall AutoCAD LT 2012 from the user's laptop and reinstall AutoCAD LT 2008, because (for some strange reason), he needed to complete a drawing.  Now, I have to wait for him to free up his laptop for a couple hours so that I can try again.

WORST SUPPORT TEAM EVER.

[#4]

I also ran into this issue on a Windows 7 64-bit laptop.  The solution is relatively simple if you think about it. 

The original post was from back in 2008 and was referencing the .NET v2.0x folder.  With the 2012 version, it requires .NET 4.0.  So I went in and made the same permissions modification to the same files under the v4.0 folder instead. However, in my case, I was adding "domain users" permissions to the files.  Worked like a charm!

[#5]

In a recent case, we had to add Users and Everyone full control to this file:

C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config\machine.config

Everything worked as expected.  The target computer was running Windows 7 x64.

[#6]

The target computer in my case is running Windows 7 32-bit.

Should I change the permissions of this file then?

C:\Windows\Microsoft.NET\Framework\v4.0.30319\Config\machine.config

[#7]

Hi, I am experiencing the same problem on a 64bit Win7 systems as well.  Though its a simple fix, but does anyone know how to avoid this problem prior to the installation, because my users are setup as domain users and its becoming a pain upgrading 10 workstations and having to change the file permission on each workstation, its just an addiiotonal step that ends up time consuming.

Thanks.