Corrupt error message

[mmenendez]

I keep encountering this message (attached) and cannot seem to figure out why this is happening. Any Ideas? Thanks in advance!

[petervanko]

oUCH! Is it overconstrained? Referencing a lot of data???

[mmenendez]

I'm not sure. I don't even know what this 'element1233...' is!

[petervanko]

Find it and delete it...quick.

[sbrown]

Under tools>element id's type in that number and revit will find it and show it to you.

[mmenendez]

Do you know how I can find that element?

[mmenendez]

Under tools>element id's type in that number and revit will find it and show it to you.

This works...thanks!

[Mr Spot]

I've received this error quite a lot lately on one particular project. The element is always and imported or linked DWG file. The DWG file looks like it was originally created in ADT but it is completely 2D data.

Sometimes if i copy the cad file into a new clean template file it resolves the issue with that particular dwg file. However, this is not consistent and their appears to be some type of element in the dwg file that revit doesn't like... Yet to identify what it is.

[Gadget Man]

That fits!

How coincidental is that? Today, for the first time, it happened to me three times!

Sure enough, I had some elements imported from ACAD (made 2-D in ADT) long time ago, however what beats me is that: while it has been sitting happily and behaving well for 2-3 years now in one Revit annotation family (the whole page of details, some of them ex-ACAD), as soon as I used that family as a basis for a new one (using some of its elements) and tried to PURGE it of all the rubbish - it happened!

Not only this, but it also corrupted my whole file (can't open it anymore), REVIT simply disappeared from my screen and when I tried to open a back-up file (*.0001.rvt) it was already corrupted too... Even more! As soon as I made a few changes to the original (old) REVIT family (when creating a new one), I saved it with the new filename and also saved it as a different, second copy with a different file name again (I decided to name it differently then). And that first file (with the first file name) is corrupted too, even when this thing happened to the second file 20 minutes (and many commands) later!!! Figure that! :screwy:

I assume, that my original REVIT family is corrupted as well, although for some reason it doesn't display it yet and for now still behaves, therefore any file derived from it would be already corrupted too, but this time REVIT doesn't want to "swallow" it anymore...

The wonderful World of IT...

[BSchneider73]

I just started using this program recently on a project with multiple Autocad references and was getting this same error message. Since it was a small project I began erasing items and reloading the dwg references. What I found was that if there was solid hatch in the Autocad file I would get this error. If I erased or even changed the hatch pattern to something other than solid I did not get the error.

Hope this helps.

[FOUTJM]

we had the same problem and when we deleted or exploded hatch patterns things worked fine again.

[Gadget Man]

OK, good to know! Thanks!

So, from now on, as the rule do not import any DWG before removing/changing any solid hatch in it. Good tip.