This issue has been driving us mad. This seems to be at the heart of the problem, our custom linetypes not being added to the database although we have them defined in the acad.lin that (findfile "acad.lin") points to.
Reading handle DEC4 object type AcDbLinetypeTableRecord Error 13 (eUnknownHandle) Object discarded Reading handle DEC8 object type AcDbLinetypeTableRecord Error 13 (eUnknownHandle) Object discarded Reading handle DECC object type AcDbLinetypeTableRecord Error 13 (eUnknownHandle) Object discarded Reading handle DECD object type AcDbLinetypeTableRecord Error 13 (eUnknownHandle) Object discarded Reading handle DED4 object type AcDbLinetypeTableRecord Error 13 (eUnknownHandle) Object discarded Reading handle DEDB object type AcDbLinetypeTableRecord Error 13 (eUnknownHandle) Object discarded Reading handle DEDC object type AcDbLinetypeTableRecord Error 13 (eUnknownHandle) Object discarded Reading handle DEDD object type AcDbLinetypeTableRecord Error 13 (eUnknownHandle) Object discarded Reading handle DEE3 object type AcDbLinetypeTableRecord Error 13 (eUnknownHandle) Object discarded Reading handle DEE4 object type AcDbLinetypeTableRecord Error 13 (eUnknownHandle) Object discarded Reading handle DEE8 object type AcDbLinetypeTableRecord Error 13 (eUnknownHandle) Object discarded Reading handle DEE9 object type AcDbLinetypeTableRecord Error 13 (eUnknownHandle) Object discarded Reading handle DEEA object type AcDbLinetypeTableRecord Error 13 (eUnknownHandle) Object discarded Reading handle DEEB object type AcDbLinetypeTableRecord Error 13 (eUnknownHandle) Object discarded Reading handle DF12 object type AcDbLinetypeTableRecord Error 13 (eUnknownHandle) Object discarded Reading handle DF13 object type AcDbLinetypeTableRecord Error 13 (eUnknownHandle) Object discarded Reading handle DF14 object type AcDbLinetypeTableRecord Error 13 (eUnknownHandle) Object discarded Reading handle DF15 object type AcDbLinetypeTableRecord Error 13 (eUnknownHandle) Object discarded Reading handle DF16 object type AcDbLinetypeTableRecord Error 13 (eUnknownHandle) Object discarded
Replacing linetype table record at index 15.
Replacing linetype table record at index 19.
Replacing linetype table record at index 23.
Replacing linetype table record at index 24.
Replacing linetype table record at index 31.
Replacing linetype table record at index 38.
Replacing linetype table record at index 39.
Replacing linetype table record at index 40.
Replacing linetype table record at index 46.
Replacing linetype table record at index 47.
Replacing linetype table record at index 51.
Replacing linetype table record at index 52.
Replacing linetype table record at index 53.
Replacing linetype table record at index 54.
Replacing linetype table record at index 56.
Replacing linetype table record at index 57.
Replacing linetype table record at index 58.
Replacing linetype table record at index 59.
Replacing linetype table record at index 60.
Salvaged database from drawing.
Is the recover messages, so....how can we fix this?
Thanks in advance for any insights..
Solved! Go to Solution.
Solved by nedwards9820. Go to Solution.
can you post a sample dwg with the lin files?
.lin file is an invalid extension to attach so I copied the text out and put it in a .txt file which I'm uploading now. It is the same that is in our acad.lin file that is pathed to
Thanks for that...
And some steps to repro?
In order to get the errors you may have to load the custom linetypes into the drawing via linetype, then move the drawing to another machine that does not have the linetypes loaded (a regular acad.lin file w/o custom linetypes) and have that machine open the dwg, set the current layer to one of inst-L2 through inst-L5 and draw a line, then delete the line.
Once that machine has deleted the line and saved the dwg, when opening on the original machine that has the linetypes loaded already, is usually when we were getting the errors.
I am not certain if this will reproduce without our linetype files, which I can provide you if another option that this forum' attachments is available (due to .shp and .shx not able to be attached, which is strange in of itself)
Thanks again for your time and your attentions, solving this issue or at least finding the cause in case it creeps up again for us would be very useful.
We have a similar problem with corrupted linetype references, and we would like to delete these linetype references, so is there a way to do this? In the DXF files we see long lists of corrupted linetypes, and these cause some drawngs to be so slow that they become unworkable.
The references we'd like to remove look like this in the DXF file:
AcDbDictionary
280
1
281
1
3
1000 SEAT L3$0$Nihhon Sekkei Archi Dwgs.dgn-StrokePattern-20
360
357
3
1000 SEAT L3$0$Nihhon Sekkei Archi Dwgs.dgn-StrokePattern-39477
360
358
3
1000 SEAT L3$0$Nihhon Sekkei Archi Dwgs.dgn-StrokePattern-39478
360
359
3
1000 SEAT L3$0$Nihhon Sekkei Archi Dwgs.dgn-StrokePattern-39479
360
35A
3
1000 SEAT L3$0$Nihhon Sekkei Archi Dwgs.dgn-StrokePattern-5625
360
35B
3
And suggestions?
-ne
Loading your lin file, it has corrupted line type definitions - do you see the same thing?
I believe this is more of a product issue rather than an API issue. Obviously, using the API you could remap the recovered linetypes back to the originals - but surely the solution here is to make sure that the linetype file exists on the new machine - doesn't etransmit help here? (sorry, I'm not a user of AutoCAD so I might be being dumb asking this :-))
Intreresting, the lin files come in without any messages for us, though surely that is the problem
Does the -purge command not help?
I replied direct from email with the drawing attached. I guess the text makes it to the forum but not the attachment. I'm attaching the drawing from the forum now.
thanks
For some reason I can't attach it as a .dwgso I've renamed the file with a .txt extension
-ne
thanks for sending the dwg file.
I loaded it into AutoCAD 2014 then examined the DWG structure using the MgdDbg app, and I failed to find anything wrong? Here's a sreen shot of the Mgddbg app examining the database, as you can see - it seems ok. I also tried a recover on the DWG file, it reports an issue with a dimstyle but that's it.
Thanks, I didn't know this was related to DGN - you probably have already seen this post, did it help? http://through-the-interface.typepad.com/through_the_interface/2013/07/minor-update-to-the-dgn-purge...
and this link mentioned at the end http://usa.autodesk.com/adsk/servlet/ps/dl/item?siteID=123112&id=22002791&linkID=9240618
Thanks -- i didn't know about the DGNPURGE command. I'm running AutoCAD14 and I didn't need the hotpatch.
DGNPURGE seems to work.
We still have a major problem with our drawings even after multiple DGNPURGE's. But if we select all the text in the drawing and just delete the lot, the problem (extreme slowness when drawing over an xref) is fixed. Brutal, but effective.
-ne