Fatal Realdwg Error !!dbobji.cpp@8501: eNotOpenForWrite, fatal error during save

[Anonymous]

Inventor 2019 Crash issue

I have a significant crash issue with a very complicated .dwg file that is associated with a very complex assembly that automatically builds itself. There is a lot of rules in both the .dwg and .iam files, but i have been using these through both the 2017 and 2018 iterations without any problems. Now with 2019 every time I make changes to the .dwg file and attempt to save it the whole program crashes and I get an error message. I have included it here as a screen capture.

Someone please help!

[johnsonshiue]

Hi! I am sorry I am not sure if the issue is the same. Are you using Inventor or AutoCAD? Could you describe the exact workflow leading to the error message?

Many thanks!

[Anonymous]

hola,
gracias por tu interés
trabajo con Autocad Map 3D v. 2019, pero el error no lo encuentro descrito específicamente para mi programa;
he observado que los errores internos se producen en todos los productos de Autodesk y, en mi desesperación, estoy investigando por todas partes.
El error surge al intentar dar estilo a bloques consultados del dibujo actual o de un dibujo asociado (es decir, sustituir la visualización de los bloques originales dibujados por nuevos bloques de símbolo).
Justo antes de que aparezca el mensaje de error se puede apreciar que la operación se ejecuta exclusivamente en un único bloque de todos los presentes.
No sé si esto ayuda a identificar y subsanar el error.

Hello,
Thanks for your interest
I work with Autocad Map 3D v. 2019, but I do not find the error described specifically for my program;
I have observed that internal errors occur in all Autodesk products and, in my desperation, I am investigating everywhere.
The error arises when trying to style blocks of the current drawing or an associated drawing (that is, replace the display of the original blocks drawn by new symbol blocks).
Just before the error message appears, it can be seen that the operation is executed exclusively in a single block of all those present.
I hope this helps to identify and correct the error.

regards

[johnsonshiue]

Hi! Many thanks for your clarification! I am an expert on Inventor and I know a little bit of AutoCAD. But, I am nowhere to be called an AutoCAD expert. So, please bear with me if I am not making sense.

If I recalled correctly, this error has something to do with file version. AutoCAD is very versatile on file versions. Older releases of AutoCAD can read dwg files saved from later releases of AutoCAD, as long as the file version is supported by the older version. For example, on AutoCAD 2019, you can save an AutoCAD 2019 file as dwg 2014 format. Then open it on AutoCAD 2014 without a problem.

In your case, it sounds like you open an older version of dwg file and you are editing in a way that it has to be saved in a newer version. If the operation proceeds, the file cannot be opened in older AutoCAD. To check that, you can open it on 2019 and see the prompt text in command line. It should tell you what version of the dwg file it is.

Many thanks!

[Anonymous]

hola,
olé por tu buena memoria;
ahora (v.2020) las cosas ya no son exactamente así, al abrir un archivo se limita a constatar que el archivo es de confianza, creado en una aplicación de Autodesk, sin mencionar la versión original en que fue creada.
Yo también sospecho que es un problema de versiones pero no encuentro solución alguna (nuestra suscripción no ampara el uso de las versiones no problemáticas en que fueron creados nuestros archivos -2015-).
En este momento el problema de éste y otros problemas de errores internos están en manos del soporte de Autocad Map 3D y no me queda más que esperar sus soluciones o encontrar alternativas de software para no perder nuestros archivos y su funcionalidad.
(trabajamos con cartografía, se trata de archivos que tienen una larga vida y sus datos son incrementales, acumulativos)
Muchas gracias por tu interés.

Hello,
bravo for your good memory;
now (v.2020) things are not exactly like this anymore, when opening a file it is limited to verify that the file is trustworthy, created in an Autodesk application, without mentioning the original version in which it was created.
I also suspect that it is a version problem but I can not find any solution (our subscription does not cover the use of the non-problematic versions in which our files -2015- were created and manipulated lately).
At this moment this and other problems of internal errors are in the hands of Autocad Map 3D support and I can only wait for their solutions or find alternative software to not lose our files and their functionality.
(We work with cartography, it's about files that have a long life and their data is incremental, cumulative, version compatibility should not fail without an explicit warning)
Thank you very much for your interest and your time
Greetings.

[johnsonshiue]

Hi! Here is what I found on AutoCAD knowledge base. Could you take a look at the article and see if it works? If it still does not work. I suggest you post it on AutoCAD forum and the team will be able to help you further.

https://knowledge.autodesk.com/support/autocad/troubleshooting/caas/sfdcarticles/sfdcarticles/Error-...

Many thanks!

[Anonymous]

I already knew him, thanks in any way

--


//Este correo electrónico y, en su caso, cualquier fichero anexo al
mismo, puede contener información de carácter confidencial
exclusivamente dirigida a su(s) destinatario(s). Queda prohibida su
divulgación, copia o distribución a terceros sin la previa autorización
de CALFENSA PROYECTOS, S.L. En caso de haber recibido este correo por
error, le rogamos notifique inmediatamente esta circunstancia a la
dirección electrónica lopd@calfensa.com. Le agradecemos de antemano su
colaboración.
//

//// //CALFENSA PROYECTOS, S.L. le informa que trata, como responsable,
sus datos de carácter personal incluidos en esta comunicación, recabados
de usted o de la entidad en la que presta servicios, con el fin de
mantener y gestionar los servicios contratados y demás relaciones
comerciales. Usted puede ejercitar sus derechos de acceso,
rectificación, cancelación y oposición en la dirección anteriormente
indicada. //

[insmuratturna]

I had same problem. Check code line priority, for example check lines below 

Wrong priority:

using (Transaction tr = db.TransactionManager.StartTransaction())
{
   for (int i = 0; i < yer.Count; i++)
   {
       BlockTable bt = tr.GetObject(db.BlockTableId, OpenMode.ForWrite) as BlockTable;
       BlockTableRecord btr = tr.GetObject(bt[BlockTableRecord.ModelSpace], OpenMode.ForWrite) as BlockTableRecord;

    using (DBText text = new DBText())

Correct :

 for (int i = 0; i < yer.Count; i++)
            {

                using (Transaction tr = db.TransactionManager.StartTransaction())
                {

                    BlockTable bt = tr.GetObject(db.BlockTableId, OpenMode.ForWrite) as BlockTable;
                    BlockTableRecord btr = tr.GetObject(bt[BlockTableRecord.ModelSpace], OpenMode.ForWrite) as BlockTableRecord;

                    using (DBText text = new DBText())
                    {

[george1985]

Hi @insmuratturna 
Thank you for posting the solution to your problem.
Can you explain what was wrong with the first code snippet? There should never be a loop inside the transaction?
Or did I misunderstand. Thank you for the reply.

[MpatelGTAKT]

This is very late, but for anyone that comes across this in 2024, I tried all the methods that were presented in this forum and was unable to resolve it. The only way I could solve it after doing a bunch of research was to delete the old drawing and recreate it. I know that's very tedious, but I spent hours trying to get this resolved with forums like this and with Autodesk assistance. It took me 1/10 of the time to just redo the drawing. Hope this helps!