4.0.5 beta: upgrade failure

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
oyvind
Posts: 3
Joined: Wed Sep 19, 2007 3:54 am

4.0.5 beta: upgrade failure

Post by oyvind » Wed Oct 17, 2007 7:26 am

First I tried to upgrade, but I might have given wrong login information for sqlserver.

OK
Configuring your new Vault Installation
Checking for IIS Version...Requesting Vault Admin user password...OK
Connecting to the SQL Server...OK
Verifying the SQL Server requirements...OK
Checking for an existing databases...Found.
Asking for database's fate...Keep existing.
Upgrading the existing source control database...
This may take a long time. Do NOT stop this process!
Checking the installed database version...OK
Ensuring that sgvaultuser has access to the Fortress database... Grant database access to sgvaultuser...OK
Upgrading SourceGear master database schema...OK
Upgrading SourceGear source control database schema...OK
Upgrading SourceGear master stored procedures...OK
Upgrading SourceGear source control stored procedures...Database 'sgvault' is already open and can only have one user at a time.
Vault Setup is exiting due to a failure or cancellation. Error Code = -1280


Then I waited a minute or so:


OK
Configuring your new Vault Installation
Checking for IIS Version...Requesting Vault Admin user password...OK
Connecting to the SQL Server...OK
Verifying the SQL Server requirements...OK
Checking for an existing databases...Found.
Asking for database's fate...Keep existing.
Upgrading the existing source control database...
This may take a long time. Do NOT stop this process!
Checking the installed database version...OK
Ensuring that sgvaultuser has access to the Fortress database... Grant database access to sgvaultuser...OK
Upgrading SourceGear master database schema...OK
Upgrading SourceGear source control database schema...OK
Upgrading SourceGear master stored procedures...OK
Upgrading SourceGear source control stored procedures...OK
Database upgrade succeeded!
Checking permissions on local folders...Checking for IIS Version...OK
Adding permissions for temporary asp.net files...
Ok
Updating Configuration...OK

Pre-Website Check...

Entering Website Check...
Looking for websites on this machine...
Looking for websites on this machine...
Prepped IIS Path : IIS://LocalHost/W3SVC. Preparing to do directory entry
Directory Entry succeeded : W3SVC
W3SVC child is AppPools
W3SVC child is Info
W3SVC child is 1
1Added to _websites
Found website - 'Default Web Site'
W3SVC child is Filters
W3SVC child is 1389319358
1389319358Added to _websites
Found website - 'testvault'
W3SVC child is 1184354219
1184354219Added to _websites
Found website - 'testsupport'
W3SVC child is 1420925006
1420925006Added to _websites
Found website - 'testoverview'

Successfully exited Website Check...
You chose to put Fortress on website: 'IIS://LocalHost/W3SVC/1389319358/Root'
Creating the Virtual Directory, VaultService...Already Exists.
Creating the Virtual Directory, VaultShadowFolder...Already Exists.
Updating Vault.Config with Server URL...OK
Updating Shadow Folder Configuration...OK
Creating the Server Home Page...OK
Your Vault Server has been successfully configured.

After pressing [OK] the install will complete and launch a Web browser where you can enter license keys. Please log in with the user name and password that you supplied during this install.
Please press OK to continue installing the Client (if selected).


I installed the solution not at the "Default Web Site", but the installer does not seem to respect this. It removed all the files, but did not replace them with any new - resulting in a blank website.

Anyway I got it to work by pointing the testvault site to the folders for the default web site, but I do not know which version of files I am currently running.

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Post by lbauer » Wed Oct 17, 2007 8:13 am

I'd be a little concerned that things are in a "half-baked" state and may cause problems down the road.

Assuming you have a good backup of your database from prior to the upgrade, I'd suggest uninstalling Vault, restoring a copy of the backup, then reinstalling Vault 4.0.5.
Linda Bauer
SourceGear
Technical Support Manager

Post Reply