Upgrading version 4 from 3 does not remember Cache/baseline

boy141 · Post by **boy141** » Mon Jan 14, 2008 5:45 pm

Hi Guys & Mods,

I upgraded one of our developer's machine to the current 4.XX version from version 3. I was checking a few of his settings and noticed that the limit baseline files is not default/ticked to 3 (it was previously ticked and option turned on). Is there a way Vault could keep that option ticked by default for upgrading installation? I believe (90%) we had the option turned on.

Thanks!

lbauer · Post by **lbauer** » Wed Jan 16, 2008 9:51 am

Some client options are stored in the database but others are stored client-side. It's possible the client upgrade overwrote the local configuration.

I will log feature request to preserve client-side settings.

Beth · Post by **Beth** » Wed Jan 16, 2008 10:01 am

Can you also tell me where you set the baseline limit before upgrading? In the client options for Vault 3.5.3, there wasn't the option to limit baselines (see pic below).

Or is it possible that the user upgraded to an early version of 4.x and then did an upgrade between versions of 4.x and the settings got lost there?

I just need more details in order for this to be reproduced.

boy141 · Post by **boy141** » Thu Jan 17, 2008 1:52 pm

Hey Beth,

Yes, we updated from 3.5 to VaultClient_4_0_5_15922. Then we set the baseline to 3. A week later, we updated to VaultServer_4_0_6_15954.msi
and the baseline was changed.

Also, on the serverside, we configured a few things in web.config such as treestructure and memory and when we did the upgrade, the values changed.