This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- SP1 InstallScript engine won't initialize on Win2k
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 01, 2009
02:13 PM
SP1 InstallScript engine won't initialize on Win2k
When I run my install (build with 2010 SP1) on a Win2k box, the InstallScript engine fails to initialize. Has anyone else had this issue and found a fix? I have a case open as well, but I was curious if someone else had seen this.
I have a test project that duplicates this as well.
Here is the error from the install log:
InstallShield 12:52:43: Running InstallScript function f1
InstallShield 12:52:43: Opening stream of file C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\MSI21.tmp
InstallShield 12:52:43: Extracting support file IsConfig.ini to C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{7C5DCAB9-1450-4CE6-B1C3-437DCE51CEAC}\IsConfig.ini
InstallShield 12:52:43: Extracted isconfig.ini to C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{7C5DCAB9-1450-4CE6-B1C3-437DCE51CEAC}\IsConfig.ini
InstallShield 12:52:43: Got '{CEE17F78-3D2D-4194-A278-CD69C8D3F90E}' for TempPathGuid from isconfig.ini
InstallShield 12:52:43: Attempting to use temp path 'C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{CEE17F78-3D2D-4194-A278-CD69C8D3F90E}'
InstallShield 12:52:44: Using new temp path
InstallShield 12:52:44: Cleaning up temp file C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{7C5DCAB9-1450-4CE6-B1C3-437DCE51CEAC}\IsConfig.ini
InstallShield 12:52:44: Using temp folder C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{CEE17F78-3D2D-4194-A278-CD69C8D3F90E}
InstallShield 12:52:44: Installing engine...
InstallShield 12:52:44: Using product language 1033
InstallShield 12:52:44: Skipping optional support file _isuser_0x0409.dll
InstallShield 12:52:44: Setting script cmdline...
InstallShield 12:52:44: ProductCode is {AD223476-C3F1-4F91-ADE2-03FEB5A32591}
InstallShield 12:52:44: Initializing Engine
InstallShield 12:52:44: Failed to Invoke __ISRTInit, error is 0x80020009
InstallShield 12:52:44: InitScript operation failed, error is 0x80020009
InstallShield 12:52:44: Failed to invoke __ISRTUninit, error is 0x80020009
InstallShield 12:52:44: Initialize() Failure, Failed to Initialize script support, Error = 0x80020009
Action ended 12:52:44: TestInstallScript. Return value 1.
I have a test project that duplicates this as well.
Here is the error from the install log:
InstallShield 12:52:43: Running InstallScript function f1
InstallShield 12:52:43: Opening stream of file C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\MSI21.tmp
InstallShield 12:52:43: Extracting support file IsConfig.ini to C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{7C5DCAB9-1450-4CE6-B1C3-437DCE51CEAC}\IsConfig.ini
InstallShield 12:52:43: Extracted isconfig.ini to C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{7C5DCAB9-1450-4CE6-B1C3-437DCE51CEAC}\IsConfig.ini
InstallShield 12:52:43: Got '{CEE17F78-3D2D-4194-A278-CD69C8D3F90E}' for TempPathGuid from isconfig.ini
InstallShield 12:52:43: Attempting to use temp path 'C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{CEE17F78-3D2D-4194-A278-CD69C8D3F90E}'
InstallShield 12:52:44: Using new temp path
InstallShield 12:52:44: Cleaning up temp file C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{7C5DCAB9-1450-4CE6-B1C3-437DCE51CEAC}\IsConfig.ini
InstallShield 12:52:44: Using temp folder C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{CEE17F78-3D2D-4194-A278-CD69C8D3F90E}
InstallShield 12:52:44: Installing engine...
InstallShield 12:52:44: Using product language 1033
InstallShield 12:52:44: Skipping optional support file _isuser_0x0409.dll
InstallShield 12:52:44: Setting script cmdline...
InstallShield 12:52:44: ProductCode is {AD223476-C3F1-4F91-ADE2-03FEB5A32591}
InstallShield 12:52:44: Initializing Engine
InstallShield 12:52:44: Failed to Invoke __ISRTInit, error is 0x80020009
InstallShield 12:52:44: InitScript operation failed, error is 0x80020009
InstallShield 12:52:44: Failed to invoke __ISRTUninit, error is 0x80020009
InstallShield 12:52:44: Initialize() Failure, Failed to Initialize script support, Error = 0x80020009
Action ended 12:52:44: TestInstallScript. Return value 1.
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 01, 2009
05:23 PM
It turns out there is a hot fix for this. Here is the link, I guess the moderator may remove it ...
http://kb.flexerasoftware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=Q206628&sliceId=1&docTypeID=DT_HOTFIX_1_1&dialogID=70645032&stateId=0%200%2070647005
http://kb.flexerasoftware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=Q206628&sliceId=1&docTypeID=DT_HOTFIX_1_1&dialogID=70645032&stateId=0%200%2070647005
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 01, 2009
07:00 PM
The issue was not with the IDE box, but on a system trying to run the setup.exe. The hotfix remedied the problem.