Jump to content

Wierd Audit / Purge Issue


Arizona

Recommended Posts

ACAD Civil 3D Land Desktop Companion 2009

 

This happens every once and a while and I've long been curious to what is going on.

I run an audit, it finds errors.

Run the audit again, no more errors.

Purge.

-the only thing it removes is one layer: $AUDIT-BAD-LAYER

Run audit again

-all the same errors are found again.

 

After the audit, $AUDIT-BAD-LAYER is empty. No entities on that layer. Multiple methods confirm that the layer is empty.

 

So - why does removing the layer $AUDIT-BAD-LAYER recreate the errors?! What exactly is going on there? Even if I just delete the layer via the layer dialog box, instead of purging, the errors return.

 

Below is what Audit is returning on the drawing this is happening in this morning.

 

 

 

Command: AUDIT

Fix any errors detected? [Yes/No] : Y

 

Auditing Header

 

Auditing Tables

 

Auditing Entities Pass 1

Pass 1 3100 objects audited

Auditing Entities Pass 2

Pass 2 2400 objects auditedAcDbLine(112E6) Invalid layer eWasErased

$AUDIT-BAD-LAYER

AcDbLine(112E7) Invalid layer eWasErased $AUDIT-BAD-LAYER

AcDbLine(112E8) Invalid layer eWasErased $AUDIT-BAD-LAYER

AcDbLine(112E9) Invalid layer eWasErased $AUDIT-BAD-LAYER

AcDbMText(112EA) Invalid layer eWasErased $AUDIT-BAD-LAYER

AcDbSolid(112EB) Invalid layer eWasErased $AUDIT-BAD-LAYER

AcDbSolid(112EC) Invalid layer eWasErased $AUDIT-BAD-LAYER

Pass 2 2500 objects auditedAcDbLine(112F0) Invalid layer eWasErased

$AUDIT-BAD-LAYER

AcDbLine(112F1) Invalid layer eWasErased $AUDIT-BAD-LAYER

AcDbLine(112F2) Invalid layer eWasErased $AUDIT-BAD-LAYER

AcDbLine(112F3) Invalid layer eWasErased $AUDIT-BAD-LAYER

AcDbSolid(112F4) Invalid layer eWasErased $AUDIT-BAD-LAYER

AcDbSolid(112F5) Invalid layer eWasErased $AUDIT-BAD-LAYER

AcDbMText(112F6) Invalid layer eWasErased $AUDIT-BAD-LAYER

AcDbLine(112FA) Invalid layer eWasErased $AUDIT-BAD-LAYER

AcDbLine(112FB) Invalid layer eWasErased $AUDIT-BAD-LAYER

AcDbLine(112FC) Invalid layer eWasErased $AUDIT-BAD-LAYER

AcDbLine(112FD) Invalid layer eWasErased $AUDIT-BAD-LAYER

AcDbSolid(112FE) Invalid layer eWasErased $AUDIT-BAD-LAYER

AcDbSolid(112FF) Invalid layer eWasErased $AUDIT-BAD-LAYER

AcDbMText(11300) Invalid layer eWasErased $AUDIT-BAD-LAYER

AcDbLine(11304) Invalid layer eWasErased $AUDIT-BAD-LAYER

AcDbLine(11305) Invalid layer eWasErased $AUDIT-BAD-LAYER

AcDbLine(11306) Invalid layer eWasErased $AUDIT-BAD-LAYER

AcDbSolid(11307) Invalid layer eWasErased $AUDIT-BAD-LAYER

AcDbSolid(11308) Invalid layer eWasErased $AUDIT-BAD-LAYER

AcDbMText(11309) Invalid layer eWasErased $AUDIT-BAD-LAYER

Pass 2 3100 objects audited

Auditing Blocks

 

81 Blocks audited

Total errors found 27 fixed 27

Erased 0 objects

 

*********

Funny how "8"+")" returns the cool dude smilie.

*********

Thanks in advance for any light you can shed on this strange phenomenon.

-Jeff

Link to comment
Share on other sites

That is one bad layer. It can drive one nuts when trying to get rid of it. For me, it often appears after running a purge or an audit. In my case, it appears most often when I'm dealing with files exported from Revit. I haven't been able to find what is causing that layer to appear. Using LAYDEL usually gets rid of it permanently. My theory is that, along with deleting the layer, the entity causing the error is also deleted. I don't think that the entity has anything on that layer. It just causes an error that creates the layer. Thusly, you are able to delete it, only to have it reappear.

Link to comment
Share on other sites

Well, strange as it may seem, closing the drawing and reopening it cured the problem. :x

Upon reopening, the errors were gone.

Kind of like the old rule - when in doubt, reboot.

 

But, Rob - I had no prior knowledge of the LAYDEL command! It's Awesome!

Tried it out, and thats a keeper.

Thank You!

Link to comment
Share on other sites

It is a powerful one. Be aware that it does delete everything that is on the layer, blocks, objects within blocks, etc.

Link to comment
Share on other sites

That is one bad layer. It can drive one nuts when trying to get rid of it. For me, it often appears after running a purge or an audit. In my case, it appears most often when I'm dealing with files exported from Revit. I haven't been able to find what is causing that layer to appear. Using LAYDEL usually gets rid of it permanently. My theory is that, along with deleting the layer, the entity causing the error is also deleted. I don't think that the entity has anything on that layer. It just causes an error that creates the layer. Thusly, you are able to delete it, only to have it reappear.

 

Should LAYDEL fail to do the trick, and only suggested as an imperfect workaround, for an imperfect drawing you can use LAYMRG and merge it into your 0 layer, or any other you deem the most appropriate.

I used to have that happen a lot with a macro I use for final -Purge and Audit of finished drawings. I never really figured it out either, but there were no Revit issues involved with mine. It hasn't happened

for a long time now. I would always run the regular PURGE after running my macro to make sure that it hadn't generated such a bad layer.

Just remember there aren't any REALLY BAD layers, just BAD draftspeople, present company excluded. :beer:

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...