Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Problem

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

Version Installation of Signifikant Server or Web application, version 5.0 or earlier is installed.

Background: 32-bit installer

Error 1603 can occur when the (default) app pool of IIS does not allow 32-bits applications. 

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.

Error 1603 can occur when the (default) app pool of IIS does not allow 32-bits applications. 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.

...

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

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:

[SetTARGETSITE]: Custom Action failed with code: '340'

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:

Image Added

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:

SetTARGETSITE Access denied.

Error 1925. You do not have sufficient privileges to complete this installation for all users of the machine.  Log on as administrator and then retry this installation.

SetTARGETSITE Custom Action failed with code: '5'

Solution

Restart installation as an administrator.

Related articles

Filter by label (Content by label)
showLabelsfalse
max5
spacesASKB
showSpacefalse
sortmodified
reversetrue
typepage
cqllabel = "webviewer" and type = "page" and space = "ASKB"
labelswebviewer

...