Object(s) added to DB too late during save.

[AllenJessup]

I have a drawing containing a couple of Surfaces. I keep getting the "Warning: An error occurred during save. We recommend you run RECOVER on the drawing" error during a save. I wanted to copy paste to a new drawing to get rid of that. When I try to Select > All and the do a clipboard Copy. I get the following error.

Object(s) added to DB too late during save. Handles 12D2 to 12D2
12D2: type AeccDbRootSettingsNode, owner 7E (AeccDbTreeNode)

I've tried Audit and Recover. No errors detected. I've purged the drawing using DWG-PURGE, which will purge reggapps and DGN data. I Wblocked the drawing and inserted it into an new drawing from our template. I still get the error when trying to copy to the clipboard.

[AllenJessup]

---

@CADmgrMike wrote:

I've had this happen on a couple of drawings with no C3D content.

The interesting fix was to rotate the drawing view and then rotate back to World.

Drawing would then save without errors.

Don't ask me why. 🙂

---

That's wild. I'll try to remember that in case it happens again.

[Anonymous]

I've told to Autodesk support, sent them my file. They found that my problem was in label AECC_ALIGNMENT_INDEXED_PI_LABEL. When this label is exploded, this solves the problem.

[wes.sheffer · Accepted solution]

I just had this error for the first time today in C3D 2020.  It happened shortly after I mistakenly applied the DACH Extension update from the Autodesk Desktop App.  I was getting the "DGM-Beschriftung Wird new erstellt" error and the "Object(s) added to DB too late during save" error, and when I tried to save, I got "One or more objects in this drawing cannot be saved to the specified format.  The operation was not completed and no file was created."  Since I had made edits, and needed to do a save-as, I couldn't just dump the session to uninstall the DACH Extension.  I went through the following and finally cleared the DB-too-late and no-file-was-created errors:

(1) Purge, Audit, C3D style purge - try Saveas

(2) Delete unused Sites, Surfaces, Alignments, etc from Prospector, then repeat (1)

(3) Delete unused linework outside the area of interest, then repeat (1)

(4) -PU Regapps, Zero Length, Empty Text, etc, then repeat (1)

(5) Prospector was pointing to the wrong Data Shortcuts folder, so "Set Data Shortcuts Project Folder" and "Associate Project to Current Drawing."  -try Saveas

Success!!  It worked with two drawings back to back that were having the same issue (near duplicates of each other.)

I don't know if it was just (5) or a combination of items, but that's what worked for me.  I will say that they were not well-managed drawings and could have had any number of corrupted objects or broken C3D objects or references.

[lynn_zhang]

Hello @wes.sheffer 

Glad to hear you managed to fix the problem and thanks so much for sharing the solution!🙂

---

@wes.sheffer wrote:

I just had this error for the first time today in C3D 2020.  It happened shortly after I mistakenly applied the DACH Extension update from the Autodesk Desktop App.  I was getting the "DGM-Beschriftung Wird new erstellt" error and the "Object(s) added to DB too late during save" error, and when I tried to save, I got "One or more objects in this drawing cannot be saved to the specified format.  The operation was not completed and no file was created."  Since I had made edits, and needed to do a save-as, I couldn't just dump the session to uninstall the DACH Extension.  I went through the following and finally cleared the DB-too-late and no-file-was-created errors:

(1) Purge, Audit, C3D style purge - try Saveas

(2) Delete unused Sites, Surfaces, Alignments, etc from Prospector, then repeat (1)

(3) Delete unused linework outside the area of interest, then repeat (1)

(4) -PU Regapps, Zero Length, Empty Text, etc, then repeat (1)

(5) Prospector was pointing to the wrong Data Shortcuts folder, so "Set Data Shortcuts Project Folder" and "Associate Project to Current Drawing."  -try Saveas

Success!!  It worked with two drawings back to back that were having the same issue (near duplicates of each other.)

I don't know if it was just (5) or a combination of items, but that's what worked for me.  I will say that they were not well-managed drawings and could have had any number of corrupted objects or broken C3D objects or references.

---

[dsulz]

I know this is an older post but I will add my two cents about how we have been able to work around this annoying "added to DB too late during save." error.

The first way we have been able to get the error to clear is to use the ExporttoautoCAD command.  We save the export and don't close the original file but after the export just save the original file and the error for what ever reason magically goes away.

The 2nd work around, another magical solution, was I went in to paperspace and the scale was set to 1"=5'_xref so I set it to 1"=40', (i'm sure it could be any of the non-xref ones) did a save.  Like the first not sure why this cleared the error but it did.

We had tried the purge, purge C3D styles, audit, (ENTDEL(HANDENT “handle”)) which gives an error because the handle in the original error doesn't seem to really exist.  None of these did anything but for whatever reason the other workarounds I mentioned allowed us to save.  Hope this can help someone else. 

[darrell_kennedy]

That worked for me too Allen. Ha!

[mpryor433]

This may have worked for me. I say may have because it crashed when I was rotating the view, but I was able to save the next time I opened the drawing.

[mpryor433]

Update: In my case, running Audit makes the error happen again but rotating the view with the navcube allows me to save. I thought maybe running any command would sort of reset it but no, the navcube is magical in this case. FYI: There are no c3d objects but there are objects from LandFX (?).

[CADmgrMike]

I had another one of these pop up this week. Interestingly, it's always been the same type of drawing that we do over and over. It's strictly 2D with nothing but standard details in it.

This time I tried switching from modelspace to paperspace (no viewports in paperspace), and I was able to save after that. Close the drawing and the issue comes right back.

After some extensive testing, I found the culprit that was causing the issue (at least in this case)

I had a multileader style that referenced a block. (see pic below)

The block had two attributes that were set to be multiline attributes. I revised the block to have single line attributes, and the issue went away. 

Hope this helps someone.

[frank.loges]

Thanks Mike Porter!  Had the exact same problem, a construction note with a multiline attribute.  Edited the block to have a single line attribute and the problem went away.

[mserrano1967]

Rotating the view/UCS and then rotating it back worked great for me.

[slant]

I solved this with one of my standard quick fix tricks.

Thaw, turn on, unlock all layers, unload or detach all xrefs/images.

zoom extents, erase all, then deselect all objects with wrapping window and execute erase all command.

audit, purge, save.

[todd.santee]

I had a similar issue where I couldn't save certain files and received the "Object(s) added to DB too late during save..." error. For whatever reason, if I changed the view with the nav cube to anything other than top-down, the file would save. But if I tried to save the file with the nav cube set to top-down, it would give me the error again.

In my case, it seems the error was with a custom redefinition of the QSAVE command in my ACADDOC.lsp. The following lisp was being used to redefine the QSAVE command to include some purging. I can't tell what's wrong with the lisp, but if I get rid of this code from my ACADDOC.lsp, I no longer receive errors when saving.

(command "undefine" "qsave")

(defun c:qsave ()
   (setvar "cmdecho" 0)
   (command "-purge" "MA" "*" "n")
   (command "-purge" "R" "*" "n")
   (command ".qsave")
   (setvar "cmdecho" 1)
   (princ)
)

Hopefully this helps someone. Also, I'm open to any feedback on my apparently errant code.

[tjRYKQS]

I know this post/issue was a few years back however I recently also encountered this issue receiving an engineers CAD file which we could not save.  @dsulzsuggestion with attempting to save after using the AECTOCAD or EXPORTCAD on your original CAD file, and not the exported file, works well. File must be open after the export and then save afterwards. I do suggest also using the AUDIT/PURGE command prior to exporting.

[topknot]

I was getting:  Object(s) added to DB too late during save. Handles 2124F59 to 2124F59
2124F59: type AcDbRegAppTableRecord, owner 9 (AcDbRegAppTable).

I went through your steps, and what worked was that somehow it wasn't pointing at project shortcuts folder. I always set that to be associated. After I set it back to the right folder, I could save.

[XoaiChinChin]

I encountered a situation where when saving a file, Civil 3D software reported an error: "_qsave Object(s) added to DB too late during saving. Handles 4BCD3 to 4BCD3 4BCD3: type AecDbBlockRefPath, owner 7BB1 (AecDbBlockRefPathDictRec)".
I found one reason: one of the files we referenced to the current file had an error.
I fixed that error by opening and checking the referenced files, fixing the errors on that file and saving that file, then returning to the file that needed to be saved and pressing save and I saved the file successfully. Hope this can help colleagues do their work well. Wishing everyone a great day at work! 😄