I sincerely hope you're all having a good day. If you found this blog entry by a search for the error message above, your day might be on its way to improving...
We had a customer who was having terrible problems with his 2008 AutoCAD software, Civil 3D. He kept getting this fatal error:
FATAL ERROR: Unhandled e0434f4dh Exception at 7c812a5bh
When we talked to Autodesk, we found out that this error was caused by a Windows Update.
This being the case, I thought I ought to pass along the fix that worked for our client, in case anyone out there has had the same problem. If you're one of the 'little guys' working from home, and you don't have a place to go for help, problems like this one can really ruin your day.
Now, let me preface this with a warning: Use this fix at your own risk. If your company has an IT person, they would want you to get their help on this. If you are on Subscription with your AutoCAD software, you can log onto the Autodesk website and create your own Support Request.
Since this problem was caused by a Windows update, you can't fix it inside of AutoCAD. It has to be a Microsoft Windows fix. (You may be able to get help from them, I don't know.) The fix that I'm passing along is from Aaron Stebner's blog. He is currently a program manager on the XNA team at Microsoft and has been working there since 1999. He has his own caveat posted on the page, too, so please remember you are using this at your own risk.
With all that said, here are the steps you can try if you are running into this Fatal Error (at your own risk!)
This being the case, I thought I ought to pass along the fix that worked for our client, in case anyone out there has had the same problem. If you're one of the 'little guys' working from home, and you don't have a place to go for help, problems like this one can really ruin your day.
Now, let me preface this with a warning: Use this fix at your own risk. If your company has an IT person, they would want you to get their help on this. If you are on Subscription with your AutoCAD software, you can log onto the Autodesk website and create your own Support Request.
Since this problem was caused by a Windows update, you can't fix it inside of AutoCAD. It has to be a Microsoft Windows fix. (You may be able to get help from them, I don't know.) The fix that I'm passing along is from Aaron Stebner's blog. He is currently a program manager on the XNA team at Microsoft and has been working there since 1999. He has his own caveat posted on the page, too, so please remember you are using this at your own risk.
With all that said, here are the steps you can try if you are running into this Fatal Error (at your own risk!)
- Download and run the/any .NET cleanup utility (the one our client used is found at: http://blogs.msdn.com/astebner/archive/2006/05/30/611355.aspx )
- Reinstall .NET using the DOTNETFX.exe on the AutoCAD software installation CD/DVD (found in the \Support folder)
- Using Add/Remove programs, run a Repair on AutoCAD before opening it.
I hope that by passing along this information, I'll give someone a place to start.
.NET Framework problems can also cause other weird things to happen. Here is a list of things that might be symptoms of .NET Framework problems. If you've tried everything to fix these, running the .NET cleanup might help with the following problems:
- Some (but not all) variations of FATAL ERROR: Unhandled e0434f4dh Exception at 7c81eb33h/7c812A5bh
- “AutoCAD was not installed properly. Please reinstall immediately” or “The application has failed to start because its side by side configuration is incorrect…” errors on startup
- JIT (Just-in-Time) Debugger errors
- 1935/HRESULT 0x80070002 errors during AutoCAD install or deployment
- “NGEN failed to exit” errors during installation
- “Class Not Registered” errors
- Exception errors in acmgd.arx or acmgd.dll during startup
- “Cannot load assembly. Error details: System.Security.SecurityException” errors at the AutoCAD command line
- “Autodesk ACT libraries were not properly registered” starting 3DS Max or Viz
- Layer manager, tool palette, quick calculator, Style manager, Project navigator and ribbon (2009) issues. (These components depend heavily on .NET Framework)
- “Error 25015. Failed to install assembly…” during installation (primarily Inventor)
- Vault installation errors
I hope this might end at least one headache out there in cyberspace. I can't guarantee anything, but I'm hoping this will give you a place to start.
May your computers never crash, and all your upgrades function smoothly.
Posts
4 comments:
thanks so much! this seems to be the best thing i've found on the subject!
If I do the windows update though, will the problem come back?
Unfortunately, at this time there's no way to figure out which Windows update causes the problem, or if it will come back. I wish I had a better answer!
if the error is like this "FATAL ERROR: Unhandled e06d7363ebh Exception at 768e42ebh" will the update solve the problem?
this error appears when clicking on layer properties in Autocad 2009..
Fantastic, worked first time. You're a genius.
Post a Comment