Reference Repair Utility

 
 
 

The Reference Repair Utility is a tool you can use to repair files in Vault with dangling relationships.

Release Availability

The Reference Repair Utility is supported by the following Vault editions:

Why Do We Need the Reference Repair Utility?

Under certain circumstances, it was possible to break historical CAD file relationships, resulting in unresolved file references or "dangling relationships." As a result, the parent versions would no longer point to any file, resulting in a dangling relationship. If a file has a dangling relationship, common Vault functions, such as Get/Check out, Where Used, and Change State can return an error or incorrect data. These errors can manifest as references not being shown under the Uses tab in Vault, or as a "file not found" error in your CAD application.

These dangling relationships must be addressed to avoid any problems gathering relationships. Service Pack 2 for Vault 2012 and Service Pack 1 for Vault 2013 introduce ways to repair dangling relationships.

Supported File Relationships
ImportantYou must ben an Administrator to repair references.

Auto-Repair vs. Manual Repair

With Service Pack 2 for Vault 2012 and Service Pack 1 for Vault 2013, dangling relationships in Workgroup, Collaboration, and Professional are automatically repaired during migration after installation of the service packs. However, dangling relationships in Autodesk Vault Basic must be repaired manually.

Auto-repair
Manual Repair

Working in a Replicated Environment

When working in a file-replication (Multi-Site) environment, it is best to perform the repair on one site to avoid duplicate efforts. The Reference Repair Utility processes only files that are on the current site. Files that are not yet replicated are not processed. As a best practice, replicate the files to the current site before you run the utility.

When working in a database-replication (Connected Workgroups) environment, you must have ownership of the parents being repaired to import the Reference Table on the server. As a best practice, before importing the Reference Table on the server, acquire ownership of all files that you are going to repair.