Vault Client source file status unknown

[rickgadd]

We are running Vault 2.0.6 and periodically over the last few months we started seeing source files listed more than one time in a project folder. When this happened we couldn't do a get, check out, or checkin on the file.

One thing we tried that worked to correct the problem was to delete the

C:\Documents and Settings\{{username}}\application data\SourceGear\Vault_1\Client\430DB8B3-ACF1-434A-A4E4-17D08F97F424

(the \430DB8B3... is just some GUID)

folder.

This worked for a while but now my status on all of my source files is "unknown". I can't check out or checkin.

Is there a way to fix this? Do I need to delete a different folder? Is there a utility that will setup my client folders again? Should I uninstall and reinstall the client?

I fixed a few critical files by renaming the file in Vault, then adding the file back in, but that will lose my revision history.

-Rick

[sterwill]

You don't want to delete the whole GUID-named folder if you just want to remove the cached repository structure. See this KB article for the specific files to delete (CacheMember_LastStructureGetTime and CacheMember_Repository). Deleting the whole GUID folder will remove baseline files and version information about all your working folders. It won't change any server-side data.

To make the Unknown files turn into files with blank (normal) status, you can simply perform a "get latest version" to retrieve the most recent repository version to your working folder. Any Unknown files in the way will be backed up to the "_sgbak" folder, then overwritten. Then you can use these files like you would normally.