XenApp 6.0 Fundamentals installation fails and the following error message is displayed:

“Installation of Citrix XenApp Fundamentals has failed. The log file ‘C:\Users\Administrator.Graham\AppData\Local\Citrix\Citrix Access Install Log.txt’ contains diagnostic information.”

 
All components are installed correctly except for the XenApp component as displayed in the following screen shot:

 
The following are the only three errors that are found in the Install log:

(SERVER) MSI (s) (34:60) [17:09:12:885]: Product: Citrix XenApp Fundamentals SMA -- Error 1920. Service 'IMAService' (IMAService) failed to start. Verify that you have sufficient privileges to start system services.
(POLICY) MSI (s) (34:60) [17:09:12:891]: User policy value 'DisableRollback' is 0
(POLICY) MSI (s) (34:60) [17:09:12:891]: Machine policy value 'DisableRollback' is 0
(ERROR) Action ended 17:09:12: InstallFinalize. Return value 3.
 
(SERVER) MSI (s) (34:60) [17:09:13:226]: MsiProvideAssembly is returning: 1607
(SERVER) MSI (s) (34:60) [17:09:13:233]: Note: 1: 2318 2:
(SERVER) MSI (s) (34:60) [17:09:13:234]: No System Restore sequence number for this installation.
(SERVER) MSI (s) (34:60) [17:09:13:234]: Unlocking Server
(SERVER) MSI (s) (34:60) [17:09:13:236]: PROPERTY CHANGE: Deleting UpdateStarted property. Its current value is '1'.
(ERROR) Action ended 17:09:13: INSTALL. Return value 3
 
(POLICY) MSI (s) (34:E8) [17:09:13:246]: User policy value 'DisableRollback' is 0
(POLICY) MSI (s) (34:E8) [17:09:13:246]: Machine policy value 'DisableRollback' is 0
(SERVER) MSI (s) (34:E8) [17:09:13:247]: Incrementing counter to disable shutdown. Counter after increment: 0
(SERVER) MSI (s) (34:E8) [17:09:13:247]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
(SERVER) MSI (s) (34:E8) [17:09:13:247]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
(SERVER) MSI (s) (34:E8) [17:09:13:248]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
(SERVER) MSI (s) (34:E8) [17:09:13:248]: Restoring environment variables
(SERVER) MSI (s) (34:E8) [17:09:13:249]: Destroying RemoteAPI object.
(SERVER) MSI (s) (34:F0) [17:09:13:249]: Custom Action Manager thread ending.
(CLIENT) MSI (c) (F0:D0) [17:09:13:252]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
(ERROR) MSI (c) (F0:D0) [17:09:13:253]: MainEngineThread is returning 1603 

Complete the following steps:

1. The following error message is displayed when you run the MSIEXEC /I “path to MPS.MSI” CTX_MF_SERVER_TYPE=”P” command.

2. Run the following command to ignore the preceding error message, MSIEXEC /I “path to MPS.MSI” CTX_MF_SERVER_TYPE=”P”  CTX_MS_HOTFIX_CHECK_BYPASS=Yes

3. The following error message is displayed as the installation continues:

Complete the following steps to resolve the preceding error:

1. From Start menu, execute Run, and type regedit.

2. Navigate to the parent container: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components.
   Note: The 'S-1-5-18' key might be different on your computer.

3. As per the preceding screen shot, look for the first of the two GUIDs, namely "C9AE13788D0B61F80AF18C3B9B1A1EE8". Scroll through the children of the Components key to locate this corresponding first of two GUIDs from the message box, as displayed in the following screen shot.

Most often this has a + beside the folder since it has one or more children items in it (one of which is the second GUID from the message box, as displayed in the following screen shot).

You can use the Find command within the registry editor but this is a much slower and more tedious operation to perform.

4. Right-click the parent container registry key, which is C9AE13788D0B61F80AF18C3B9B1A1EE8 in this example.
   Note: The following screen shot uses the 000085D... registry key for illustrative purposes only.

5. Click Permissions..., as displayed in the following screen shot:

6. Select Add in the Permissions for... dialog box, and add the Administrator, Administrators, and SYSTEM accounts, as displayed in the following screen shot:
   Note: Ensure to add your local account which had administrator privileges.

7. From the Permissions for Administrator section, select Allow for the Full Control and Read option, as displayed in the preceding screen shot:

8. Click Advanced to display the following Advanced Security Settings dialog box.

9. Navigate to the Permissions tab; select Replace all child object permissions with inheritable permissions from this object, and click Apply.

10. Navigate to the Owner tab, highlight Administrators, select Replace owner on subcontainers and objects, and click Apply. 

11. Repeat Steps 9 and 10. This time around you should not get any errors about not being able to update the permissions on the child keys.

12. Click OK to exit.

13. Re-run your Microsoft installer or un-installer.

Notes

• It is recommended that you right-click the icon and execute Run as administrator... if the option is available.

• The Could not open key error message is displayed, on the exact same keys when the preceding operation is not performed correctly.