Enterprise Vault Installation fails with error code 1603 in MSI install log
Article ID: 100046960
Updated On:
Description
Error Message
From the EV installation log file -
MSI (s) (C8!68) [20:21:17:701]: PROPERTY CHANGE: Deleting WixQuietExec64CmdLine property. Its current value is '"C:\Program Files (x86)\Enterprise Vault\x64\WebAppInstallUtility.exe" -InstallMode install -AppType EVOData -InstallPath "E:\Apps (x86)\Enterprise Vault\EVOData"'.
Action start 20:21:17: ConfigureEVODataCmd.
WixQuietExec64: Error 0x80070001: Command line returned an error.
WixQuietExec64: Error 0x80070001: QuietExec64 Failed
WixQuietExec64: Error 0x80070001: Failed in ExecCommon method
CustomAction ConfigureEVODataCmd returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Cause
This issue is caused when the Default Web Site is removed from IIS and EV attempts to add a virtual directory.
Typically, this is done as a part of server hardening. All other prerequisites are installed and Deployment Scanner does not show any issues with IIS as it is installed on the server.
Resolution
Recreate the Default Web Site under IIS to allow for the EV virtual directories to be created properly.
To recreate the Default Web Site in IIS with the standard configuration, including the default application pool and physical path, follow these steps:
1. Open IIS Manager by searching for IIS Manager in the Windows Start menu or by running inetmgr from the Run dialog.
2. Expand the server name in the left-hand Connections pane, right-click on the Sites node and select Add Website from the context menu.
3. Configure Website Details:
3.1. Site name: Default Web Site
3.2. Application pool: Select DefaultAppPool
3.3. Physical path: Set this to %SystemDrive%\inetpub\wwwroot. This typically resolves to C:\inetpub\wwwroot.
3.4. Binding: Leave the default settings for the binding (Type: http, IP address: All Unassigned, Port: 80).
3.5. Click OK.
4. The newly created Default Web Site should now appear under the Sites node in IIS Manager. Ensure it is started (indicated by a green play icon). If it is stopped, right-click and select Start.
Issue/Introduction
