PDA

View Full Version : CustomAction ISPowerShellStartup returned actual error code 1603



ShaneJennings
01-07-2015, 04:35 AM
Hi,
I am creating a basic MSI project however I cannot get my installer to work. Whenever I start the installer it tells me that the installer was interrupted and cannot continue. After looking at the MSI log I found that the problem seems to be the custom action "ISPowershellStartup". The log says:


InstallShield 16:25:49: Beginning ISPowerShellStartup...
InstallShield 16:25:49: Cannot create a file when that file already exists.

CustomAction ISPowerShellStartup returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 16:25:49: ISPowerShellStartup. Return value 3.


I also cannot open the MsiLog from the installer, as I get the error "Directory Manager not initialised".
Looking at the log it says:


Action 16:26:02: ShowMsiLog.
Action start 16:26:02: ShowMsiLog.
MSI (c) (E0:04) [16:26:02:809]: Note: 1: 2732 2: 0
Error 2732. Directory Manager not initialized.
MSI (c) (E0:04) [16:26:04:193]: Product: ARA Setup2 -- Error 2732. Directory Manager not initialized.

Action ended 16:26:04: ShowMsiLog. Return value 3.
Info 2896. Executing action ShowMsiLog failed.
Action ended 16:26:04: SetupCompleteError. Return value 3.
Action ended 16:26:04: INSTALL. Return value 3.


I tried creating a powershell custom action, however I couldn't get the custom action to work so I deleted it, and then later on I got this error. I have tried removing pretty much everything (custom actions, components, features, etc.) with the hope of finding out what was causing the custom action to fail however even with an empty project I still get this error.

Can anyone shed some light on why this is happening and how to fix it/avoid it in the future?