I have packaged a small legacy install that distributes a few files including an executable(handheldinstall.exe). I would like to have the MSI launch the executable after installation is complete. I have added a custom action and install execute sequence:

CustomAction:
Action=CA_HandheldInstall
Type=3282
Source=handheldinstall.exe
Target=

InstallExecuteSequence:
Action=CA_HandheldInstall
Condition=
Sequence=6595

The InstallFinalize sequence is 6600. The exe never launches. Anyone know what might be wrong? I'm making these changes to the MSI in Orca.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Hi Joe,
this can't work like this, but you are on the right track.
Your CA type is: 3072 + 192 + 18 (TypeInScript-TypeNoImpersonate + Async-Continue + EXE).
This combination is not allowed, have a look at the logfile where this CA should run. A deferred CA must allways have a return code.
You need to run this type of CA at very end of the InstallExecuteSequence or if its not needed in silent mode, at the end of the InstallUISequence.

So, change the type to 210 and the sequence to 6800 and it will work.

Regards, Nick
Answered 05/08/2007 by: nheim
Tenth Degree Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity