The installation of GFI LanGuard fails and displays error 1603.
- GFI LanGuard
- All supported environment
This is a generic error which can have different causes, such as:
- Database upgrade errors.
- Short file name creation is disabled on the target machine.
- An Install Script custom action is prototyped incorrectly.
- A file is locked and cannot be overwritten.
- The Microsoft Windows Installer Service is not installed correctly.
- The Windows Temp folders are full.
- The setup was corrupted after installation and, therefore, fails with this error during un-installation.
- An older version of Install Shield Developer is being used.
- Print and File sharing is disabled.
- Go to Start > Run and type %temp%.
- Open the file lanss_v121_agentinstallkitlog.txt in a text editor.
- Search for return value 3 which should be located in the verbose log that lists the action that failed and caused the setup to rollback.
The indications of the file can point to one or more of the following solutions:
Possible solution 1: Empty all temporary folders
- Launch command prompt.
- Run the command set
- Note the path listed for TEMP and TMP. For example:
- Delete all files in these locations.
Possible solution 2: Close other applications
Make sure no other applications, including utilities such as virus scanners, are running in the background. Close all running applications and utilities, and launch the installation again.
Possible solution 3: Make sure short file name creation is enabled
- Go to Start > Run and type regedit.
- Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem.
- Double-click NtfsDisable8dot3NameCreation.
- Change the value to 0.
- Reboot the machine to apply this change.
Note: If short file name creation is required to be disabled, reset the NtfsDisable8dot3NameCreation value to 1 after installation and reboot.
Possible solution 4: Ensure that the Windows Installer Service is running
- Go to Start > Run and type services.msc.
- Find the Windows Installer service and ensure that the status is set to Running and that it is set to Automatic startup.
- Right-click > Properties to change the startup setting or to start the service.
Possible solution 5: Re-register the MSIExec
- Open a command prompt in elevated mode as Administrator.
- Run the commands below:
Possible solution 6: Ensure the user logged on the server has enough permission on the drive
- Navigate to the driver where the previous version of GFI Languard is installed. For example, drive C.
- Right-click Properties and go the security tab.
- Click SYSTEM and ensure that the Allow box of every item in Permissions for SYSTEM is checked.
- Repeat the previous step for Administrators.
- Add the domain administrator user and grant full permissions on the drive.
- Click Apply and click OK twice.
Possible solution 7: Upgrade GFI LanGuard from clean boot
Start GFI LanGuard server using clean boot and verify if the upgrade is completed:
- Microsoft Windows 7, 8 and 10:http://support.microsoft.com/kb/929135
- Microsoft Windows Server 2008, 2012 and 2016
- Go to Start > Run and type msconfig.exe.
- Under Boot check Safe boot and Minimal.
- Click Apply and click OK.
- Reboot the server.
- Install GFI LanGuard.
- Create all backups for GFI LanGuard following the support article, https://www.gfi.com/support/products/gfi-languard/How-to-backup-GFI-LanGuard
- Uninstall LanGuard from Control Panel.
- Reinstall GFI LanGuard using the latest version.
- Link old database in the new installation of LanGuard > Configuration > Database maintenance options > Database backend settings... Under Database Name field enter the LanGuard database name that was previously used.
- Import settings from the exported backup in the new installation of LanGuard by using the below support article:
Possible solution 8: Run the Microsoft Windows Installer CleanUp utility
If this error occurs during uninstallation, use the Microsoft Windows Installer CleanUp utility to uninstall the GFI LanGuard. You can re-attempt the installation process after uninstallation.