Major Vault Issues

[jakana]

Since this morning our Vault server has been throwing errors whenever any transaction is attempted. I checked the server for any disk space or SQL Server problems, but everything checked out fine.

I used the Admin Tool to create a backup of the repository and did a backup of the sgvault database. I then tried a restore of a previous respository backup and we're still having the same problems, only now the latest repository backup doesn't show up in the admin tool so now I can't get it back, either!

I'm not sure what to do next. Help!

[jakana]

I dropped the sgvault database and did and complete restore and reboot of the server, and things appear to be working normally again.

...except for a single file (as near as I can tell it's isolated to this file). This one file shows a current version of "3", but there are really only 2 versions (which is what I see if I do a "View History" on the file).

Whenever I try and checkout the file, the Vault client either hangs *or* it returns an error message:

Check out failed for $/Projects/KlaussnerFurniture/servicenet.klaussner.com/Code/ServiceNet.WebService/ServiceNet.asmx.vb: Could not get the requested version of the object.


I have a local copy of the latest version, but I can't use Vault for this file because I can't check in/out, can't delete the file from Vault (returns another error), etc. We really need source control on this file and it needs to be in this folder with this filename.

Any ideas how to correct this?

[lbauer]

Did you delete your client-side cache after you restored the database? You cache may be out of sync because it has information from the previous database.

Info on client-side cache here:
http://support.sourcegear.com/viewtopic.php?t=6

[jakana]

Yes, I've deleted the client-side cache, but that didn't help.

Ultimately, I re-organized the project into a different folder and just added the whole thing into Vault in the new location. I still can't delete the old project, which I don't like at all, but I don't know what else to do until I can find a workaround.

Note: I now believe that the root cause of this problem was that there were a few files (including this problematic one) that were checked out when the Vault database was backed up. Somehow (later), Vault incremented the version number but didn't actually record the changes in the database, so now version #3 is not in the database but Vault believes that is the latest version.

I tried to revert back to version #2, but that is throwing an error, too. Basically, everything I've tried to "do" to that file via the Vault client throws an error.

I got desperate enough that I even started poking around the Vault SQL Server database directly (but I didn't change anything). Is it possible to tell Vault that the latest version is actually 2, not 3?

At this point, all I want to do is to be able to delete the old project, including this file, from Vault all together.

[lbauer]

Code: Select all

I got desperate enough that I even started poking around the Vault SQL Server database directly (but I didn't change anything). 

We don't recommend making changes directly to the database. The "cure" could be worse than the "disease."

Try one more thing: Close any open client on your machine. Delete the client-side cache. Restart IIS.

Is the version still wrong?

If so, we may need to take a look at your database in house to determine how best to fix it.

[lbauer]

If you still see the wrong versions after the steps in my last post, try some operations on the "bad" file and then send me a copy of the sgvault.log file in %windir%\temp\sgvault.

Be sure to include what version of Vault you're on, if it's not clear from the log file. Email it to linda at SourceGear.com.