Virtual Delivery Agent failed with code InstallFailure 1603

If you are upgrading or installing the Desktop or Server VDA and getting either of the below error messages then read on.

Installation of MSI File ‘IcaTS_x64.msi’ failed with code ‘InstallFailure’ (1603).

Installation of MSI File ‘IcaWS_x64.msi’ failed with code ‘InstallFailure’ (1603).

I recently got this message when upgrading the VDA within a Citrix Platform Layer (Citrix App Layering). In this example, access to read the LoggedEvents registry key was denied.

Upon receving the error message, click on Why did this fail?

Confirm the error relates to the installation of IcaTS_x64.msi or IcaWS_x64.msi.

Go to Event Viewer. Within the Application log you’ll see why exactly the install failed. Notice that the LoggedEvents key could not be opened.

Open RegEdit and browse to the key manually (HKLM\Software\WOW6432Node\Euem\LoggedEvents). You’ll get an Access is denied error.

Right-click the Euem key and select Permissions.

Click Advanced.

Check Replace all child object permission entries with inheritable permission entries from this object -> Apply.

Click Yes. If you get an error, set yourself as the owner of the LoggedEvents key and re-run the above steps. 

Now you’ll be able to read the key, and install the VDA.

If you are getting the 1603 installation error due to a different issue than what is described above, try these three possible fixes:

  • Reset performance counters
    1. Open CMD as an administrator
    2. Run command lodctr.exe /R
    3. Restart the machine
  • Rebuild WMI repository
    1. Open CMD as an administrator
    2. Run command sc config winmgmt start=disabled
    3. Run command net stop winmgmt
    4. Run command winmgmt /salvagerepository %windir%\System32\wbem
    5. Run command winmgmt /resetrepository %windir%\System32\wbem
    6. Run command sc config winmgmt start=auto
    7. Restart the machine

3 Comments

  • Serg

    September 5, 2017

    Spot on, thank you!

    Reply
  • Martyn Dews

    February 14, 2018

    Hi George.

    Thanks for posting this. I have come the same error and it was due the registry permission issue. In my case SYSTEM did not have rights over the subkey whilst it did for the parent.

    The question I have is why this missing permission exists. Do you know the root cause of why they are not propagated to the child?

    Martyn

    Reply
    • George Spiers

      February 14, 2018

      Hi Martyn. Not sure of a root cause. Have not got this issue in a while now. I do know Citrix are working on reducing the likelyhood of 1603 errors happening in future VDA releases.

      Reply

Leave a Reply