custom action won't fire up

[Olaf S]

Hi,

I have a package that needs to launch an exe from the installation target folder after installation. The exe registers some program modules and such and snapshoting the registry by a "repackaging project" was not successful for some reason. So I decided to use a custom action instead, firing it up after the installation installed the files:

I've chosen:

• deferred action (since it modifies the system)
• run under the local system account (no impersonation) to avoid problems with UAC

and I want it to execute when (install AND first time install) condition is met.

I moved it right before the "finish execution" stage so I'm very convinced that the exe is really there and ready to be launched.

However, the beast obviously doesn't launch, the log says:

Code: Select all

MSI (s) (E4:C4) [17:27:43:095]: Doing action: vfpalert.exe
Aktion beendet um 17:27:43: PublishProduct. return code 1.
MSI (s) (E4:C4) [17:27:43:095]: Doing action: InstallExecute
Aktion gestartet um 17:27:43: vfpalert.exe.
Aktion gestartet um 17:27:43: InstallExecute.
MSI (s) (E4:C4) [17:27:43:095]: Running Script: C:\Windows\Installer\MSI2657.tmp
MSI (s) (E4:C4) [17:27:43:095]: PROPERTY CHANGE: Adding UpdateStarted property. Its value is '1'.
MSI (s) (E4:C4) [17:27:43:126]: Machine policy value 'DisableRollback' is 0
MSI (s) (E4:C4) [17:27:43:126]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 
MSI (s) (E4:C4) [17:27:43:126]: Executing op: Header(Signature=1397708873,Version=500,Timestamp=1164348276,LangId=1031,Platform=0,ScriptType=1,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)
Aktion beendet um 17:27:43: vfpalert.exe. return code 1631.

What can be the reason for this and how can that be solved? What if the exe doesn't return "0" when it runs successfully?

best regards
Olaf

[Daniel]

Hello Olaf,

Indeed, there may be the case that the EXE doesn't return a "0" return value when it runs successfully. Can you please uncheck the "Fail installation if custom action returns an error" execution option of the related custom action and see if this helps?

If this is of no help, then please send us the .AIP (project file) and a verbose log of the installation to support at advancedinstaller dot com so we can investigate them.

All the best,
Daniel