Visual Basic 6.0 SP 6
SourceGear Vault 2.0.6 (2219)
Yesterday I started getting an issue when trying to check things out. I receive a bunch of the following errors:
The working folder state information for D:\Vault\Omni Products\Systems 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
Now for some background. I use to have .Net 2.0 installed on this machine but removed it. I may not have checked anything out since then even though it's been a few days so this may be directly related to that. The only other person who has reported this issue on the forum had 2.0 installed and the advice given to him was to remove it but it's already been fully uninstalled from my machine so I'm not sure what to do now. I also tried to fix one of the projects by deleting the working folder and bringing it back. This seemed to work but today when I opened the file it had lost all binding information.
When trying to open Vault Client to get the version I started getting the same message about another project that I've had checked out for a few days (bad practice I know.. heh) but I know for sure I wasn't getting that error regarding that project yesterday. So it looks like Vault is going to be completely useless to me within the next few days if all my projects start failing.
Any thoughts? I'd rather not have to rebuild my machine...
Vault Exception - Ticks out of range
Moderator: SourceGear
Unfortunately, there's not much you can do if the state files have already been converted to the 2.0 framework. - .Net changed some things with 2.0 that make our cache files incompatible when you go back.
We have actually changed the format of our cache files starting in 3.1 (now in Beta) so that we will no longer have this problem if the framework decides to change things. But that unfortunately won't help you in the short term...
We have actually changed the format of our cache files starting in 3.1 (now in Beta) so that we will no longer have this problem if the framework decides to change things. But that unfortunately won't help you in the short term...