INTERNAL ERROR

[James T.]

We have been getting several errors with this Internal Error saying

!U:\global\src\corecad\CORESRC\scandr.cpp@2274: eLockViolation

or

!U:\Global\scr\objectDbx\DB\Imp\src\dbuilt.cpp@975:eHandler use

Any help would be appreciated because it crashes CAD and does not allow a
save or if it does allow a recovery save it does not work correctly.

[R.K. McSwain]

"James T." <jtobbe@mindelscott.com> wrote

Any help would be appreciated because it crashes CAD and does not allow a
save or if it does allow a recovery save it does not work correctly.

If you are getting that dialog that says "AutoCAD can not continue, do you want to save your changes?", always say NO. If you answer yes, then any corrupt data in memory is written to disk, trashing your drawing in the process.

[James T.]

How do you keep it from giving you this error in the first place

"R.K. McSwain" <rkmcswain@yahoo.com> wrote in message
news:bodv0r$qor$1@update.carlsonsw.com...
"James T." <jtobbe@mindelscott.com> wrote

Any help would be appreciated because it crashes CAD and does not allow a
save or if it does allow a recovery save it does not work correctly.

If you are getting that dialog that says "AutoCAD can not continue, do you
want to save your changes?", always say NO. If you answer yes, then any
corrupt data in memory is written to disk, trashing your drawing in the
process.

[R.K. McSwain]

"James T." <jtobbe@mindelscott.com> wrote

How do you keep it from giving you this error in the first place

If I knew the answer to that I wouldn't be sitting here...
Sorry, couldn't resist

Seriously, internal errors in AutoCAD can be caused by most anything and are very difficult, if not impossible to track down. "eLockViolation" can mean that an object was locked and an application is trying to write to that entity. I have never seen "eHandler use".

Does this happen at random on any drawing, or just in a certain drawing? Can you provide a set of steps to cause this error to occur?

[James T.]

Seems to be randomly happening different machines and different drawings.
"R.K. McSwain" <rkmcswain@yahoo.com> wrote in message
news:boe6tk$uf0$1@update.carlsonsw.com...
"James T." <jtobbe@mindelscott.com> wrote

How do you keep it from giving you this error in the first place

If I knew the answer to that I wouldn't be sitting here...
Sorry, couldn't resist

Seriously, internal errors in AutoCAD can be caused by most anything and are
very difficult, if not impossible to track down. "eLockViolation" can mean
that an object was locked and an application is trying to write to that
entity. I have never seen "eHandler use".

Does this happen at random on any drawing, or just in a certain drawing? Can
you provide a set of steps to cause this error to occur?

[R.K. McSwain]

"James T." <jtobbe@mindelscott.com> wrote

Seems to be randomly happening different machines and different drawings.

That would indicate to me that an application is causing the error, as opposed to a drawing being corrupted.
Does it happen when you eliminate SurvCADD from the equation (ie: running vanilla AutoCAD?)

[James T.]

Have not tried just cad but I will
"R.K. McSwain" <rkmcswain@yahoo.com> wrote in message
news:bog8bj$kmp$1@update.carlsonsw.com...
"James T." <jtobbe@mindelscott.com> wrote

Seems to be randomly happening different machines and different drawings.

That would indicate to me that an application is causing the error, as
opposed to a drawing being corrupted.
Does it happen when you eliminate SurvCADD from the equation (ie: running
vanilla AutoCAD?)

[James T.]

Disabled Virus Protection seemed to do the trick
"James T." <jtobbe@mindelscott.com> wrote in message
news:bog9oo$lac$1@update.carlsonsw.com...

Have not tried just cad but I will
"R.K. McSwain" <rkmcswain@yahoo.com> wrote in message
news:bog8bj$kmp$1@update.carlsonsw.com...
"James T." <jtobbe@mindelscott.com> wrote
Seems to be randomly happening different machines and different
drawings.

That would indicate to me that an application is causing the error, as
opposed to a drawing being corrupted.
Does it happen when you eliminate SurvCADD from the equation (ie: running
vanilla AutoCAD?)

[Stephen Rhodes]

We have recently introduced Carlson into our organisation and have found
SurvCADD (autocad) "crashes" quite often.
("Save" gets used a lot now!)

We cannot pinpoint the exact circimstances- in about 25% of crashes, autocad
just closes and we do not get a chance to do anything. Other crashes allow
us to save and recover drawing - and almost all the time there are no errors
reported after the recovery (audit).
What can we do to find these errors so that we can feed information back to
Carlson????

Thanks in advance...Stephen


"James T." <jtobbe@mindelscott.com> wrote in message
news:boe7c0$ul8$1@update.carlsonsw.com...

Seems to be randomly happening different machines and different drawings.
"R.K. McSwain" <rkmcswain@yahoo.com> wrote in message
news:boe6tk$uf0$1@update.carlsonsw.com...
"James T." <jtobbe@mindelscott.com> wrote
How do you keep it from giving you this error in the first place

If I knew the answer to that I wouldn't be sitting here...
Sorry, couldn't resist

Seriously, internal errors in AutoCAD can be caused by most anything and
are
very difficult, if not impossible to track down. "eLockViolation" can mean
that an object was locked and an application is trying to write to that
entity. I have never seen "eHandler use".

Does this happen at random on any drawing, or just in a certain drawing?
Can
you provide a set of steps to cause this error to occur?