Vault 5.1.2 Client giving random Pending Change Set results
Moderator: SourceGear
Vault 5.1.2 Client giving random Pending Change Set results
Hello: We are using Vault Standard Server, version 5.1.2 (19281) - both client and server. We have 3 developers using Vault. We are using the Edit-Merge-Commit style of source control. We all set our working folder(s) to the same place on a mapped drive. One of the developers gets random amounts of Pending Change Set results all the time - even when there should be no pending change sets. Using Get Latest Version does not resolve this. Committing all the reported pending changes sets does not resolve this. I have uninstalled and reinstalled the client several times - that does not resolve this. Other developers are not having this problem. Any help getting this corrected would be very much appreciated!
Re: Vault 5.1.2 Client giving random Pending Change Set resu
Vault status codes don't deal with users all having the same working folder. Every user has their own cache. When users share working folders, when one user makes a change, another user's cache sees that as a change.
Here's a few things the user can try to resolve this. Try one and then check the results before moving onto the next one.
1) Perform a Get Latest with the option to Overwrite checked. When Automatic Merge is used, Vault assumes that any changes remain.
2) Have the user turn on the option to detect changes using CRCs. That option is found in the Vault Tools - Options - Local Files.
3) Have the user rename their Client-side cache. Details on how to do that are in this KB article: http://support.sourcegear.com/viewtopic ... 13&t=11513
Here's a few things the user can try to resolve this. Try one and then check the results before moving onto the next one.
1) Perform a Get Latest with the option to Overwrite checked. When Automatic Merge is used, Vault assumes that any changes remain.
2) Have the user turn on the option to detect changes using CRCs. That option is found in the Vault Tools - Options - Local Files.
3) Have the user rename their Client-side cache. Details on how to do that are in this KB article: http://support.sourcegear.com/viewtopic ... 13&t=11513
Beth Kieler
SourceGear Technical Support
SourceGear Technical Support
Re: Vault 5.1.2 Client giving random Pending Change Set resu
Thank you! Option 1 was not really an option for us. Option 2 did not resolve this. Option 3 appears to have fixed this problem. Apparently my cache had somehow become corrupted. Again, thanks!
Re: Vault 5.1.2 Client giving random Pending Change Set resu
Thanks for the update. I'm happy to hear you are working again.
Beth Kieler
SourceGear Technical Support
SourceGear Technical Support