6 replies to this topic

[Artyom]

I have a problem to enable silent mode for an existing basic MSI project.
For silent mode I run: setup.exe /s /v"/qn"
Custom Actions that were in the UI sequence I've added also to execute sequence and added conditions on the UILevel (UILevel<>2 - in the UI sequence, UILevel=2 - in the execute).
While running in silent mode, Custom Actions that included only in execute sequence are not executed.
(Debugger showed that it terminates after last Custom Action of the above kind ends).
There are no problems running in normal mode.

I'm using InstallShield X - professional.

If anybody has an idea, please advice!

Thanks.

[Stefan Krueger]

Remove the UILevel conditions. Instead set the action scheduling option to "run only once".

[Artyom]

Having UILevel conditions removed and the action scheduling option set to "run only once" didn't help. Same result.

[Glytzhkof]

Where in the sequence did you add these custom actions? Immediate mode? Deferred mode? Before or after InstallInitialize or InstallFinalize?

[Artyom]

The custom actions that don't run in silent mode are located after InstallFinalize in the execution sequence.

[Glytzhkof]

That would explain it. You will need to move these custom actions before InstallFinalize. If you do so they should be run in deferred mode. It is also possible to insert the actions after InstallFinalize in the immediate sequence: but this is technically terrible and WILL cause problems at some point.

Please note that deferred mode custom actions may require that you write properties into the execution mode using the CustomActionData property. This process is described in the MSI SDK.

[Artyom]

InstallShield created 'ISSetupFilesCleanup' between InstallFinalize and my custom actions. Pushing it down to the end of the sequence solved the problem! Any way I'll try to move the custom actions before InstallFinalize.

Thank you all for your help!