I just upgraded from vanilla autocad 2010 to 2013. I installed the Autocad Civil 3D 2013 Object Enabler (in order to work with subconsultant's Civil 3D files). Although it seems to be working I keep getting the following error messages when I open up any file that has/xref's Civil 3D objects:
"Unhandled Exception C0000005 (access violation writing 0x0000) at address DB5416B3h"
This message pops up twice.
I do see that when loading the drawing (if I scroll up in the command window) it has a line that reads "Unable to access shared pipe catalog folder. Please verify configuration. Run 'setNetworkCatalog' to reset." It says this twice. Perhaps this is the source of the unhandled exception error?
I have done the following:
1. set PROXYGRAPHICS to 1 (per a forum search). Still get the error message.
2. disabled digital signature icons (per autodesk). Still get the error message.
3. tried to run 'setnetworkcatalog'. It's an unknown command.
Although the object enabler does seem to be working (in the 1 day I've played with it), I'm worried that there will be issues down the road.
Anyone else have this issue? Or better yet, know how to solve it?
I hate error messages.
I have the same problem; I just installed Object Enabler for Civil in AutoCAD 2013, and I get four of these same "Exception in aecbase.dbx ARX Command" errors (or variations of them) when trying to open a site plan from Civil.
I've also noticed that some drawings will now no longer open in 2010, even though I have 2013 saving down to 2010. I get a Fatal Error when I try to open in 2010. It occurs on any drawing that has the Civil 3D info xref'd into it....but not all. Very hard to understand.
I've NEVER had problems upgrading before...and I started way back with Acad R14!!!
2013 is killing me!
i really need a solution to this problem all drawings with civil 3d data has this problem, the worst problem is i can't save some files.
aecbase.dbx fails to load
Just to report back...
The Unhandled Exception errors stopped when the civil 3D drawings I was working with were revised by the civil engineer (for unrelated reasons). Neither of us is sure what the problem was or why the errors stopped. Something on Civil 3D's end or some bad translation by the object enabler... a mystery.
I still have issues opening Acad 2013 drawings in 2010 even though they were saved down to 2010. I get random fatal errors in some drawings and have to recover them. My solution to this was to simply stop using 2010 completely, something I was loath to do considering the Unhandled Exception errors and all. So far 2013 has been behaving well enough.
Sybold, I was always able to open the drawings that had the Unhandled Exception errors. It wasn't a crash problem for me...
attached the errors
FATAL ERROR: Unhandled Access Violation Writing 0x0000 Exception at de7116b3h
it happends when opening a civil 3d 2010 dwg
even when the drawing is saved with the exporttoautocad command
I get this too, when opening a survey dwg with AEC objects in it. I get these similar errors
"Exception in aecbase.dbx ARX Command", "Exception in aeccvbase.dbx ARX Command", "Exeption in aecarchbase.dbx"
I saw some suggestions to use APPLOAD and load the aecbase.dbx and aeccvbase.dbx, etc files before opening the problem dwg, but I still get the errors when trying to open, save, use the -EXPORTTOAUTOCAD or AECTOAUTOCAD commands.
These error prompts occur in AutoCAD 2013 64bit SP1.1, and DWG TrueView 2013 64bit. (converting with TrueView was another suggestion I found)
The errors do not occur in AutoCAD 2012 64bit SP1. I use that as a workaround.
I had the same message sequence after upgrading to 2013 then removing C3D 2012 from my system (several weeks after the upgrade install). Ran the repair option from windows control panel (add/remove programs) and the problem resolved itself.
I am having the same issue. Does AutoDesk review and respond to these messages?
Something bad happens to most files I have received that are Civil 3D.