I am running 3.5.1 with no major issues. I was curious if anyone has run into any nightmare upgrade scenarios...
Windows 2003 Server SP1
SQL Express SP2
Existing Vault 3.5.1 install
Any major upgrade issues with 3.5.2?
Moderator: SourceGear
Difficulties Upgrading Vault 3.5.1 to 3.5.2
I did run into a couple of things upgrading from 3.5.1 to 3.5.2.
When upgrading the client, it went smoothly. I just ran the 3.5.2 install and it upgraded. The server upgraded perfectly as well.
When upgrading the admin tool, I ran the 3.5.2 install. It did not uprade the admin tool. I ran the install again, and it still didn't upgrade. It says it did, but the files were still version 3.5.1. I tried uninstalling the tool. The uninstall ran without error, but did not uninstall the tool. Still 3.5.1. I ran uninstall again. Same result. I deleted the Admin Tool folder. Then the install failed with an exception. I restored the tools folder out of the recycle bin, and ran the install. It failed with a different exception. It couldn't find 998617.msi.) I copied the install file and named it 998617.msi and ran that install. Then it installed and upgraded to 3.5.2.
So, uninstall 3.5.1 Admin Tools BEFORE running the 3.5.2 install.
I experienced a similar thing with the VSS import tool. Uninstall the 3.5.1 VSS import tool before installing 3.5.2.
The order I upgraded may have made a difference. I upgraded the server, then the client, then the admin tool, then the VSS import tool. These are all running one the same (local) machine. I'm running SQL Express SP2, Windows XP SP2, .NET Framework 2.0, VS 2005 SP1.
When upgrading the client, it went smoothly. I just ran the 3.5.2 install and it upgraded. The server upgraded perfectly as well.
When upgrading the admin tool, I ran the 3.5.2 install. It did not uprade the admin tool. I ran the install again, and it still didn't upgrade. It says it did, but the files were still version 3.5.1. I tried uninstalling the tool. The uninstall ran without error, but did not uninstall the tool. Still 3.5.1. I ran uninstall again. Same result. I deleted the Admin Tool folder. Then the install failed with an exception. I restored the tools folder out of the recycle bin, and ran the install. It failed with a different exception. It couldn't find 998617.msi.) I copied the install file and named it 998617.msi and ran that install. Then it installed and upgraded to 3.5.2.
So, uninstall 3.5.1 Admin Tools BEFORE running the 3.5.2 install.
I experienced a similar thing with the VSS import tool. Uninstall the 3.5.1 VSS import tool before installing 3.5.2.
The order I upgraded may have made a difference. I upgraded the server, then the client, then the admin tool, then the VSS import tool. These are all running one the same (local) machine. I'm running SQL Express SP2, Windows XP SP2, .NET Framework 2.0, VS 2005 SP1.
I forgot to say that I now get the error message "A database error has occured (FailDBFault)" in the Vault client whenever I connect to the upgraded database. The list of files will appear, but if I try to diff a file, check it out, get latest, anything, I get the same "A database error has occured (FailDBFault)" error message.
mserfass:
If you are still having problems with your Vault installation, send a copy of the Vault Server log to support at sourcegear.com, ATTN: Linda.
It's in %windir%\temp\sgvault. Also, we'd like to see a copy of the vault_install.log file from your user's temp directory, %temp%.
If you are still having problems with your Vault installation, send a copy of the Vault Server log to support at sourcegear.com, ATTN: Linda.
It's in %windir%\temp\sgvault. Also, we'd like to see a copy of the vault_install.log file from your user's temp directory, %temp%.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager