FATAL ERROR: Unhandled Access Violation Reading 0x0090 Exception at .....

[JustinGG5N9H]

Hey Everyone,

A few drafters in our office have been running into a fatal error when importing Sheet Layouts from a Master Template file we have set up for our construction drawing sheets. The error reads "FATAL ERROR: Unhandled Access Violation Reading 0x0090 Exception at A2DFEA6h". We reran the process after running cleanup on the drawing (Audit, Recover, Purge, -Purge), with the same result. Only difference between the two is the last Alphanumeric number changed to 539AFEA6h. We have run cleanup procedures on both the Template and the subject drawing, and the template works fine for others in the office. Dose anyone know a solution to prevent this from happening to other in the office. So far, between the two drafters that have had this issue, I see no common pattern other then importing the layout.

Thank you for your help, and have a great day.

[spear_kevin_pe]

hi... can you post some details? what version of cad/c3d made the template? what version are designers running? Is it possible to post the template? I know that's a tough ask....

[JustinGG5N9H]

Removed in favor of a Direct replay to Kevin.Spear.

[JustinGG5N9H]

Well hello again Kevin. Yes, the version that created the template is Civil 3D 2018. The drafters are using 2023 currently. And unfortunately no, proprietary info and all that. It should also be noted that the template I speak of is not our DWT. It is only the master source for our typical paper space layouts.

[spear_kevin_pe]

For giggles, can staff import from the OOTB files that have layouts and get the same error? If so, then its something in the program. If not, then its something in your sheet templates. The OOTB location would be:

C:\Users\<username>\AppData\Local\Autodesk\C3D <version>\enu\Template\Plan Production

[JustinGG5N9H]

Yes, the drafter currently having the issue was able to pull from the OOTB. We have opened up the subject drawing onto 3 other machines to see if the issue persisted, but it is Isolated to the one drafter at the moment. I am going to try to updated the Template to the current version to see if that works.

[JustinGG5N9H · Accepted solution]

Through additional trouble shooting, we discovered that an architectural block from a Revit file conversion was causing the error. The Drafter had brought it into his drawing and exploded it to convert the styles to match our standards for the concept. Something about the block caused the issue. Upon deleting all occurrences of that block and its components, the issue was resolved.