Hello, I have come accross a problem where the AI_SetLogOnAsService custom action causes silent installations to fail.
The scenario:
We have an installation package with multiple builds.
Some of these builds install a service and possibly override the service account under which the service will run. These builds work as expected.
Other builds do not install the service at all.
These builds work when executed with the UI but fail when /qn is specified.
I tracked the issue to the AI_SetLogOnAsService custom action which for some reason is not filtered out of the InstallExecuteSequence for builds that do not contain the service.
I have sworked around this issue for now by specifying a condition, in the table editor, that will never be true for those builds that do not install the service.
Just thought you might like to know.