cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
MRKiscaden
Level 5

Install Scripts fail on Win Server 2008

I have an InstallScript Custom Action (InitInstallDir) that is launched immediately after the CostFinalize action. Right now, It simply writes to the MSI log and returns. This Custom Action works perfectly in Windows XP and Windows Vista. However with Windows Server 2008 I get the following error:

[CODE]MSI (c) (50:D0) [16:24:39:788]: Doing action: InitInstallDir
Action start 16:24:39: InitInstallDir.
MSI (c) (50:E4) [16:24:39:850]: Invoking remote custom action. DLL: C:\Users\mrk\AppData\Local\Temp\2\MSI81F5.tmp, Entrypoint: f9
InstallShield 16:24:40: Running InstallScript function f9
InstallShield 16:24:40: Using temp folder C:\Users\mrk\AppData\Local\Temp\2\{7E4542F8-3F81-4599-8B65-9F19797F3C06}
InstallShield 16:24:40: Installing engine...
InstallShield 16:24:40: Using product language 1033
InstallShield 16:24:40: Extracting support file setup.inx to C:\Users\mrk\AppData\Local\Temp\2\{7E4542F8-3F81-4599-8B65-9F19797F3C06}\setup.inx
InstallShield 16:24:40: Opening stream of file C:\Users\mrk\AppData\Local\Temp\2\MSI81F5.tmp
InstallShield 16:24:40: Extracting support file ISRT.dll to C:\Users\mrk\AppData\Local\Temp\2\{7E4542F8-3F81-4599-8B65-9F19797F3C06}\ISRT.dll
InstallShield 16:24:40: Extracting support file IsConfig.ini to C:\Users\mrk\AppData\Local\Temp\2\{7E4542F8-3F81-4599-8B65-9F19797F3C06}\IsConfig.ini
InstallShield 16:24:40: Extracting support file _isres1033.dll to C:\Users\mrk\AppData\Local\Temp\2\{7E4542F8-3F81-4599-8B65-9F19797F3C06}\_isres.dll
InstallShield 16:24:40: Extracting support file String1033.txt to C:\Users\mrk\AppData\Local\Temp\2\{7E4542F8-3F81-4599-8B65-9F19797F3C06}\String1033.txt
InstallShield 16:24:40: Skipping optional support file _isuser1033.dll
InstallShield 16:24:40: Detected X64 OS
InstallShield 16:24:40: Extracting support file ISBEWX64.exe to C:\Users\mrk\AppData\Local\Temp\2\{7E4542F8-3F81-4599-8B65-9F19797F3C06}\ISBEW64.exe
InstallShield 16:24:40: Setting script cmdline...
InstallShield 16:24:40: ProductCode is {3662EAA9-69C2-4026-BE7F-5EBB694A86DA}
InstallShield 16:24:40: Initializing Engine
MSI (c) (50!BC) [16:24:40:928]: PROPERTY CHANGE: Deleting ALLUSERS property. Its current value is '1'.
InstallShield 16:24:40: Script function f9 failure. Unknown Exception.
MSI (c) (50:E4) [16:24:41:038]: NOTE: custom action InitInstallDir unexpectedly closed the hInstall handle (type MSIHANDLE) provided to it. The custom action should be fixed to not close that handle.
Action ended 16:24:41: InitInstallDir. Return value 1.[/CODE]

What is going on? I have no clue where the "PROPERTY CHANGE: Deleting ALLUSERS property." is coming from. That is not from my Custom Actions.
Labels (1)
0 Kudos
(3) Replies
Christopher_Pai
Level 16

Do a search for Deleting ALLUSERS. Lot's of good hits including:

http://community.installshield.com/showthread.php?t=174396&highlight=Deleting+ALLUSERS
0 Kudos
MRKiscaden
Level 5

Looking at the logs on other platforms where the scripts are not failing, they also have the "Deleting ALLUSERS" line. I am more concerned about the error "Script function f9 failure. Unknown Exception." since it is preventing my installer from functioning at all. Any insights for this one?
0 Kudos
MRKiscaden
Level 5

One more detail: I have the same Problem on Windows Vista x64.

Perhaps my install script engine is no-good?
0 Kudos