Serious Issues with Vault

[CareBear]

Hello!

We've had various issues with Source Gear Vault since we started using it. We started on version 2.0.3 I think and have upgraded each upgrade up until 2.0.6

We have two 10 users licensenses.

The problems we're having are the following:

1. When checking in files in Visual Studio 2003, Visual Studio doesn't recognize the files as checked in. They appear checked out, but in reality they are checked in when validating with Vault Client. It doesn't help closing the solution, but have to restart whole Visual Studio.

2. Changes are being overwritten. Multiple times have people lost their changes, and there have been occasions where people have done multiple check in and check out during a week, but after we've discovered that something was wrong, the history of the file does not show the supposedly checkin/checkouts.

3. Getting latest often doesn't return all new files, and has caused problems for many of us, and especially on the database type projects.

4. Often when things have become revert to old code, we can find the changes in the backup folder "_sgbak". Without this folder we would have lost a lot of work.


Some more details:
We have different Visual Studio solutions but the primary does now contain 35 projects. These are of type class library, Windows Service, Windows application. There are no web projects, as we use class library instead.

With 35 projects in the same solution, it's very time consuming having to restart Visual Studio when files are not visibly checkedin, as each restart require a complete rebuild of all the projects.

Issue 1. has increased a lot after we setup Cruise Control .NET together with NAnt, etc.


Does anyone have suggestions or links to Knowledge Bases, guidelines, etc. to guide me to a solution for these problems? We have considered upgrading to Version 3.0, but if we can't fix these issues on 2.0.6 how will we know that paying for 3.0 upgrade will help or not?

The reason for delaying these questions is cause we had a release deadline which we have now completed, and there is dedicated some time to address these issues. If we can't fix it, we might have to look for alternative solutions.


Regards,
Sondre

[dan]

This will be very hard to track down over the support forum. Send me email with the link below - I think the first thing to do is to set up some logging classes with the IDE DLL to see what it thinks is happening.

[bpd]

My team of 10 developers using 2.0.6 are reporting many similar issues to these.

An incident that has occured multiple times seems to be related to the infamous FileStatus of *Missing* or *Renegade* where Vault has overwrittern the newer local file with the one from the repository because a CheckIn must have failed or something and mustve never got the newer file ?

I have seen a developer complete a GetLatest of a project and without making any changes has looked at that same project in the SV IDE a few days later and many of the files show as *Missing* even though the files exist in his local working folder ?

We always find our missing code as a backup file in the _sgbak folder

Was there a resolution to your issues ?

[dan]

These symptoms don't make a lot of sense - Vault would only delete files on the local disk if a file had been deleted in Vault (and if your option is set to do that).

If the files are showing up as missing in Vault, it might be that Visual Studio switched working folders on you (which it will sometimes annoyingly do).

This may be a long shot, but are you using web projects? We've noticed that if you choose the same Vault folder for both the project files and the web service files, it actually stores these files on two different folders on the local disk, and then attempts to switch working folders when it needs one or the other, and often gets confused on things like Get Latest.

If that doesn't apply, I would suggest turning on client logging - see http://support.sourcegear.com/viewtopic.php?t=2146

The IDE logging in 2.0.x was not very good for the IDE. We are releasing 3.0.2 today or monday, which would allow us much better insight to what the IDE is doing. Let me know if you are in a position to upgrade...

[dan]

Another thought on this: Often when files are not retrieved in a Get Latest, it is because another version was created on the server, and the user is set to not automatically merge the file, or the automatic merge failed due to conflicts.

Can you all verify wasn't the case when the Get Latests didn't get the most recent versions of files?