I am using Vault 2.0.4 (2190) on both the client and server (Windows Server 2003). I recently upgraded my Windows XP desktop to SP2. We are using Visual Studio 6.0. After upgrading whenever I check something back in using VB 6.0 in Visual Studio those items have a status of renegade in the Vault Client. I reset my working folder to make sure that was correct but the same problem occurs. Also whenever I check something out it prompts me with a Locally Modified File window even though the file matches what is in Vault. I did not change any of my Vault settings after the upgrade to SP2. Our other programmer here upgraded without any problems.
Thanks,
Ray
Upgrade to XP SP2 causing problems
Moderator: SourceGear
You might check whether the file actually has any changes in it after the checkin.
In 2.0, the only way Vault determines the status of a file is by its datatime, so it is likely that the file timestamp was changed after the checkin (perhaps by VB6), and that is why it is reported as Renegade. You might check whether the same problem happens when you checkin from the Vault GUI client.
If this is the problem, my only suggestion I would have it to upgrade to 3.0, which adds the capability to check file status by checksum instead of datetime.
In 2.0, the only way Vault determines the status of a file is by its datatime, so it is likely that the file timestamp was changed after the checkin (perhaps by VB6), and that is why it is reported as Renegade. You might check whether the same problem happens when you checkin from the Vault GUI client.
If this is the problem, my only suggestion I would have it to upgrade to 3.0, which adds the capability to check file status by checksum instead of datetime.