problem upgrading from v2.0.2

epis_itmanager · Post by **epis_itmanager** » Fri Jan 13, 2006 10:54 am

I ran into some problems when upgrading from v2.0.2 to v3.0.7. The install gets nearly to the end and then gives the following error:

Unknown error (0x800cc810) Vault Setup is exiting due to a failure or cancellation. Error Code = -1280

I've done some searching on error code 1280 and didn't find anything that looked relevant to my situation. Any ideas how I can proceed?

lbauer · Post by **lbauer** » Fri Jan 13, 2006 11:04 am

At what point does the installer fail -- what does the installer screen say just before the error?

The install process generates a log file called vault_install.log, which should be in your user's temp directory (%temp%). Are there any errors reported in the install log?

epis_itmanager · Post by **epis_itmanager** » Fri Jan 13, 2006 11:14 am

Thanks for the reply. I should clarify a bit. I actually tried installing vault server version 3.1.6 after the 3.0.7 install failed. That probably wasn't a very good idea. Here is what showed up just before the install of version 3.1.6 failed:

OK
Upgrading your Vault configuration.
Checking for IIS Version...Connecting to the SQL Server...OK
Verifying the SQL Server requirements...OK
Requesting Vault Admin user password...OK
Upgrading the existing Vault database...
This may take a long time. Do NOT stop this process!
Checking the installed database version...OK
Upgrading SourceGear Vault database schema...OK
Upgrading SourceGear Vault stored procedures...OK
Database upgrade succeeded!
Checking permissions on local folders...Checking for IIS Version...OK
Adding permissions for temporary asp.net files...
Ok
Looking for websites on this machine...
Looking for websites on this machine...
Unknown error (0x800cc810)
Vault Upgrade Setup is exiting due to a failure or cancellation. Error Code = -1001
Please press OK to continue installing the Client and Admin Tools (if selected).

Then when I click "ok" the installer package gives error 1722. Here is what the install log reports:

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 SetupAction, location: C:\Inetpub\wwwroot\VaultService\bin\CustomActionExe.exe, command: /TARGETDIR="C:\Inetpub\wwwroot\VaultService\ " /TARGETDIR2="C:\Inetpub\wwwroot\VaultService\VaultShadowFolder\ " /CUSTOMNAME="" /CUSTOMPW="" /PARAMS= /DROPDB= /UPGRADE={B5566019-7EA6-4608-B65A-4A5918771B97};{B5566019-7EA6-4608-B65A-4A5918771B97};{B5566019-7EA6-4608-B65A-4A5918771B97};{B5566019-7EA6-4608-B65A-4A5918771B97};{B5566019-7EA6-4608-B65A-4A5918771B97};{B5566019-7EA6-4608-B65A-4A5918771B97} /ADMINPW= /SQLLOGIN= /SQLPW= /WINAUTH= /SQLSERVER="" /IISPROCESS=0
=== Logging stopped: 1/13/2006 9:12:50 ===

lbauer · Post by **lbauer** » Fri Jan 13, 2006 12:17 pm

I actually tried installing vault server version 3.1.6 after the 3.0.7 install failed.

It's hard to say what state your database or the rest of the installation is in.

I'd suggest starting over. Do you have copy of your Vault 2.x database? You'll want to make another copy before you install again, so you still have a backup. If you *don't* have a backup, contact me at linda at sourcegear.com and we'll try something else.

Suggested steps if you do have a backup of the 2.x database:

Uninstall the Vault Server, and, when prompted, don't keep the (partially?) updated database. Restore a copy of your 2.x database to MS SQL Server, and make a backup.

Then run the Vault 3.1.6 installer. It should detect your database and upgrade it.

If you do encounter an error, note when in the installation this occurred. Email a copy of the new install log to linda at SourceGear.com and we'll go from there.

epis_itmanager · Post by **epis_itmanager** » Fri Jan 13, 2006 12:39 pm

I did a full backup of my 2.x database before I started. We're using MSDE by the way. Before I try to uninstall and start over, should I create another copy in addition to the pre-upgrade backup? If so, what is the recommended process for doing that with MSDE?

lbauer · Post by **lbauer** » Fri Jan 13, 2006 2:30 pm

Just the pre-upgrade backup should be enough, as long as you always have one good backup.

I've consulted with some of my colleagues, and before we start over, I'd like you to try running the 3.1.6 installer again. It's possible that the database was properly upgraded even though the installer is failing.

New steps:

Uninstall Vault 3.1.6, and KEEP the database when prompted. Then run the 3.1.6 installer again. If it fails, I'd like to see the entire vault_install.log. Email it to Linda at sourcegear.com.

epis_itmanager · Post by **epis_itmanager** » Fri Jan 13, 2006 3:07 pm

Sounds good. I figured out how to do another backup from our SQL Server (unfortunately we don't have a dba around). There was an option in Enterprise Manager that let me backup sgvault, so I think we have at least two good backups to work with.

I'll do as you instruct this time...uninstall Vault 3.1.6, and KEEP the database when prompted, then run the 3.1.6 installer again.

If I run into any problems, I'll email you the entire vault_install.log. Acutally, the install log files I found in the user temp directory were not called "vault_install.log," They had cryptic names like 'MSI38db7.LOG" and "MSIcdda.LOG." Was I looking at the wrong log files? They looked like they contained vault install information.

lbauer · Post by **lbauer** » Fri Jan 13, 2006 3:21 pm

They had cryptic names like 'MSI38db7.LOG" and "MSIcdda.LOG."

These are probably being generated by MSI, not by our logging code. After reinstall, search for "vault_install.log." If it wasn't created, send the MSI*.log file, if it has the same date/time as your recent installation. There may still be useful information in it.

epis_itmanager · Post by **epis_itmanager** » Fri Jan 13, 2006 3:29 pm

Thanks Linda. I tried the reinstall and it failed again. I found the correct log file this time. I just emailed it over to you.

lbauer · Post by **lbauer** » Mon Jan 16, 2006 8:51 am

I've responded to your email. There seems to be a problem updating the website.