SCCM - MSI Error 1603 error when deploying an appl. VBscript - How to obtain the local SCCM Proxy Poin. this way when he MSI executes and calls the installscript service to start it will start up as the user who kicked off the installer, not as the logged on user (standard user) who doesn't have rights to install software.ĪppDeploy have a good write up on this issue.Īppdeploy Video - Dealing with InstallScript Suggest you follow the troubleshooting in the. Action RegisterComServer, location: C:\Program Files\Citrix\Virtual Desktop Agent\, command: C:\Windows\Microsoft.NET\Framework64\v9\regasm.exe /silent /tlb DirectorComServer.exe. Contact your support personnel or package vendor. Would like to find the root cause of this before proceeding to the production environment. We need to change the Installsheild permissions from executing as the 'interactive user' to executing as the 'Launching User'. A program run as part of the setup did not finish as expected. 15:35:07: Information - CApp::SetExitCode(45) - Exit code is 1602 (called with 1602) 15:35:08: Information - CComponentManager::GetInstallStatus(505) - Component was Self Service Plug-in installed successfully. : C:Program FilesCitrixReceiver StoreFrontFeaturesExplicitFormsCommon Also already tried stopping all Citrix services, IIS service and MS monitoring agent before starting the upgrade process. The root cause of this turns out to be the InstallScript DCOM Permissions for any version of IISscript installed. It seems this application was meant to use a setup.exe to invoke the MSI. The application was deployed using and MSI and it was trying to start up the installscript engine but failed. ISMsiServerStartup Failure, Failed to Initialize script support, Error = 0x80070006 I recently came across and issue whereby I created a deployable package and it worked fine under admin but kept failing on a users machine.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |