Upgrade VaultServer_4_1_0_16216->VaultProServer_7_1_0_32028

[jhildeman]

I am upgrading from VaultServer_4_1_0_16216 to VaultProServer_7_1_0_32028. I will be placing the new Vault Pro v7 on a SQL2008 server and leaving the database on an existing SQL2005 server which seems safe according to your compatibility table found at http://www.sourcegear.com/vault/documen ... chart.html.

My strategy is:
1) Backup sgvault and sgmaster
2) Install VaultProServer_7_1_0_32028.msi on new 2008 web server
3) Point to existing sgvault database on SQL2005 server

Is there anything else I need to know?

Do I need to install major version to major version? i.e. Install 5.1, then 6.1, then 7.1? I am hoping that v7.1 will make all necessary fixes to the database. Is that a safe assumption?

Thanks,
Jim

[Beth]

Because you are a few versions back, you will need to upgrade in steps. Check out our KB article posted here: http://support.sourcegear.com/viewtopic ... 13&t=11648&

[jhildeman]

The conversion was successful. I did 4.x -> 5.1.x -> 6.1.x -> 7.0 to 7.1. I can successfully connect using the Vault client (stand alone). I can see all my repositories. I can checkout, checkin fine as long as it's through the standalone client.

I run visual studio 2012 and "open from source control" (or even opening an existing project with bindings), it prompts for the login, i give the same credentials i did to manual vault client and it comes back with "The server returned an unknown status code (1025)." Any ideas?

[jhildeman]

It looks like Visual Studio just needed to set the default source control client to one of the pro versions.

Steps:
1) Run Visual Studio 2012
2) Tools, Options, Source Control
3) Pick one of the "Vault Pro" clients - not the previous standard one

[Beth]

Thanks for the update. I'm happy to hear you're working.