Vault acting strange

[dmurty]

Hi,

We are using vault 4.0.6.15954 and have been for some time now. All of a sudden we are experiencing some strange errors. Some machines are showing files as beeing checked out, when we go to the machine and user that vault says it is check out to, vault says that the file is not checked out. The only way to clear this is to check the file out and then undo the check out from the admin tool. On our build machine the build script can checkout and checkin but then fails to check out on a particular set of files. following is the output from the build script:
"C:\Program Files\SourceGear\Vault Client\vault.exe" -host csserver2.2synergy.local -user <OUR USER> -password <OUR PASSWORD> -repository "HealthCare Assistant" checkout "$/1 - Current Development/Installation/Database/Demo/Demo.db" "$/1 - Current Development/Installation/Database/Demo/Demo.log" "$/1 - Current Development/Installation/Database/Demo/Demo.mlg" -setfiletime modification -exclusive <vault>
<error>
<exception>System.Exception: Wait timeout for mutex after 30000 milliseconds.
at VaultLib.SystemMutex.Take(UInt32 ms)
at VaultClientOperationsLib.CacheMember_LastStructureGetTime..ctor(String folder)
at VaultClientOperationsLib.TreeCache.Load()
at VaultClientOperationsLib.TreeCache..ctor(Int32 repID, String username, String uniqueRepositoryID, String localStoreBasePath, ClientInstance ci)
at VaultClientOperationsLib.ClientInstance.SetActiveRepositoryID(Int32 id, String username, String uniqueRepositoryID, Boolean doRefresh, Boolean updateKnownChangesAll)
at VaultClientIntegrationLib.ServerOperations.SetRepository(VaultRepositoryInfo repositoryInfo)
at VaultClientIntegrationLib.ServerOperations.SetRepository(String repositoryName)
at VaultClientIntegrationLib.ServerOperations.Login(AccessLevelType altCommand, Boolean bAllowAuto, Boolean bSaveSession)
at VaultClientIntegrationLib.ServerOperations.Login()
at VaultCmdLineClient.VaultCmdLineClient.ProcessCommand(Args curArg)
at VaultCmdLineClient.VaultCmdLineClient.Main(String[] args)</exception>
</error>
<result>
<success>False</success>
</result>
</vault>
Process completed with exit code -1

On another developer's machine, vault shows the files as checked out and edited but when they try to check in vault does not check the files in and produces the following error message:
[2/2/2009 4:50:41 PM] Preparing data to begin transaction
[2/2/2009 4:50:42 PM] Beginning transaction
[2/2/2009 4:50:42 PM] An error occurred while trying to begin a transaction.
[2/2/2009 4:50:42 PM] Transaction failed
[2/2/2009 4:50:42 PM] An exception was encountered during the transaction. Exception: Server was unable to process request. ---> Error in the application. at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at VaultClientNetLib.ClientService.VaultService.BeginTx(Int32 nRepID, String strComment, VaultRequestItem[]& requests, String& strTxID)
at VaultClientNetLib.VaultConnection.BeginTx(Int32 nRepID, VaultRequestItem[]& requests, String& strTxID, String comment)
at VaultClientOperationsLib.ClientInstance.Commit(ChangeSetItemColl givenItems, String strChangeSetComment, Boolean keepCheckedOut, Boolean removeLocalCopy, CommitType committype, VaultDateTime dateImport, Int32 nUserIDImport, Int64& nRevID, Int32[]& retBegEndTx)

Any suggestions or advice will be greatly appreciated,

Damien

[Beth]

When you are checking the other client or the original client that you see the check-out from, are you performing a refresh so that it checks for new information?

What usually fixes most odd behaviors is to upgrade to the latest version. From Vault 4.0.6 to 4.1.4, it will be a free upgrade. You will want to read the Vault 4.1.4 Release Notes before you start though, and always make sure you have a current backup before upgrading.

You could have your users rename their CacheMember_CheckOutList to force Vault to pull a new one, but you are likely to continue having the problem if you don't upgrade.