How to Release an Exclusive File Lock?

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
Leo Winters

How to Release an Exclusive File Lock?

Post by Leo Winters » Thu Aug 19, 2004 1:20 pm

I have a .vb file that is checked out in VS.NET 2003, and can't seem to check it back in. When I attempt to do so, the resx file checks in, but the .vb file doesn't change status (e.g. remains checked). I've tried to undo checkout, but this doesn't work, either. I've tried excluding from project and readding, but that doesn't work.

Any suggestions?

Thanks in advance!

dan
Posts: 2448
Joined: Wed Dec 17, 2003 5:03 pm
Location: SourceGear
Contact:

Post by dan » Thu Aug 19, 2004 2:07 pm

Try it from the Vault GUI client and see whether it is checked out. If it is, check it in from there.

Leo Winters

Post by Leo Winters » Thu Aug 19, 2004 2:47 pm

I actually did try that, but the "Check In" option is grayed out in the standalone Vault client. Only the integrated VS.NET 2k3 vault gui has the option to Check In, but when I try to check in from there, it remains checked out.

Could I just update tables in the DB to update status of the file to checked in? It shows up as Checked out both on this machine and any other that connects to the Vault Server...

Thanks in advance for any assistance you can provide! =)

Leo Winters

Post by Leo Winters » Thu Aug 19, 2004 2:49 pm

... Also, if I try checking out in the standalone client (with the intent to try to check it back in from there), I get the following error:

Check out failed for $/Services/ServicesMonitor/ServicesMonitor.vb: The file has been exclusively locked.

dan
Posts: 2448
Joined: Wed Dec 17, 2003 5:03 pm
Location: SourceGear
Contact:

Post by dan » Thu Aug 19, 2004 3:17 pm

You can always undo the checkout from the Admin Tool, but it is a mystery why only the IDE client would allow checkin. If you do a properties on the file from the standalone client, it will show you where the file is checked out to - see if the file really does exist there.

Leo Winters

Post by Leo Winters » Thu Aug 19, 2004 3:29 pm

Yes, the file did exist, and both the standalone and VS.NET 2k3 client were pointing to the same location... weird, eh?

No matter... the Undo Check Out worked like a charm!

Thanks for your help!! =)

dan
Posts: 2448
Joined: Wed Dec 17, 2003 5:03 pm
Location: SourceGear
Contact:

Post by dan » Thu Aug 19, 2004 3:35 pm

One last parting comment: If the status of the file was Unknown, that might explain it - you can't check in a file until the Unknown status is resolved.

Post Reply