Exclusive Checkout (two times on same file)

[Busboy]

Hi,
We are using exclusive checkout on our databases, but sometimes the Vault server is making mistakes and allow the same user to checkout the same file twice. See attached screendump.

How can I avoid this?

[jclausius]

This has been fixed in the upcoming Vault 4.0.5 release.

[mbainbridge]

Seems to have been broken in 4.0.6 (or at least in Fortress 1.0.6)

We're seeing a lot of these double-checkouts; one developer had to clear the cache 24 times in a day because recently-updated files were being affected.

This seems to work every time:

Developer A has a file checked out. If they undo the checkout, then check the file out again immediately, developer B will now see that file being checked out twice, even though the server is set for exclusive checkouts. Now multiply this by 20 developers, and you have chaos :-/

Using the web admin client (Undo checkout) shows that the file is only checked out once. The only way to clear this error in the Fortress client is to clear the cache. We've tried the 1.0.6 client and the 1.1b2 client with the same results.

Will check on Monday what happens when we try this on the 1.1b2 test server, and also when IIS has been restarted on the main server.

[jclausius]

mbainbridge,

For the sake of completeness, you mention the Fortress client, but what is the version of the Fortress Server you are using?

If you could provide the info from Help->Technical Support that would give us a listing of everything involved.

[mbainbridge]

Hi Jeff,

(Wasn't sure whether to move this to the Fortress forum or not...)

Both client and server are 1.0.6, although I've installed the 1.1b2 client to see if that made any difference (it didn't). Tech support info below.

The problem appears to be when a file has been checked out by a user on one machine and unchecked out on a different machine by the same user. Unfortunately, as we've all recently got new PCs, we have a large number of files checked out on machines that no longer exist.

This should hopefully be reproducible:

1) On one machine, check out a file as user A.

2) On a different PC, start Fortress clients as user A and user B. As user A, undo the checkout. The client appears to perform the operation, but still shows the file checked out. (The server has actually performed the operation, as the web client doesn't show it in the list for Undo-checkout). Refresh user B and it will also still be shown as checked out.

3) As user B, check out the file. It will now show a double-exclusive-checkout as user A and user B.

If the caches are reset on both machines, the correct file status is then shown. At 45 seconds a time, this is rather nauseating after a while (especially 24 times a day).

We have reproduced this on Fortress 1.0.6 (server and client) and also on a test server running Fortress 1.1b2 (server and client).

Hope this makes sense
--
Marcus

Client Information
Fortress Client Version: 1.1.0.16096
.Net Framework Version: 2.0.50727.832
Operating System: Microsoft Windows XP Professional
Service Pack: 2.0
OS Version: 5.1.2600
Total Physical Memory: 2 GB
Time Zone: (GMT) Greenwich Mean Time : Dublin, Edinburgh, Lisbon, London

Server Information
Fortress Server Version: 1.0.6.15954
.Net Framework Version: 2.0.50727.832
Operating System: Microsoft(R) Windows(R) Server 2003, Standard Edition
Service Pack: 2.0
OS Version: 5.2.3790
Timezone: (GMT) Greenwich Mean Time : Dublin, Edinburgh, Lisbon, London
SQL Version: Microsoft SQL Server 2005 - 9.00.3054.00 (Intel X86)
Mar 23 2007 16:28:52
Copyright (c) 1988-2005 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2)

License Information
2 serial number(s):
1 of 2: 25 full users, permanent
2 of 2: 25 full users, permanent

[jclausius]

Many thanks for the info. We'll test this scenario to see if we can get to the bottom of things.

Thanks again.