Web Viewer installer quits immediately with error 1603

Problem

When running the Web Viewer installer, the installation program quits immediately without leaving a log file. Error message mentions "error 1603".

Summary of solutions

The issue can be solved by the following actions. Please refer to the sections further down for the details on each solution.

1. If version is 4, then ensure that "Enable 32-Bit Applications" is set to "True" for the DefaultAppPool

2. Ensure that the Default web application has a http binding to port 80

3. Ensure that the Default web application has ID 1

4. Ensure that "Enable IIS 6 compatibility" is installed in the "Turn Windows Features On or Off" section of the "Program and Features" Control panel. This happens for version 5.1.

5. Ensure that the installer is run by an Administrator

6. Ensure redirects in IIS are disabled

Background: 32-bit installer

Error 1603 can occur when the (default) app pool of IIS does not allow 32-bits applications. This is valid for installation of Signifikant Server or Web application, version 5.0 or earlier.

Version dependency

Prior to version 4.2.2 Signifikant requires to be run in 32-bit mode in IIS.

From version 4.2.2 - version 5.0.8 Signifikant can run in 64-bit mode, but installer still requires 32-bit mode.

Version 5.1 and later do not require 32-bit mode and application performs best in 64-bit mode.

Solution

To solve this, please open IIS Manager, right-click on the default app pool in the "Connections" pane and select "Advanced settings". Then change "Enable 32-bits applications" to True and try to install the Web Viewer again (run as administrator).

If you run version 4.2.2 or later, it is possible to set "Enable 32-bits applications" to False again after installation is completed to enable application to run in 64-bit mode.

For version 5.1 and later, the setting is not an issue and should be set to False..

Background: Default Web Site definition

Error 1603 can also occur when the Default Web Site bindings is only to https and not to http. The installer assumes a port 80 (http) binding is available. If not, the installer will abort and the installation is rolled back.

Furthermore, the default site is found on index 1, not by its name. If more then one site is defined, the index order may be changed and the Default Web Site has got a new index number.

Solution

To solve this, please open IIS Manager, select the Default Web Site and edit Bindings. Ensure that a binding with type http is defined, for port 80.

Also select the Sites node and ensure that the Id is 1 for Default Web Site .

Open

Background: Installer depends on IIS6 

Error 1603 can also occur when Microsoft installer fail to access a component, installed with IIS6 Metadata and configuration. The installer log file contains detailed logging, and the presence of this indicate indicate a component is missing:

Solution

When searching for the error, here is an explanation: https://codeasp.net/blogs/microsoft-net/1214/msi-installer-error-custom-action-completed-with-return-code-340

To enable IIS 6 compatibility. Go to Control panel -> Program and Features-> Turn Windows Features On or Off and modify as shown in the image below:

Open

Background: Installer must be run by an administrator

Error 1603 can also occur when Microsoft installer fail to access a windows resources when not started by an administrator.

The installer log file contains detailed logging, and the presence of this indicates this error:

Solution

Restart installation as an administrator.

Background: Installer must be run by an administrator

Error 1603 can also occur when a redirect is active.

The installer log file contains detailed logging and indication of this error:

Solution

Check http redirect on server and site level and disable.

Related articles