Problem:
Some windows installer based packages created with InstallShield Professional Windows Installer 2.03 occasionally abort when
executing custom actions written for InstallScript execution. This problem occurs on random systems and is sporadic.
Cause:
The problem is typically identified by looking a the log file of a failed installation (example):
Action start 9:28:48: StartUp.
1: Startup, Last modification : 12/14/2000
1: Preparing COM context, return = 0x0
1: Tring to start ISScriptHandle engine...
1: ISScriptHandle engine Started
1: Extracting support files...
1: Checking product language...
1: Constructing string table...
1: Creating script engine
1: Starting script engine COM server...
1: Opening script file...
1: Starting Kernel wrapper...
1: Registering the kernel wrapper...
1: Failed to create script engine...
1: Script Handler initialization failed, error = 0x0
Action ended 9:28:50: StartUp. Return value 1.
...<log deleted>....
Action start 9:28:51: ISSCheckRequirements.
1: f0: Function failed, the user might cancel the installation.
Action ended 9:28:52: ISSCheckRequirements. Return value 3.
...<log deleted>....
The StartUp action fails to create the Script Engine so when the first InstallScript custom action is executed we get a Function failed message. On InstallScript custom actions that look for valid return codes this causes the installation to fail and rollback.
On successful startups of the engine the log looks like:
Action start 9:26:40: StartUp.
1: Startup, Last modification : 12/14/2000
1: Preparing COM context, return = 0x0
1: Tring to start ISScriptHandle engine...
1: ISScriptHandle engine Started
1: Extracting support files...
1: Checking product language...
1: Constructing string table...
1: Creating script engine
1: Starting script engine COM server...
1: Opening script file...
1: Starting Kernel wrapper...
1: Registering the kernel wrapper...
1: Starting up setup service...
1: Setting up selected language...
1: Calling __ISRTInit
1: Script engine started successfully.
1: Calling __ISWIInit
1: Calling __ISWIOnBegin...
1: Script engine initialization finished.
Action ended 9:26:41: StartUp. Return value 1.
Workaround:
We have opened cases with InstallShield to try to correct the problem and have been asked to discontinue use of InstallScript actions or migrate to Developer 7.
This should be described in InstallShield case number 1-73J93. We have also found a workaround that seems to be reliable that is also documented in
ROSmm18508. The workaround is described as follows:
The installer on the system must be corrupt.. It would be necessary to remove the previous installer before attempting a new install. Follow these steps:
1) stop the windows installer service from services in control panel
2) stop any running installations that you may have.
3) Check and make sure Ikernel.exe is not in memory. If it is, and not setup is running at the time, end that task. Do this with task manager.
4) Clean out the Temp directory.
5) Delete the Program Files\Common Files\InstallShield\Engine folder.
6) reboot the system.
7) try the installation again
You can also reference InstallShield notes at : http://support.insta...ticleid=Q104985
We have also added some additional steps to the installation to try to limit this problem.
A) followed procedures outlined in http://support.insta...ticleid=Q105420
B) rebuilt MSCore msi file that we believe had a corrupt kernel.