CLI fails checkout

[Don Robinson]

Versions:
Vault Client: 2.0.3 (2174)
CLI Client: ? - whatever shipped with the 2.0.3 client
OS - WinXP Pro
Antivirus - yes, Symantec; disabling does not affect error
Proxy - Winproxy 5.1 - Client configured to NOT use it, not sure about CLI

Problem
I use a Korn Shell script to manage bulk batches of file changes I get from other co-developers. Normally it works just fine, but recently I've had severely degraded performance, and I can't see why. Advice is welcome.

My basic connection to the repository works 19/20 times (which is good enough), using this line (user, password and IP not as shown):

======
ss="E:/Program?Files/SourceGear/Vault?Client/vault.exe "
$ss -user * -password * -host 0.0.0.0 -repository FVS rememberlogin
======

and this output is produced

======
<vault>
<result success="yes" />
</vault>
<vault>
======

So far so good. I've simplified the example here: in my working script I parse the returned text and it fails at that point I get an error and exit.

The core of the problem is with the following example (the working example is buried with variable names, so I've simplified it here). When I give this command to check out a particular file:

======
$ss checkout \$/FVS/base/src/algcmp.for
======

I get this back:

======
<error>
The working folder state information for F:\fvs\ppbase\src is incompatible with this version of Vault. Please choose a different working folder path. The specific compatibility exception was: Wait timout for the mutex exceeded.
</error>
<exception>
System.Exception: The working folder state information for F:\fvs\ppbase\src is incompatible with this version of Vault. Please choose a different working folder path. The specific compatibility exception was: Wait timout for the mutex exceeded.
at VaultClientOperationsLib.ClientInstance.UpdateKnownChanges_File(VaultClientFolder watchedFolder, String diskPath, Boolean notifyChangeSetItemsChanged, WorkingFolder workingFolder)
at VaultClientOperationsLib.ClientInstance.UpdateKnownChanges_RefreshKnown(Boolean doNotify)
at VaultClientOperationsLib.ClientInstance.Refresh(Int64 knownServerRevision, Boolean isRetry, VaultRepositoryDelta delta, Int64 returnedRevision)
at VaultClientOperationsLib.ClientInstance.Refresh()
at VaultCmdLineClient.VaultCmdLineClient.ProcessCommandCheckout(ArrayList strItemArray)
at VaultCmdLineClient.VaultCmdLineClient.ProcessCommand(Args curArg)
at VaultCmdLineClient.VaultCmdLineClient.Main(String[] args)
</exception>
<result success="no" />
</vault>
======

Contrary to this message embedded in the error: "The working folder state information for F:\fvs\ppbase\src is incompatible with this version of Vault. Please choose a different working folder path. The specific compatibility exception was: Wait timout for the mutex exceeded.", the working folder appears to be correct.

Everything works fine working from the Vault Client and from the Dev Studio integration side. I don't get any long delays.

My suspicion is that the CLI connects through the proxy, and that this is the source of the problem. It is a big deal to uninstall the proxy just to test this. So I'd welcome any advice or insights from the SourceGear folks.

Thanks,

[jeremy_sg]

The important bit of text there is "Wait timout for the mutex exceeded". There was a mutex problem that was fixed in version 2.0.5 of Vault. The release notes are at http://support.sourcegear.com/viewtopic ... ight=mutex