What causes this? I'm on Windows Server 2008 R2 64-bit running the VaultServer64_6_0_1_598.msi.
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. Action: CustomActionExe.exe, location: C:\inetpub\wwwroot\VaultService\bin\CustomActionExe.exe, command: /TARGETDIR="C:\inetpub\wwwroot\VaultService\ " /TARGETDIR2="C:\inetpub\wwwroot\VaultPro\ " /WEBDAV="C:\inetpu..."
Vault 6.0.1 Standad Installer -- Error 1721?!
Moderator: SourceGear
-
- Posts: 47
- Joined: Thu Jun 25, 2009 12:02 pm
Re: Vault 6.0.1 Standad Installer -- Error 1721?!
This is an .msi error. Users sometimes get this error when the installer has trouble with registry entries from a previous installation.
Is this a fresh install on a new machine? An upgrade of an existing version of Vault? If so, which version?
Is this a fresh install on a new machine? An upgrade of an existing version of Vault? If so, which version?
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
-
- Posts: 47
- Joined: Thu Jun 25, 2009 12:02 pm
Re: Vault 6.0.1 Standad Installer -- Error 1721?!
Well, we had Vault 5.x installed on another box and installing 6.0 onto a new box, but upgrading the existing database. So it is/isn't an upgrade.lbauer wrote:This is an .msi error. Users sometimes get this error when the installer has trouble with registry entries from a previous installation.
Is this a fresh install on a new machine? An upgrade of an existing version of Vault? If so, which version?
We did three things, all at once and overcame the problem. I don't know which of these were the culprit:
- Copied the downloaded MSI locally (we had it on a shared drive, accessed via a UNC path... MSI sometimes has toruble with this)
- Ran through msiexec (with the goal of getting more MSI logging)
- Ran that msiexec from an command prompt that was running with administrator privileges
Re: Vault 6.0.1 Standad Installer -- Error 1721?!
Thanks for the update. Probably giving the installer adequate permissions helped. That can be accomplished by running the installer on the machine where you are installing. Also, elevating the permissions by installing from a command prompt which is running as Administrator is a good idea.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager