Vault Client error when connecting to repository

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
phether
Posts: 4
Joined: Wed Jun 02, 2004 12:48 pm

Vault Client error when connecting to repository

Post by phether » Fri Oct 22, 2004 9:15 am

I am suddenly getting this error when trying to connect to a Repository with the Vault Client.
"Could not find file "C:\Documents and Settings\Paul Hetherington\Application Data\SourceGear\Vaule_1\Client\500fa77f-43e8-83be-044f5980e8d9\phetherington\_sgvault\740562247\4148.17425"

This occured after I tried opening a solution with Visual Studio 2003 and an error say that it could not find the repository and tried to make me work in offline mode.

I had to end task both cases to get out.\

Thank You
Paul

sterwill
Posts: 256
Joined: Thu Nov 06, 2003 10:01 am
Location: SourceGear

Post by sterwill » Fri Oct 22, 2004 12:22 pm

Did you receive this message simply from connection to a repository with the Vault Windows Forms client? Or were you performing some sort of operation (Get Latest Version, Check Out, etc.)?
Shaw Terwilliger
SourceGear LLC
`echo sterwill5sourcegear6com | tr 56 @.`

phether
Posts: 4
Joined: Wed Jun 02, 2004 12:48 pm

Post by phether » Fri Oct 22, 2004 2:20 pm

I get this error as soon as I run the Vault Client and select a specific Repository. Other Repositories work fine.
Right now I am forced to work in Offline mode in VS.NET 2003 :(
-Paul

sterwill
Posts: 256
Joined: Thu Nov 06, 2003 10:01 am
Location: SourceGear

Post by sterwill » Fri Oct 22, 2004 2:41 pm

It seems like a baseline file is missing from the hidden folder.

A work-around would be to delete the folder "C:\Documents and Settings\Paul Hetherington\Application Data\SourceGear\Vault_1\Client\500fa77f-43e8-83be-044f5980e8d9\phetherington\_sgvault\740562247\",
and all the files in it. This would have the side-effect of turning all files "Unknown" in one of your working folders. It's hard to tell which one would be affected, because those numbers near the end of the path are a one-way hash from a disk path. You can always rename that folder instead of deleting it (so you can rename it back if there were any changes you hadn't yet checked in).
Shaw Terwilliger
SourceGear LLC
`echo sterwill5sourcegear6com | tr 56 @.`

Post Reply