Results 1 to 7 of 7

Thread: INTERNAL ERROR: !dbobji.cpp@7319: eNotOpenForWrite

  1. #1
    Member
    Join Date
    2012-04
    Posts
    3
    0 Did you find this post helpful? Yes

    Exclamation INTERNAL ERROR: !dbobji.cpp@7319: eNotOpenForWrite

    I keep getting this error with no rhyme or reason for it. INTERNAL ERROR: !dbobji.cpp@7319: eNotOpenForWrite
    It will sometimes crash while I'm away from my desk. Any help with this would be appreciated.

  2. #2
    Forum Manager, Administrator Ed Jobe's Avatar
    Join Date
    2000-11
    Location
    Turlock, CA
    Posts
    4,962
    0 Did you find this post helpful? Yes

    Default Re: INTERNAL ERROR: !dbobji.cpp@7319: eNotOpenForWrite

    There is a reason, you're just not seeing it. With the info you've provided, all I can tell you is that the c++ dll is failing at lin3 7319 of module dbobji. Something is trying to edit an object in the dwg when it is not able to. Try to think of things that might have changed recently. When did the problem start? Is it only on one dwg? Have you tried recovering it? If there is more to the error message, show that.
    C:> ED WORKING....

  3. #3
    Certified AUGI Addict jaberwok's Avatar
    Join Date
    2000-12
    Location
    0,0,0 The Origin
    Posts
    8,386
    0 Did you find this post helpful? Yes

    Default Re: INTERNAL ERROR: !dbobji.cpp@7319: eNotOpenForWrite

    There are a lot messages about this but I've only found one which appears to provide a solution so look here and see if it helps you.
    John B

    "You can't convince a believer of anything; for their belief is not based on evidence, it's based on a deep-seated need to believe." - Carl Sagan

  4. #4
    Member
    Join Date
    2012-04
    Posts
    3
    0 Did you find this post helpful? Yes

    Default Re: INTERNAL ERROR: !dbobji.cpp@7319: eNotOpenForWrite

    Yeah...I saw this and forwarded it on to the people who need to know...Thanks for the reply though.

  5. #5
    Member
    Join Date
    2012-04
    Posts
    3
    0 Did you find this post helpful? Yes

    Default Re: INTERNAL ERROR: !dbobji.cpp@7319: eNotOpenForWrite

    We do have some custom menus and some of the commands change settings. It does it sporadically. Like two weeks ago, it crash on me about almost a dozen times during the day. I needed to get a drawing at ASAP, so I soldiered through it. At the end of the day, I restarted my computer and the next morning it ran fine. Yesterday it crashed 4 times in the morning (2x before and 2x after I rebooted) and then it seem to run fine. This morning it crashed 3x and have not rebooted, but it hasn't crashed in awhile. I don't see any trend of being in certain drawings or doing certain commands that is causing it. It will sometimes crash while I'm away from my desk.

  6. #6
    Member
    Join Date
    2007-04
    Posts
    10
    0 Did you find this post helpful? Yes

    Default Re: INTERNAL ERROR: !dbobji.cpp@7319: eNotOpenForWrite

    I was getting this error on a few client drawings just using the Design Center and clicking on any of the styles or blocks. I didn't find any file corruption using audit or recover so I used the reference manager to look for any unresolved refernces. In my case there were missing Plot Configuration files and CTB's. I just copied my standard pc3 and ctb files renaming them to the missing files and the error crashing stopped. This is a guess, on my part, but my thinking is "eNotOpenForWrite" means AutoCAD is looking for something but can't find it.

  7. #7
    Forum Manager, Administrator Ed Jobe's Avatar
    Join Date
    2000-11
    Location
    Turlock, CA
    Posts
    4,962
    0 Did you find this post helpful? Yes

    Default Re: INTERNAL ERROR: !dbobji.cpp@7319: eNotOpenForWrite

    John, the error message doesn't mean that. All its telling us is that the line of code in the dll where the error occurs was expecting to be able to write to a table in the dwg database, but the record was not able to be edited. I would submit this as a bug with the details you have. It seems that this dll did something that didn't account for the case where some table data ( i.e. ctb, etc) was missing and at some point after that, it cascaded to the point where an error occurred. I can't tell you more than that without doing some research. But regardless, this is a bug that should be reported. Its nice that you can document repeatable circumstances.
    C:> ED WORKING....

Similar Threads

  1. INTERNAL ERROR: !dobji.cpp@672:eNotOpenForWrite
    By simonaster in forum AutoCAD Civil 3D - General
    Replies: 5
    Last Post: 2009-08-05, 02:24 PM
  2. INTERNAL ERROR: !dbobji.cpp@6769: eNotOpenForWrite
    By rlehman.124981 in forum Software
    Replies: 3
    Last Post: 2008-12-17, 02:17 PM
  3. INTERNAL ERROR: !dbobji.cpp@6769: eNotOpenForWrite
    By mserapiglia in forum Software
    Replies: 3
    Last Post: 2008-05-20, 09:41 PM
  4. Error when running sub - eNotOpenForWrite
    By bweir in forum Dot Net API
    Replies: 1
    Last Post: 2006-10-23, 03:54 PM
  5. Crash - !dbobji.cpp@6266:eNotOpenforWrite
    By CADMama in forum AutoCAD General
    Replies: 12
    Last Post: 2006-07-12, 04:35 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •