Error 1721 while upgrading

[spatialminds]

I have an existing installation of Vault version 3.0.2 that I am trying to upgrade to Vault version 4.1.2. I verified that all of the preconditions for this version of Vault are met. While installing I receive 2 identical error messages and the install/upgrade fails. The Error message reads, "Error 1721: There is a problem with this windows installer package. A program required for this install to complete could not be run. Contact your support personnel or package vendor. "

Server OS: Windows Server 2003 (Small Business Server) SP2

Suggestions on how I can remedy this would be appreciated.

Regards,
Craig

[Beth]

To upgrade from any version prior to 3.1.9 will require a few extra steps.

Do you have a backup of your 3.0.2 database? If so, then delete the sgvault and sgmaster databases from your server and restore your Vault 3.0.2 backup.
Then install Vault 3.0.7. If that has no errors, then install Vault 3.1.9. If that goes well, then install Vault 4.1.2.

If at any point there is a failure, then send an email to support at sourcegear.com with a screenshot of the error and a copy of your vault_install.log found in %username%/local settings/temp with a description of what happened.

[spatialminds]

Are you asking if I have a backup from BEFORE I attempted the upgrade that I can use to restore the database to a pre-upgrade attempt state?

If so, I'm afraid that the database has significantly changed since the upgrade extent making the old backup fairly obsolete at this point.

Craig

[Beth]

I'm a bit confused. The answer I gave was meant for being implemented back in September when you originally posted. I'm assuming if there have been changes that you have successfully installed? Or have you not performed the upgrade, but you returned to 3.0.2 successfully (hopefully using a 3.0.2 database)? What has happened since September 10th?

[spatialminds]

I'm a bit confused. The answer I gave was meant for being implemented back in September when you originally posted. I'm assuming if there have been changes that you have successfully installed? Or have you not performed the upgrade, but you returned to 3.0.2 successfully (hopefully using a 3.0.2 database)? What has happened since September 10th?

The original upgrade attempt failed with the messages described in my first post. I'm assuming that since the Vault upgrade installer failed that it didn't upgrade the software or database and is still running version 3.0.2. Would that be a fair assumption to make?

As everything seemed to be working fine, and several submissions had been made by the time your post was made, we didn't make any attempts to restore the db to a pre-upgrade attempt state. We assumed the db had been left untouched or been rolled back when the upgrade failed.

The plan now is to:

- Backup the current database
- Follow your incremental upgrade steps described above.

The only reason for my question here is to insure that the db isn't in some funky 4.? db state that is going to mess up our future upgrades.

Sorry for the confusion on this.

[spatialminds]

I just checked the VaultService web page, and the server is currently running Version 3.5.1.4786, not 3.0.2 as I previously assumed.

[spatialminds]

I was able to upgrade smoothly through version 4.0.9 with everything working. I am having trouble with the 4.0.9 to 4.1.3 upgrade now, but that is unrelated to this thread topic.

The correction for the original Error 1721 is documented in the release notes of 4.1 http://sourcegear.com/vault/releases/4.1.html which itself links to a solution for removing the Fortress Client http://support.sourcegear.com/viewtopic.php?t=9629. If you follow the linked solution, but uninstall the Vault Client instead you will be able to perform the upgrade without encountering Error 1721.

[Beth]

Thanks for keeping us updated. You look like you're on the right track. Feel free to ask any further questions you may have.