When you install, uninstall, or upgrade using MetaInstaller on a Windows-based computer, you may receive one of the following error messages.

Installation of MSI File ‘[ABC.msi]’ failed with code ‘Installfailure’ (1603).

where ABC.msi filename can refer to any .msi file. For example, IcaTS_x64.msi , BrokerAgent_x64.msi etc.

While 1603 is the most common failure code from Microsoft MSI Engine, one may also observe different error messages and codes. These troubleshooting steps are recommended for all such failures.

Table of Contents

• Pre-requisites
• Troubleshooting Steps
• Rectify Incomplete Installation which could interrupt any future installations
• Troubleshoot/Resolve issues using Citrix MSI Log Analyzer
• Resolve issues which could be due to corruption
• Issues caused due to permissions or access issues
• Other causes to check
• What Next?

Pre-requisites

You need Administrator rights on your account to perform the steps listed in this article. Check User Accounts to see if you have Administrator rights or contact your Network Administrator to gain permissions.
It is recommended that you watch below VDA Upgrade Leading Practices before you perform upgrade.

Back to top

Troubleshooting Steps

Rectify Incomplete Installation which could interrupt any future installations

When an installation does not complete or roll back successfully, some files may remain in the system. Windows Installer considers the incomplete installation to be active and does not install new products or re-install existing products until the installation is resolved. Follow the instructions in this article to resolve this issue: Error: When Trying to Install or Remove XenApp Software, a 1603 Error Message is Displayed

Back to top

Troubleshoot/Resolve issues using Citrix MSI Log Analyzer

Citrix MSI Log Analyzer is a tool that troubleshoots install issues or upgrade issues and enables customers to resolve common issues by pointing them to a specific support article.

Note. You may skip this step if you were pointed to this article by the MSI Log Analyzer tool or the XenApp Xendesktop 7.16 Metainstaller, which has been integrated with the MSI Log Analyzer.

1. Follow instructions in CTX229734 to download the latest version of the tool on the target machine where the installation failed occurred. Citrix recommends that you obtain the latest version of the tool.

Review these additional troubleshooting steps, in cases where steps above did not resolve the issue 

Back to top

Resolve issues which could be due to corruption

Though the exact cause may vary from case to case, there could be a sign of corruption in registry, Performance counters, WMI providers, C++ Runtimes or or .NET Installation. 
This guide begins with the least intrusive methods to help troubleshoot these issues. It is not intended to be an exhaustive guide, but it should be able to provide solution for the majority of these issues.

1. Fix problems that block programs from being installed or removed
   Refer to this article for more information. 

2. Repair Missing or corrupted System files
   Run ‘sfc /scannow’ both in online and offline mode. Refer to this link for more details. 

3. C++ RunTime

Occasionally, the C++ redistributable packages are corrupted or inconsistent which may cause installations and upgrades to fail.

1. Each XA/XD release comes with the system requirements. For example: 7.15 requirements are available here.
   Note: For your case open the link specific to the XA/XD release version being installed

2. In the page, refer to the section on Virtual Delivery Agent(VDA) for Desktop OS and Server OS which provides details on the specific Microsoft Visual C++ runtimes.
   
   For example: As shown above VDA 7.15 on Desktop OS needs VC++ 2013 and 2015 runtimes. Depending on the version you are installing the runtime versions for those VDA may be different.

3. The version mention in the documentation list the year. Follow the below steps to note down the File Versions of the actual msi of the VC++ runtime. Open/Mount the XenApp/Xendesktop ISO layout and browse to the Support folder. For each VC++ runtimes noted in step ii above browse to that sub-folder within the Support folder. For each of those, Right click the vcredist msi file under the respective VCRedist folder, Click Properties and Note down the File Version under Details tab. Make a note of all the 4 parts separated by dot for each vcredist msi file.
   

4. Launch Control Panel and under Installed Program list note down all the VC++ runtime versions with the dots. If any of the version noted in step above is missing then one should install the specific version from the support folder under the Layout. On a 64 bit machine, both 32 bit and 64 bit versions are required to be installed. If all versions are present in the control panel then there might be some corruption in which case it is recommended to uninstall and reinstall those specific versions.

Test to install again and see if the problem persists.

4. .NET Repair

   1. Follow steps here https://support.microsoft.com/en-us/help/2698555/microsoft--net-framework-repair-tool-is-available  to repair .NET
   2. Test to install again and see if the problem persists.

• Performance Counters
  Verify that the Performance Counters can be reloaded by opening an elevated CMD shell and type the following commands ( hit [ENTER] after each line) :

           cd c:\windows\system32 
           lodctr /R
          cd c:\windows\sysWOW64
           lodctr /R

  Resync the counters with Windows Management Instrumentation (WMI):
  WINMGMT.EXE /RESYNCPERF
  Stop and restart the Performance Logs and Alerts service.
  Stop and restart the Windows Management Instrumentation service.
  Check the event viewer for any errors.

Back to top

Issues caused due to permissions or access issues

1. Citrix MSI Log Analyzer output may point to the file/registry location where one should assess the permissions and ensure the administrator installing the VDA has necessary permissions. If not grant permission and try the installer again
2. Try to temporarily move the VDA out of the OU enabled GPO and try installation once again, then move the VDA back to previous OU post the successful installation.

Other causes to check

1. You may receive this error message if any one of the following conditions is true:
2. Windows Installer is attempting to install an app that is already installed on your PC.
3. The folder that you are trying to install the Windows Installer package to is encrypted.
4. The drive that contains the folder that you are trying to install the Windows Installer package to is accessed as a substitute drive.
5. The SYSTEM account does not have Full Control permissions on the folder that you are trying to install the Windows Installer package to. You notice the error message because the Windows Installer service uses the SYSTEM account to install software.
6. Sometimes AntiVirus may interfere with the installations. Disable the anti-virus software and attempt the installation.
7. In some cases it is observed running in as a domain instead of a local Administrator or vice versa may help resolve the issue.

What Next?

This really boils down to an OS based problem in most cases. Here are some solutions that have worked in other support cases.

1. There is a deeper fix that can rebuild the performance counters from scratch. See links below.
2. Admins can re-register the Windows installer service and look at other general Windows MSI repair options.
3. Admins can attempt a repair install of Windows.
4. If none of these steps delivers a resolution, further data can be captured by collecting MSI logs and running CDF Control on the machine while the installer runs.
5. Links provided in the Additional Resources section.

5. Use the VDA Cleanup Utility

Back to top

• How to manually rebuild Performance Counters
• WMI: Repository Corruption, or Not?
• How to Enable Microsoft Installer logging
• CTX111961 - CDFControl
• CTX132117 - Error: When Trying to Install or Remove XenApp Software, a 1603 Error Message is Displayed