/build/static/layout/Breadcrumb_cap_w.png

ISSCRIPT_ENGINE_VERSION = 11.50.0.42618

I am packaging a complex app that has multiple MSIs
App Pre req is Oracle 10g
App has client side and server side installations. Currently I am working on the client side installation.

First three MSIs are Crystal report which installed without any error.
When I install Workbench.msi (this is the main app) it gives me an error :

1.Failed to install ISKernel Files
Make sure you have appropriate privileges on this machine.

I googled and found that the issue is related to ISScript.
Found one of the MSI property ISSCRIPT_ENGINE_VERSION = 11.50.0.42618
Downloaded ISScript11.msi from _http://consumerdocs.installshield.com/selfservice/viewContent.do?externalId=Q108322&sliceId=1 and installed the it.

This doesnt solve my problem as I get the same error.

Now, the story changes when I see the verbose log file. It says there is no issue with the ISScript engine version. I am summarizing what it says:


1: The InstallScript engine version currently installed on this machine is adequate.
1: Event 'E950410' is created
MSI (c) (C8!38) [07:09:50:410]: PROPERTY CHANGE: Adding ISStartupEvent property. Its value is 'E950410'.
1: GetInstallDriver, Can not find InstallDriver in ROT table, Return Code = 0x80004005
1: {E7A14D55-E906-44D2-A00E-D069DA706EF2}
1: Extract supporting files
1: Failed to extract ISRT.dll, error is 2
1: Failed to extract _IsRes.dll, error is 2
1: Failed to extract _IsUser.dll, Ignore it.
1: ISMsiServerStartup Failure, Failed to Initialize script support, Error = 0x80010105
1: MsiServerStartup failed. Abort installation.
CustomAction ISStartup returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 7:09:50: ISStartup. Return value 3.
MSI (c) (C8:24) [07:09:50:996]: Doing action: SetupCompleteError
Action 7:09:50: SetupCompleteError.
Action start 7:09:50: SetupCompleteError.
MSI (c) (C8:24) [07:09:50:997]: Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'SetupCompleteError'
Info 2898.For Tahoma8 textstyle, the system created a 'Tahoma' font, in 0 character set, of 13 pixels height.
Info 2898.For TahomaBold10 textstyle, the system created a 'Tahoma' font, in 0 character set, of 16 pixels height.
Action 7:09:51: SetupCompleteError. Dialog created
MSI (c) (C8:D8) [07:09:51:011]: Note: 1: 2731 2: 0
MSI (c) (C8:28) [07:09:52:886]: Doing action: ISCleanUpFatalExit
Action 7:09:52: ISCleanUpFatalExit.
Action start 7:09:52: ISCleanUpFatalExit.
MSI (c) (C8:28) [07:09:52:886]: Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'ISCleanUpFatalExit'
MSI (c) (C8:D8) [07:09:52:889]: Invoking remote custom action. DLL: C:\Users\Admin\AppData\Local\Temp\MSI4D37.tmp, Entrypoint: CleanUp
Action ended 7:09:52: ISCleanUpFatalExit. Return value 1.
Action ended 7:09:52: SetupCompleteError. Return value 2.
Action ended 7:09:52: INSTALL. Return value 3.



Any help would be appreciated to determine the issue or somewhere I went wrong :(

0 Comments   [ + ] Show comments

Answers (1)

Posted by: anonymous_9363 12 years ago
Red Belt
0
Can not find InstallDriver in ROT table, Return Code = 0x80004005 This looks suspiciously like the old "Launching User" versus "Interactive User" screw-up. In any event, 80004005 is normally "Access denied" so, if it's not the former, I'd strongly suspect some odd permissions on a registry key/value. For the latter, ProcMon will highlight the offender.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ