Incompatibale Version

jnapier · Post by **jnapier** » Mon Feb 14, 2005 11:12 am

I recieved an error that looks like one of the users may have installed the 3.0 client version while the server is 2.06. The error I am recieving is listed below. I can not figure out how to fix the this problem.

Hopefully someone can provide some insight, thank you.

The working folder state information for D:\Solutions\WebSolutions\NGSolutions\BOLSolution\Website\admin\archive\march_2004\sip_spd is incompatible with this version of Vault. Please choose a different working folder path. The specific compatibility exception was: Wait for the mutex was abandoned. System.Exception: The working folder state information for D:\Solutions\WebSolutions\NGSolutions\BOLSolution\Website\admin\archive\march_2004\sip_spd is incompatible with this version of Vault. Please choose a different working folder path. The specific compatibility exception was: Wait for the mutex was abandoned. 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.ProcessCommandGet(ArrayList strItemArray) at VaultCmdLineClient.VaultCmdLineClient.ProcessCommand(Args curArg) at VaultCmdLineClient.VaultCmdLineClient.Main(String[] args)

dan · Post by **dan** » Mon Feb 14, 2005 11:40 am

If you upgrade the client to 3.0 without upgrading the server, then yes, the client cache files would be incompatible when trying to revert back to the 2.0 client.

The only way to fix this is to delete the cache files and let the client reconstruct them. See http://support.sourcegear.com/viewtopic.php?t=6 for an explanation of the client side cache files and how to remove them.

jnapier · Post by **jnapier** » Tue Feb 15, 2005 10:17 am

I cleaned out the cache as suggested and insured that no users had the 3.0 client installed. The problem was resolved yesterday and has now returned this morning. The warning message is pointing to a different folder than it was yesterday.

I must point out this this is through the command line and I have no problems uing the Gui. We are using the command line for our build process. It almost seems like something has become corrupted.

What now?

dan · Post by **dan** » Tue Feb 15, 2005 10:25 am

Is it happening on the exact same folder/repository?

At what point are you getting this message? (What is the CLC attempting to do when it happens)?

jnapier · Post by **jnapier** » Tue Feb 15, 2005 10:42 am

The CLC is attempting to get the latest version when this occurs.

It is happening in the same repository, and it appears to be the same folder. But like I said, it was failing on a different folder yesterday before I cleaned out the cache, now its another folder.

The weird thing is that I have several nightly builds and only one of them has any direct contact with the folder that is causing the problem. All of the builds get the same error referencing the same folder when they try to perform a GET. And the weird thing is that they are not even trying to get anything from that folder. So any GET fails immediatly when connecting to the repository. Thats as far as the builds get before failure so I can't tell you if any other operations will exhibit the same behavior.

sterwill · Post by **sterwill** » Tue Feb 15, 2005 11:22 am

The error message the client is printing could be more helpful. The actual problem is the part at the very end (wait for the mutex was abandoned). Vault 2 had problems with its use of Windows sytem mutexes. Sometimes they were not disposed of properly before the garbage collection process occured, and this caused the error you're having. Your state files are just fine, our default error message needs some tuning.

Vault 3 uses a different system mutex implementation, which doesn't have the abandonment problems.

jnapier · Post by **jnapier** » Tue Feb 15, 2005 11:27 am

So are you asking me for more information - I've given you everything. The error message I listed is all I have recieved.

Or are you telling me to upgrade to 3.0? I wish I could but our budget isn't letting us right now.

Everything has been running fine for the last year and now all of a sudden this is happening nightly. Why all of a sudden? What could have occurred?

dan · Post by **dan** » Tue Feb 15, 2005 1:52 pm

Perhaps something changed just enough in the tree to trip this. Contact me by email (using the button below) and we can talk about possible solutions.

jnapier · Post by **jnapier** » Mon Feb 21, 2005 1:17 pm

Cleaned the cache again and it has been working for the last couple of days. I'll get back to you if the problem pops up again.

Thanks.