PDA

View Full Version : Anyone know what this error message means?


bmonk
2007-07-17, 01:42 PM
I get this error message when attempting to recover a drawing. Does anyone know what it means, and does anyone know what I can do to fix it, to get my drawing back.
rkmcswain
2007-07-17, 05:17 PM
It means you are probably out of luck.

Maybe not however...
See this page for some suggestions, including two offers to examine your DWG file.
http://rkmcswain.blogspot.com/2005/10/corrupt-drawings.html
Arben.Allaraj
2007-07-18, 08:36 AM
I get this error message when attempting to recover a drawing. Does anyone know what it means, and does anyone know what I can do to fix it, to get my drawing back.

Try to convert the last saving *.bak file in DWG.
bmonk
2007-07-18, 08:13 PM
Try to convert the last saving *.bak file in DWG.

I did that and got the same result.
bmonk
2007-07-19, 02:01 PM
I have conceded defeat. I cant seem to find anything on this error other than what R.K. linked, and after reading that, I think I'll just throw it in the "must be a glitch in the Matrix" pile and move on.

Thanks for the tips and links.
Ed Jobe
2007-07-19, 02:22 PM
That's coming from a dll I don't recognize. Where did you get the app stored on your U: drive? Check with them on the error.
cadtag
2007-07-19, 03:06 PM
... Where did you get the app stored on your U: drive? .

It's not his U: Drive, it's the U: drive mapped by the developer's who wrote and compiled the file that is crashing. the CPP extension is for C++, and there's a problem with the header file that was compiled into the DLL or executable file that's crashing. Something in the drawing is triggering a call that's supposed to be supplied from the .h file being referenced, and it's breaking there.

There may be something in the Windows EventViewer application logs that would help track down the breaking dll or exe, and from there you can decide whether or not to contact the developer of that software, whether it's Microsoft (Windows or dotNet), Autodesk, or some other 3rd party app on the machine.

It's probably a pretty unique situation, othewise it ought to have been caught during the application's debugging phase of development. but none of the developer's claim to be bug free, especially in odd situations.