Checked out file in renegade status

[tScott999]

A file we checked out is showing up as being checked out (correct), but the status is renegade. As per the definition of renegade, this should not be possible. We are currently using version 5.0.3.

We thought the situation could be cured by simply checking out the file and merging any differences. The file still shows the same settings.

We thought the problem could be related to our use of VS 2010; however, the last problem happened when using the Vault merge tool. The file was merged and then committed without complaint from the system.

We only discovered the problem when someone complained our change was not incorporated into our last release (and discovered the files renegade status and being checked out).

Has anybody else been experiencing these problems? Solutions?

Thanks for any help.

[lbauer]

Is this specific to one user on one machine? Or are other users seeing renegade status for checked out files?

There could be a problem with the client-side cache mis-reporting the status. You could try deleting the client-side cache, as it may be out of sync with the database. Close any open clients first.

http://support.sourcegear.com/viewtopic ... 13&t=11513

The Vault client could be confused as to the checkout location of the file. It could be checked out to one machine, and the file modified on a different machine. To see the checkout location in the Vault client, enable the Check out location column in the Vault Client under Tools->Options-> File List Columns.

This inconsistency can also happen if multiple users are using the same working folder.

Another way to get the status to be edited would be to backup the file, do a get latest with "overwrite," check out the file, and replace the working directory copy with the modified version.