We faced an issue after installing a s/w which has version then while upgrading the s/w to higher version, found upgradation was failed with below mentioned error.

Action start 4:56:49: ISStartup.
1: The InstallScript engine version currently installed on this machine is adequate.
MSI (s) (A0!90) [04:56:50:523]: PROPERTY CHANGE: Adding ISStartupEvent property. Its value is 'E5650523'.
1: Event 'E5650523' is created
1: GetInstallDriver, Can not find InstallDriver in ROT table, Return Code = 0x80004005
1: {53FF6C80-F062-4CBE-AA4D-B832F86C6C19}
1: Extract supporting files
MSI (s) (A0!90) [04:56:51:351]: Note: 1: 2732 2: 0
MSI (s) (A0!90) [04:56:51:382]: Note: 1: 2732 2: 0
1: Failed to extract IGdi.dll, Ignore it.
1: ISMsiServerStartup Failure, Failed to RegisterMsiServer, Error = 0x80004004
1: MsiServerStartup failed. Abort installation.
Action ended 4:57:16: ISMsiServerStartup. Return value 1603.

The above mentioned error has occured inside RemoveExistingProduct (Custom Action) function which returns 3.

Please share your valuable suggestion to resolve the above issue.

Thanks in Advance
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


This issue has been resolved in AppDeploy previously. Im not sure about the link.

Please search in AppDeploy
Answered 01/20/2010 by: mekaywe
Brown Belt

Please log in to comment

Thanks for quick response

We have searched in appDeploy and found the below link for similar issue
http://itninja.com/question/how-do-you-roll-out-new-machines?1892&mpage=1&key=ISMsiServerStartup%2CFailure&#21892 and applied their changes and found the same issue.

1 . DCOM Change

We have created our MSI file in InstallShield Version11 and ISScript11.

Please help us to resolve the issue.

Thanks in Advance
Answered 01/20/2010 by: TWSenthil
Yellow Belt

Please log in to comment
You need to find entries for ALL the InstallShield drivers/engines in the AppID branch and remove the 'RunAs' entry. IIRC, there were flavours of one version, some of which were set and some which weren't. Pretty much what I said in post # 12 in the thread you linked to, in fact.
Answered 01/20/2010 by: VBScab
Red Belt

Please log in to comment