Installation of MSI File ‘IcaWSx64.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. Installation of MSI File ‘IcaTSx64.msi’ failed with code ‘InstallFailure’ (1603). Installation of MSI File ‘IcaWSx64.msi’ failed with code ‘InstallFailure’ (1603). I recently got this message when upgrading the VDA within a Citrix Platform Layer (Citrix App Layering). Feb 12, 2014 Today I would like to describe you an interesting problem I had during my last receiver deployments. The start of the installation always failed with the message: The configuration manager.
vCenter server update fails with error
2018-11-01 06:22:37.632-04:00 vcsInstUtil-9451637 I: RunFirstLastUpdateboot: Successfully ran boot script: “C:Windowssystem32cmd.exe /S /C “”D:Program FilesVMwarevCenter Serverbinrun-updateboot-scripts.bat” –action rollback >> C:UsersadminAppDataLocalTempvminst-con.log 2>&1″”
2018-11-01 06:22:37.632-04:00 vcsInstUtil-9451637 I: Leaving function: VM_RunUpdateBoot
2018-11-01 06:22:37.695-04:00 vcsInstUtil-9451637 E: wWinMain: MSI result of install of “D:VMware vCenter Server 6.5 U2cvCenter-ServerPackagesvcsservicemanager.msi” may have failed: 1603 (0x00000643)
2018-11-01 06:22:37.695-04:00 vcsInstUtil-9451637 E: LaunchPkgMgr: Operation on vcsservicemanager.msi appears to have failed: 1603 (0x00000643)
2018-11-01 06:22:37.695-04:00 vcsInstUtil-9451637 I: PitCA_MessageBox: Displaying message: “Installation of component VCSServiceManager failed with error code ‘1603’. Check the logs for more details.”
Some times while upgrading/updating the PSC or vCenter server , we hit an error with code 1603, there could be multiple reasons for this error and isolating the issue is bit difficult by checking the logs and time consuming as well.
Recently, we faced an issue while updating our vCenter server and found a simple solution. And it is worth trying before you proceed with the log analysis.
Whenever we install vCenter server and its components on a server, it creates few local accounts with respect to the services related to vCenter server and those users are managed by the vCenter / its components itself. And the users needs administrative privilege while performing the update/upgrade.
During the upgrade/update, if those users doesn’t have enough privilege, then that may lead to the update failure. Mostly, this happens due to accidental removal of the account from Administrator group or by the Group policy which removes the account from Administrator group.
In my scenario, we have separate PSC and VC, we had the same situation, our AD Group policy removed the user from Administrator group which led to update failure, to resolve the issue we added the user to the Admin group and restarted the update
User list :
Launched User Management MMC
Start –> Run –> lusrmgr.msc
Machine had one local user and it belongs to vCenter Component (PSC) named vapiEndpoint and that user was not a part of Administrator group.
This user has been added to Administrator group and the update process was restarted. Post that we were able to update our PSC successfully.
In the similar way, we added all the users given below which are related to vCenter server service on VC machine under Administrator group, that helped us to resolve the issue.
If the above solution doesn’t help you or if the users already in the administrator group, then you have to check the logs for other errors.
Hope this article help you!!