Re: FailFileInvalidChecksum Again!

Eric Sink wrote:
> For the item that's failing, you want to remove
> the cached baseline file inside the _sgvault
> folder.  cd into that working folder, then
> cd into the _sgvault folder inside it.  type
> dir.  You should see lots of files with numeric
> names such as 1311.46010, and also a file called
> "state".

Actually, removing only the cached baseline file will cause Vault
to have further problems during the next Get Latest.  You'll need
to remove all the contents of the hidden directory, including
the state file.  If you've already found the right _sgvault directory,
delete everything inside it.  Then delete (or move away) all the files
in your working folder.  Now you can do a Get Latest Version
for these files to get them back.  Vault 2.0 has improved CRC checking
during the management of these hidden files.

If you can't find your _sgvault folder (the default is to store them
outside of the working folders), I've written a small tool to help.

You can get the tool at the following URL:

ftp://ftp.sourcegear.com/pub/support/vault/ClientDiagnostics_(for_Vault_1.2).exe

Place the executable file in the directory where your Vault client
is installed (probably C:\Program Files\SourceGear\Vault Client\) and
run it from there.  Connect to the repository using the menu items,
navigate to the file that's causing you problems, and choose "Explore
Hidden Data Folder" from the file item's context menu.  

This is the _sgvault folder that contains the state information and
baselines for your selected file and its siblings.  The Client Diagnostics
tools can also show you the internal IDs of files and folders.  I'm 
planning to add a knowledge base article on its use later today.

-- 
Shaw Terwilliger <[email protected]>
SourceGear Corporation