Check-In does not remove check-out mark at the client

mariok@robertmondavi.com · Post by **mariok@robertmondavi.com** » Thu Apr 22, 2004 1:33 pm

Hi, (message applies to vault server 1.2.2, client 1.2.3, 1.2.2)

I've had this issue come up a few times and right now where I check-in a file, the server successfully receives the changes fine and it appears that the server releases the lock on the file but the vault client or visual studio still think that the file is checked-out. If i do an undo check-out no changes appear to happen. If I check-in again from the vault client, it does an undo check out with no errors but release of the lock.

In the past I noticed the same issue would manifest whenever I would checkout a file on a machine x but tried to check-in the same file at machine y (same user name). So if I went and checked-in the file at the original machine x then the lock would release. But now I don't have a clue.

Since I'm an admin, I went to the server app and tried to release the lock there but the server does not list that file as checked-out.

Can you help?

I'm attaching the server log

My contact info is
Mario Karagiorgas
707-251-4174
mailto:mariok@robertmondavi.com

Post by **jclausius** » Thu Apr 22, 2004 2:27 pm

if you bring up another instance of vault gui, is the file still checked out?

if not, does the file happen to be a shared file or checked out by multiple people?

Post by **jclausius** » Thu Apr 22, 2004 2:31 pm

in case you're wondering about the shared file / multiple checkouts. a bug of that nature was fixed in vault 2.0.0.

if this is the case, is an upgrade to vault 2.0.2 out of the question? remember, the upgrade to 2.0.x is at no charge. http://support.sourcegear.com/viewtopic.php?t=159

mariok@robertmondavi.com · Post by **mariok@robertmondavi.com** » Thu Apr 22, 2004 2:56 pm

Bringing another instance of the vault client fixed the issue but not in vs ide. In vs ide after I unbound and reconnect the project to source control. It fixed it. So all good. Thanks!

Yeah we want to upgrade to 2.x but we noticed that you have a liberal upgrade policy so we're waiting to see 2.0 mature first a bit since we can only afford to do those once in a while.

Post by **jclausius** » Thu Apr 22, 2004 3:23 pm

if you're at all curious that this checkout list refresh problem is related to the bug fixed in 2.0.0, ( and you have a spare machine to spare

), you could :

make a backup of the database
set up a new machine with msde / sqlserver and iis
restore the backup to the new machine
download and install the latest version of vault server/client

in this enviornment, you should see the problem has been fixed.