Error message when linking DWG to RVT

[Sahay_R]

One of our projects gives this error when it is being opened - 

This continues, even after PURGE, OVERKILL, unfreezing layers and deleting a gazilion objects floating around, WBLOCK, moving the location of 0,0, moving the BASE of the DWG - you name it.

What did I miss? I am just trying to keep the RVT as free of warnings as possible. DWG after all the steps taken above is attached.

[Viveka_CD · Accepted solution]

Hi @Sahay_R

Which version of Revit are you using?

Perform the following steps in the order listed:
Open the drawing file.
Purge Registered Applications (from the command line):
Type -PURGE.
"R" for Regapps (registered applications), then Enter.
"N" when asked to verify each name to be purged, then Enter.
Type PURGE at the command line. With all checkboxes checked on, click Purge All.
Audit and fix any errors:
Type AUDIT at the command line.
"Y" for Yes to fix any errors, then Enter.
Save the drawing.

If the drawing persists with problems, try the following steps:
Ensure all layers are on, thawed, and unlocked.
Detach all external references (XREFs).
Write Block all necessary information in the file out to a new drawing (from the command line):
Type WBLOCK at the command line.
Under Source, select "Objects".
Under Objects, click the "Select objects" icon.
Use a selection window to choose only the necessary objects from the file (do not simply type ALL).
Set file path and name, then OK.
Open a new blank drawing file.
Insert the file created in Step 3 (from the command line):
Type INSERT at the command line.
Select the file.
Uncheck "Specify On-screen" and check "Explode", then OK.
Type PURGE at the command line. With all checkboxes checked on, click Purge All.
AUDIT and fix any errors.
Type SAVEAS and create a new file name.

Let me know if that helps. 

Regards,

[Sahay_R]

I missed the -PURGE and the inserting the WBLOCKed file into a clean file. This links nicely. 

FWIW if in -PURGE you select all, you do not need to PURGE again.....

[Viveka_CD]

@Sahay_R I'm happy to hear that on a Tuesday morning!