Phone Lines icon GFI Support Home

Articles in this section

See more

Why do I get vague error code 1603 when installing Central Management Server?

Author: Andriy Rybalchenko Updated

Overview

When you try to install the Central Management Server, the installation fails or starts the roll back process with a vague error code 1603 stating that the installation ended prematurely.

 

Solution

This is a generic Windows error that can have many different possible causes. First of all, ensure the important LanGuard installation requirements, such as:

  1. The user running the installer is a local administrator or the domain administrator with the local admin privileges on the machine where CMS is deployed and a sysadmin role assigned within SQL Server that would be (is) hosting the CMS database.
  2. The installer is unblocked - right-click on it and check Properties.
  3. Any third-party antivirus and other protection engines are disabled.
  4. All other applications are closed, including running in the background.

If the CMS database already exits (by default, LGCMCScanResults12), check if the user running the installer can connect to it. Additionally, verify that the default Languard database has a different name; this can be checked by going to Configuration -> Database Maintenance Options in LanGuard console.

Reboot the server, and retry the Central Management Server installation.

If you still encounter the error, the details can be found in the installation log file lanss_v125_lgcmcinstallkitlog.txt, located in the %TEMP% folder (log file name corresponds to LanGuard version).  Search for errors and the phrase return value 3 that lists the action that failed and caused the setup to rollback, and apply the possible solution(s) below.

Possible solution 1: Empty all temporary folders

  1. Launch Command Prompt.
  2. Run the command set
  3. Note the path listed for TEMP and TMP. For example:
    • TEMP=C:\Users\Owner\AppData\Local\Temp
    • TMP=C:\Users\Owner\AppData\Local\Temp
  4. Delete all files in these locations.

Possible solution 2: Ensure that the Windows Installer Service is running

  1. Run services.msc.
  2. Find the Windows Installer service and ensure that the status is set to Running and Automatic startup.
  3. Right-click > Properties to change the startup setting or to start the service.

Possible solution 3: Make sure short file name creation is enabled

  1. Run regedit.
  2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem.
  3. Double-click NtfsDisable8dot3NameCreation.
  4. Change the value to 0.
  5. Reboot the machine to apply this change.

If short file name creation is required to be disabled, reset the NtfsDisable8dot3NameCreation value to 1 after installation and reboot.

 

Testing

Retry the installation after applying the relevant solution. If the issue persists, contact GFI LanGuard Support and attach the corresponding log file lanss_v125_lgcmcinstallkitlog.txt.

Related articles