PDA

View Full Version : Problem with triggering more than one Powershell CA



richard.hewett
09-21-2012, 01:35 AM
I have a simple MSI with 3 type 2097168 CA. Each is associated with the removal of a particular feature, such as:



REMOVE><"Feature1" OR (REMOVE="ALL" AND &Feature1=2)


Each Powershell script functions as designed when only one feature is being removed, but if I attempt to remove more than one feature in a single operation I get the following



MSI (s) (38:58) [07:29:04:166]: Doing action: PSRemoveFeature1
Action 07:29:04: PSRemoveFeature1.
Action start 07:29:04: PSRemoveFeature1.
MSI (s) (38:B0) [07:29:04:207]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI696D.tmp, Entrypoint: PS2
InstallShield 07:29:04: Beginning Run PowerShell...
InstallShield 07:29:06: Finished Run PowerShell
Action ended 07:29:06: PSRemoveFeature1. Return value 1.
MSI (s) (38:58) [07:29:07:063]: Doing action: PSRemoveFeature2
Action 07:29:07: PSRemoveFeature2.
Action start 07:29:07: PSRemoveFeature2.
MSI (s) (38:04) [07:29:07:103]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI74C4.tmp, Entrypoint: PS3
InstallShield 07:29:07: Beginning Run PowerShell...
InstallShield 07:29:07: Error 8 : \Local\Temp\PS_{203E5E67-E147-484E-81D8-00CB449CF45E}.ini Not Installed
CustomAction PSRemoveFeature2 returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 07:29:07: PSRemoveFeature2. Return value 3.


What am I doing wrong? Why can't REMOVE="ALL" trigger each Powershell script sequentially?

hidenori
09-28-2012, 11:18 AM
I have attached the InstallShield 2012 Spring hotfix for this issue to this post. In order to apply the fix, you need to copy PowerShellWrap.dll to C:\Program Files\InstallShield\2012Spring\redist\Language Independent\i386 folder. Note that it is an unofficial fix as it is not fully tested by our QA team. Therefore, I would strongly recommend that you make a backup copy of the original file before applying the fix. The work order #IOA-000074187 has been submitted to track this issue.