Checked out and Renegade

[rlepard]

We have an application that is programmatically checking in and checking out files from a Vault 3.1.8 repository using various Vault dlls. We have cases where a particular client PC results in files that are recognized as checked out, but get flagged as Renegade and cannot be checked back in.

Scenario 1:
Login to Vault Client GUI
Check out file (file checked out, status = blank in GUI)
Make edits (file checked out, status = edited in GUI)
Check in file (file checked in, status = blank in GUI)


Scenario 2:
(monitor state information in GUI)
Check out file programmatically (file checked out, status = blank in GUI)
Make edits (file checked out, status = renegade in GUI)
Check in file programmatically --> fails indicating that file needs to be merged



Troubleshooting:
* a different user can login to the problem client PC and different user gets same error
* we've deleted the vault cache on the client pc and still reproduce the error
* appears to happen for every file on the client PC
* we unchecked the "Require Check Out before Check In" setting. In this case, the status is "Needs Merge" in the GUI. If we manually resolve the merge through the GUI, then the status is changed to Edited and the file can be checked in.
* Change computername on the client PC resolves the error. Delete old computername from active directory then change computername back to original name and we do not get an error.
* Rebuilding the client PC resolves the error

What else can we do to troubleshoot the error?

Thanks,
Rob

[Beth]

A needs merge status indicates the the baseline is different since the last check out or update of the baseline. Are there other working on the same files, or even other scripts touching the files?

[rlepard]

Hi Beth -

Thanks for the response. There was no one else working with the same files during this time, other than monitoring the folder/file through the GUI.

Another bit of information that wasn't clear yesterday: Before renaming the PC, the user was low on free disk space and manually deleted some old files, so that may have contributed to the issue / resolution.

On a different PC, a user having the problem ran a standard disk cleanup, cleaning temporary files, temporary internet files, and compressed old files. In the process, the c: drive went from 1.5GB free to 3.5GB free. After the cleanup, we could not duplicate the problem on that PC.

-- Rob

[Beth]

Thanks for the update. If you run into it again, just let me know.