BigFix Exit Code 1603

1

Hi

I am trying to deploy BigFix Remote Control Target on a Windows machine and it’s getting failed with exit code 1603.

Also tried to install the trc_target_setup.exe manually on the same machine and getting error as “Error 1920. Service BigFix Remote Control - Target (TRCTARGET) failed to start. Verify that you have sufficient privileges to start system services”. We have also tried logging in with super user credentials and still facing the same error.

Please help as we are facing this issue at Client Location on multiple Windows machines.

2

Hi,

According to the Microsoft documentation the error 1603 means:

1603 - ERROR_INSTALL_FAILURE

Fatal error during installation.

while the error 1920 means:

1920 - ERROR_CANT_ACCESS_FILE

The file cannot be accessed by the system.

The installer needs to have access to the registry and the installation folder which is by default C:\Program Files (x86)\BigFix\Remote Control\Target.

There must be something which is blocking the access to these resources. What version of OS are you trying to install on ? What is the version of the installer ?

3

1603 is a catch-all error code for MSI-based installers. It can mean many things. In this case, I often find that the installation will succeed after a reboot.

4

Also check whether right-clicking the installer and using 'Run as Administrator helps.

5

Hi, We are majorly facing this issue on Win 7 6.1.7601 OS and a few PCs of Win10 10.0.10240.16389 and Win10 10.0.18362.1(1903).

And Target Installer Version is 10.0.0.0518.

6

Hi,
We have tried this as well with domain superuser but still the same error pops up.

7

I suggest you to take a look at the file rc_fixlet.log in the folder C:\Program Files (x86)\BigFix Enterprise\BES Client\__BESData on the Client machine where the Target installation is attempted.

When an installation fails the fixlet copies the msi log into this file. You can see this operation in the action script of the fixlet. Let’s see if you can get more information from this.

My guess is that since you are using domain users and the machines are in a domain there may be some restrictions set on the policies that prevents users (even domain admins) from accessing the registry or the program folders. So I suggest you to try a manual installation also with a local user (non-domain user) with admin privileges and see if the result changes.

2 Likes