Major issues with Vault 4.0.x VS2005 clients

isg · Post by **isg** » Fri Aug 31, 2007 3:18 am

Hi.

I am having major issues with the Vault 4.0.x VS2005 clients! Sometimes when working in parallel and two developers works on the same file changes are lost! This happens when developer one checks in the file, and deveveloper two gets latest, then the changes from developer two is not merged into developer twos file!

This has happened more than once and makes the VS2005 client COMPLETELY USELESS. Unless this error is fixed very soon we will probably be looking at alternatives to vault with a better track record!

Beth · Post by **Beth** » Fri Aug 31, 2007 7:38 am

Can you have your user look in their _sgbak folder for the previous version? If a file is overwritten, a copy is placed there. To find the location of that folder, go to the Vault GUI Tools - Options - Local Files - Backup. The path is noted there.

I will try to reproduce that here.

ian_sg · Post by **ian_sg** » Fri Aug 31, 2007 8:20 am

isg,

I've been unable to reproduce your problem. Can you provide more information? On what types of files are you seeing this? What project type? What version of Vault?

One possibility, in the scenario you describe, is that the changes could not be automatically merged when developer two did the Get Latest. This would happen if you'd both made changes to the same line, for example. In this case, developer two's file is left untouched, and the file enters a "needs merge" state. In the solution explorer this state is indicated by a blue flag with toot tip text "The file needs to be merged." In the pending changes window the file is shown in red and the details column says "Needs Merge." From either window, developer two can now select "Show Merge" to manually perform the merge.

isg · Post by **isg** » Fri Aug 31, 2007 8:38 am

Well i have the previous versions of the file in vault, but somehow the changes one developer commited was later lost. I am 100% sure that there has been no merge conflict as there was no changes in the same lines. Also we have never had any issues like this in version 3.x but now we have seen 2 issues in a week in version 4.0.4! Its very unfortunate as ve cannot trust any commits!

I will look into reproducing the error ASAP!

Post by **jclausius** » Fri Aug 31, 2007 9:26 am

That is strange you are having problems here. It is surprising you would be having issues as the normal GET routine heavily was heavily tested.

A couple of different things to check:

1) Is the working folder in the place where you expect it to be located? You can verify this with the Vault GUI client. Sometimes a working folder can accidentally get re-mapped, and users changes are located in a different spot then where they think the file is at.

2) Is it possible the "Overwrite" option is on during a GET. Verify the command dialogs for GET is enabled, and that the Automatic Merge option is used during the GET. You can also hold down the Shift key while invoking GET to see the GET's options.

3) Was the file located in _sgbak in the working folder? By default Vault will not overwrite any file, but rather make a backup copy in _sgbak. If the file is located there, then the GET was invoked with "Overwrite" as that code path does make a copy in case of accidental overwrites.

Something routine as GET should not be causing any problems. If you are able to recreate this, please notify us ASAP.

Thanks.

Beth · Post by **Beth** » Fri Aug 31, 2007 9:42 am

I also forgot to mention there is a new feature where you can go to the properties of the file in Vault and there will be a backup tab where you can restore an overwritten version of that file.