Announcements
IMPORTANT. Forum in Read Only mode. You can no longer submit new questions or replies. Please read this message for details
Autodesk Architectural Desktop 2007 & Prior
Welcome to Autodesk’s Autodesk Architectural Desktop 2007 & Prior Forums. Share your knowledge, ask questions, and explore popular Autodesk Architectural Desktop 2007 & Prior topics.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

ADT3.3 to ADT2006: eNotOpenForWrite error

5 REPLIES 5
Reply
Message 1 of 6
grosstm
558 Views, 5 Replies

ADT3.3 to ADT2006: eNotOpenForWrite error

My office has just converted from ADT3.3 to ADT2006. So far this has gone pretty well, but a user has come to me with a problem and I can't figure out what it is. She's got one file that she can open and save normally in ADT3.3, but when she opens the same drawing in ADT2006, she gets:

"INTERNAL ERROR: !dbobji.cpp@6266: eNotOpenForWrite"

I've removed the xrefs, Recovered, Audited, Wblocked, Inserted, every trick I know to no avail. But the same thing happens every time. If I view the text window while I run Recover in ADT2006, I see the following:

Validating objects in the handle table.
Valid objects 2190 Invalid objects 0
Validating objects completed.
Creating new ACAD_MATERIAL dictionary
Creating new ACAD_COLOR dictionary
Creating new ACAD_TABLESTYLE dictionary
Used contingency data.

Salvaged database from drawing.

Fixed 14 cross link(s) in entity lists.
Opening an AutoCAD 2000 format file.

Auditing Header

DXF Name Current Value Validation Default
Door Display Props (LAYER)
eNullObjectId 0
Door Display Props (LTYPE)
eNullObjectId ByBlock
Door Display Props (Color)
Out of range ByBlock
Door Display Props (LAYER)
eNullObjectId 0

(these eNullObjectId's go on for quite a bit, covering all kinds of objects)

Then it tells me that it's recovered the drawing database, and then I get the Internal Error as indicated above. The file has been zipped and attached. Anyone have any idea what's happening here? Thank in advance!
5 REPLIES 5
Message 2 of 6
Anonymous
in reply to: grosstm

Hi,
Attached is a "fixed" drawing. One of the open Space Objects was misbehaving
in the drawing.
(I had to add a new Space Object so please check so it's correct, see
attached file.)

Hope this helps!
Thanks
Anna

wrote in message news:4873516@discussion.autodesk.com...
My office has just converted from ADT3.3 to ADT2006. So far this has gone
pretty well, but a user has come to me with a problem and I can't figure out
what it is. She's got one file that she can open and save normally in
ADT3.3, but when she opens the same drawing in ADT2006, she gets:

"INTERNAL ERROR: !dbobji.cpp@6266: eNotOpenForWrite"

I've removed the xrefs, Recovered, Audited, Wblocked, Inserted, every trick
I know to no avail. But the same thing happens every time. If I view the
text window while I run Recover in ADT2006, I see the following:

Validating objects in the handle table.
Valid objects 2190 Invalid objects 0
Validating objects completed.
Creating new ACAD_MATERIAL dictionary
Creating new ACAD_COLOR dictionary
Creating new ACAD_TABLESTYLE dictionary
Used contingency data.

Salvaged database from drawing.

Fixed 14 cross link(s) in entity lists.
Opening an AutoCAD 2000 format file.

Auditing Header

DXF Name Current Value Validation
Default
Door Display Props (LAYER)
eNullObjectId 0
Door Display Props (LTYPE)
eNullObjectId ByBlock
Door Display Props (Color)
Out of range ByBlock
Door Display Props (LAYER)
eNullObjectId 0

(these eNullObjectId's go on for quite a bit, covering all kinds of objects)

Then it tells me that it's recovered the draw
ing database, and then I get the Internal Error as indicated above. The
file has been zipped and attached. Anyone have any idea what's happening
here? Thank in advance!
Message 3 of 6
grosstm
in reply to: grosstm

I really appreciate the help Anna... but that didn't quite do it. The drawing opened fine, but now when I save the drawing I'm getting the same error. I've tried doing the whole wblock/recover/etc. routine on this file and it doesn't seem to help.

Just out of curiosity, what did you do to get this so I at least could open it? You mentioned there was something wrong with one of the space objects... what was it?
Message 4 of 6
grosstm
in reply to: grosstm

Quick extra note:

When I do hit save, I can sometimes see that the Multiply Owned Object error comes up briefly at the command line. But it flashes by too fast before it's gone and I can't see what entity is involved.
Message 5 of 6
Anonymous
in reply to: grosstm

oops sorry I missed that it was one more space on a frozen layer.
Please test the attached file.

wrote in message news:4874218@discussion.autodesk.com...
Quick extra note:

When I do hit save, I can sometimes see that the Multiply Owned Object error
comes up briefly at the command line. But it flashes by too fast before
it's gone and I can't see what entity is involved.
Message 6 of 6
grosstm
in reply to: grosstm

My user is reporting that the file is working just fine now. Thanks for all your help Anna!

Was this just a random corruption, or is there something we can do to make sure this doesn't happen in the future?

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Autodesk Design & Make Report