Corrupt element will be deleted

[Rick Houle]

The message reads "at some point before this session... element XXXX became corrupt and will be deleted in the recovery file."

The problem is, it keeps occurring, and when it does the entire team is severed from the central file. Because Revit will delete the corrupt element upon next open, we cannot find out what the recurring problem is being caused by.

Attached is one of the small detail families we tracked it into.
CAN ANYONE PLEASE TELL ME what we are doing wrong to create this problem for ourselves..??!?

[aggockel50321]

When opening your family with RAC 2009, I got the attached warning message.

If you can open the file without it deleting, you can look up, and remove or fix the offending element.

[Rick Houle]

That is my problem. I cannot open the file without Revit automatically deleting the object.

This end user is able to "Load into Project" this bad family. He is also able to save and close the bad family. But once the central has hold if it, everyone's local file becomes severed from central. Losing a teams worth of work each time.

It happens from the same person's PC each time. His journal file does not respond for me when i drag it to icon.

(shouldn't i be able to review an end-user journal?)

[Kevin Janik]

You might be able to open the journal file and see what happened when it loads and then deletes the element. It might report the id of the offending element and what it was. The journal is for things like that at the factory. Also, sending the file to them would be good. They can figure it out and it might help them see what they need to do to help things like this not happen for users again without telling the user what is the offending element. If they do not know about it others will probably have the same problem.

Below is the area of the journal file that goes bad from looking at a non problematic journal file.

' 6:< MessageBox "Element 3980 became corrupt at some time before this session. To continue with this project, save a recovery file. In the recovery file, this element will be deleted to fix the problem."
' H 04-Jun-2008 12:11:26.077; 6:<
Jrn.Data "MessageBox" _
, "IDOK", "Element 3980 became corrupt at some time before this session. To continue with this project, save a recovery file. In the recovery file, this element will be deleted to fix the problem."
' 6:< 04-Jun-2008 12:11:26.077; Assertion failed: line 1347 of .\DocView\ElemTable.cpp
' 3:< Before : Destroy Display Manager
' 3:< System (KB) [Available / Total ] [Revit Memory Usage (KB) ---------------- ]
' 3:< RAM Statistics: 964328 / 2095532 168856=InUse 182852=Peak 962348=Delta
' 3:< VM Statistics: 1778772 / 2097024 126228=InUse 144116=Peak 192024=Delta
' 3:< After : Destroy Display Manager
' 3:< System (KB) [Available / Total ] [Revit Memory Usage (KB) ---------------- ]
' 3:< RAM Statistics: 964328 / 2095532 168856=InUse 182852=Peak 962348=Delta
' 3:< VM Statistics: 1778772 / 2097024 126228=InUse 144116=Peak 192024=Delta
' 3:< [TKY] OLEStreamLock::relinquishLock: m_pArchive already committed or aborted?
' 3:< DBG_WARN: Bad BlockTimer nesting. At 2, expected 3, located 3 -- recovering: line 262 of .\BlockTimer.cpp.
' 0:< DBG_WARN: Bad BlockTimer nesting. At 1, expected 0, located 1 -- probably cannot recover: line 262 of .\BlockTimer.cpp.
' C 04-Jun-2008 12:11:26.343; 0:< ->processShellCommand
' C 04-Jun-2008 12:11:26.343; 0:< ProcessShellCommand FileDDE
' C 04-Jun-2008 12:11:26.343; 0:< <-processShellCommand
' C 04-Jun-2008 12:11:26.343; 0:< <-InitInstance
' C 04-Jun-2008 12:11:26.374; 0:< appPriv idle
' 0:< 04-Jun-2008 12:11:27.312; Exception occurred
' 0:< 04-Jun-2008 12:11:27.312; ExceptionCode=0xc0000005 ExceptionFlags=0x00000000 ExceptionAddress=77573080
' 0:< System (KB) [Available / Total ] [Revit Memory Usage (KB) ---------------- ]
' 0:< RAM Statistics: 964740 / 2095532 165412=InUse 182852=Peak 965380=Delta
' 0:< VM Statistics: 1779584 / 2097024 123784=InUse 144116=Peak 193656=Delta
' 0:< MessageBox "An unrecoverable error has occurred. The program will now be terminated. All of your data has been recently saved, so there is no need to create recovery files."
' H 04-Jun-2008 12:11:31.718; 0:<
Jrn.Data "MessageBox" _
, "IDOK", "An unrecoverable error has occurred. The program will now be terminated. All of your data has been recently saved, so there is no need to create recovery files."
' 0:< 04-Jun-2008 12:11:31.718; program terminated


Maybe the problem is with an AutoCAD block since the error in bold above I highlighted refers to a " ' 3:< DBG_WARN: Bad BlockTimer nesting. At 2, expected 3, located 3 -- recovering: line 262 of .\BlockTimer.cpp."

Kevin

[Rick Houle]

Interesting, thanks for the insight. I will look at the resulting journal.

So, let's say it is an Autocad block... (i do believe the problem is caused by cad residue)
After first couple violations i had the end user "clean" his families of all cad, copy-paste the Revit work into a clean template and use NO CAD from there... I do not see signs of cad residue in the family...

Back in cad days, you could dig into the dbase to find bad stuff... here in Revit, if i see no cad mess in the Object Styles or Imported Categories i dont know where else to look -- is there a way to dig into the Revit dbase to "SUPER PURGE" some bad, invisible info..???