Invalid object version for some files in repository

[sgclark]

Hello,
Background: We're upgrading from Vault 5.0.x to Vault 6.0 and changing to new server box running Win Server 2008 R2. Last week, the Vault 6.0 server software was installed on the new server and a SQL backup from the 5.0.x box was restored to the new server and upgraded to Vault 6.0.

Today, I installed the Vault 6.0 client on our continuous integration box (running Cruise Control.NET) to test with before the new server box goes live. I can connect through the GUI client fine. However, when I run our CI scripts, the vault GetVersion command, used by CC.NET to get the latest version of our source code, fails and Invalid Object Version errors are reported for a dozen or more files in the repository. When I look at the properties of these file with the GUI Client, I get the same error. There doesn't seem to be a pattern to what files are failing, they're scattered in several places throughout the code base. Our CI box that is still using the Vault 5.0.x system does not report these errors.

Can you shed any light on this situation for me and give me some things to try to fix this? We're planning on the new server going live later this week so need to get this resolved soon.

Thanks,
Steve

[Beth]

Which version of CC.NET are you using?

[sgclark]

We're using CC.NET Ver. 1.6.7981.

[sgclark]

And I forgot to mention the CI box is running XP Pro SP3.

[Beth]

Last week, the Vault 6.0 server software was installed on the new server and a SQL backup from the 5.0.x box was restored to the new server and upgraded to Vault 6.0.

I'm a little confused about the order of the steps you performed. The SQL database has to be in place before the Vault 6.0 installer is ran. Is that how the upgrade was performed, or did you install Vault first and then restore the database?

[sgclark]

You're right, that wasn't very clear. Yes, the database was in place before 6.0 was installed. Last Friday, you walked a co-worker of mine through the process (after he messed up on the first attempt).

I'm wondering if this might be a local caching issue. Would it hurt anything to remove the local cache files?

[Beth]

It shouldn't hurt to remove them, but to be on the safe side, just rename the top level folder that holds the cache instead. Vault will create a new one. Then if we need anything from the old one it can be retrieved.

Also, were you on CC.NET 1.6 prior to the upgrade?

[sgclark]

Also, were you on CC.NET 1.6 prior to the upgrade?

Yes

[Beth]

Since you get the same errors with the GUI client, could you try renaming or removing a cache for a Vault GUI client, set the working folder again, or set a new working folder, and see if you can get files, check them out, edit them and so on?

[sgclark]

Things seem to be working now. Removing the _sgvault cache folder didn't help, but removing the ChacheMember files got things working again.

One final question: when installing the 6.0 client software on our developer PCs, is it necessary or advisable to uninstall the old client software first?

Thanks.

[Beth]

You shouldn't need to uninstall the previous client. The installer should take care of that.