4.1.2 upgrade fails from 4.1.1

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

Moderator: SourceGear

Post Reply
kadorken
Posts: 77
Joined: Mon Feb 16, 2004 8:38 am
Contact:

4.1.2 upgrade fails from 4.1.1

Post by kadorken » Tue Jul 29, 2008 7:08 am

Trying to update to 4.1.2, the first installation failed with (from the installer log)
Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action CustomActionExe.exe, location: C:\inetpub\wwwroot\VaultService\bin\CustomActionExe.exe, command: /TARGETDIR="C:\inetpub\wwwroot\VaultService\ " /TARGETDIR2="C:\inetpub\wwwroot\Fortress\ " /PARAMS= /DROPDB= /UPGRADE={36C60A14-7323-450D-BF8A-EF3FA8813D12} /ADMINPW= /SQLSERVER="" /WINAUTH=1
=== Logging stopped: May 2008 8:37:44 ===

Subsequent attempts to reinstall get:
Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action CustomActionExe.exe, location: C:\inetpub\wwwroot\VaultService\bin\CustomActionExe.exe, command: /TARGETDIR="C:\inetpub\wwwroot\VaultService\ " /TARGETDIR2="C:\inetpub\wwwroot\Fortress\ " /PARAMS= /DROPDB= /UPGRADE= /ADMINPW= /SQLSERVER="" /WINAUTH=1
=== Logging stopped: May 2008 8:39:42 ===
and the messages
Looking for IIS Version
Configuring your new Vault Installation
Requesting the IIS Process User...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
Grant database access to NT AUTHORITY\NETWORK SERVICE...OK
Upgrading SourceGear master database schema...OK
Upgrading SourceGear source control database schema...OK
Waiting for upgrade connection to sgvault database to be released...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

Furthermore, if I connect to the SQL server with SQL Mgmt Studio, the list of databases listed shows 'sgvault' to be in (Single User) mode.

Stopping and restarting the SQL server didn't fix it;
Stopping and restarting the Vault web server didn't fix it.

And now I cannot access the vault database at all.

Suggestions?

kadorken
Posts: 77
Joined: Mon Feb 16, 2004 8:38 am
Contact:

Re: 4.1.2 upgrade fails from 4.1.1

Post by kadorken » Tue Jul 29, 2008 7:33 am

Wow, that was scary. I have no idea what corrected the problem. Persistence pays off I guess. I stopped the SQL Server Agent (because something I read warned about doing this if using the SQL server in single user mode, but I'm not sure that 'single user' mode the article was referring to was the same as the '(Single User)' status of the one 'sgvault' database shown in SQL mgmt studio).

However, at some point, the 'sgvault' database went back to 'normal'; the upgrade proceeded and the vaultserver started as before.

Of course, this attempt was the first time in 5 years of upgrading vault that I tried to do an upgrade without first making a backup first; never again!

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

Re: 4.1.2 upgrade fails from 4.1.1

Post by lbauer » Tue Jul 29, 2008 7:57 am

Of course, this attempt was the first time in 5 years of upgrading vault that I tried to do an upgrade without first making a backup first; never again!
Yikes! We have three rules when making any change to the Vault database: Backup, backup, backup.

Not to unduly alarm you, but installing over a failed installation without restoring a backup of the database could lead to database inconsistencies down the road. There's really no way to check the database.

However, be sure to backup regularly, and if you need support later, be sure to let us know what happened to the initial update attempt.
Linda Bauer
SourceGear
Technical Support Manager

Post Reply