Working Folder State Information incompatible

[CraigNicholson]

I'm pulling my hair out with Vault for the last few days. I tried to Get Latest on a tree sub-folder and started getting Null Reference exceptions in the Vault GUI Client. Both client and server are 5.1.1.19215 and the client is running on Windows 7 x64 SP1. Working Folder State Information is set to be stored in the working folder. I've tried renaming the working folder on disk, deleting the repository cache under C:\Users\<username>\AppData\Local\SourceGear\Vault_1\Client and still no joy.

After renaming the entire root working folder I keep getting this error:

The working folder state information for C:\Source\MyFolder\SubFolder\SubSubFolder is incompatible with this version of Vault. Please choose a different working folder path. The specific compatibility exception was: Ticks must be between DateTime.MinValue.Ticks and DateTime.MaxValue.Ticks.
Parameter name: ticks

I've installed the Vault GUI Client on another machine and tested that I can Get Latest of the sub-tree just fine. So it seems to be an issue on one PC only. No errors are logged on the server in the log files either.

I remember having a DateTime.Ticks issue back with the pre .NET Framework 2.0 version of Vault. What could be the problem here?

[lbauer]

Try this slightly different set of steps:

Depending on your OS, find the path

C:\Users\username\AppData\Local\Sourcegear\Vault_1
or
C:\Documents and Settings\<userprofile>\Local Settings\Application Data\SourceGear\Vault_1

and delete or rename the entire Vault_1 folder.

Restart IIS on the Vault Server machine with an "iisreset" command.

Next, set new working folders and perform a Get Latest with Do Not Overwrite/MergeLater to re-establish baselines, rebuild the cache files and reset file status.

[CraigNicholson]

Thanks for the response, unfortunately those steps didn't help. I got the following error repeatedly during the Get Latest of the sub-tree to a completely new set of working folders. Note that the progress went to 100% and now says "Connected".

The working folder state information for C:\Users\<username>\Documents\Source\X\Y\Z is incompatible with this version of Vault. Please choose a different working folder path. The specific compatibility exception was: Could not detect the file type in the supplied stream.

In the Messages tab the following is logged:

An error was found with the baseline file for $/X/Y/Z/Somefile.ext. Refetching baseline and retrying get operation...

I've in the interim also repaired my Vault GUI Client installation and it hasn't helped either.

What concerns me is why this is happening only now. I haven't had issues like this with Vault in the past. Right now I'm unable to work with my source repository and I'm seriously thinking of switching the entire company to git.

[lbauer]

I'd suggest we schedule a remote assist session where I can take a closer look. I'm available today.

Email support at sourcegear.com, Attn: Linda. Please include a link to this forum post and we'll set something up.

[lbauer]

Can you log in with the Vault Client, using a different Vault user account and do the operation that's failing?

[CraigNicholson]

Ok I've tried using a different Vault user on the same computer and it works. What next?

[lbauer]

This seems to point to a caching problem, since the cache is established per user.

A couple of things to try: After you delete your client side cache (the Vault_1 folder), change your options to not store the baselines in the working folder. Create a new, empty working folder with a different name than the previous working folder. Try the get into the empty working folder.

[lbauer]

We dealt with this offline. User's Get is working now, but we will review client and server logs to get more insight into the problem.