InstallShield 2016 not installing Service

Question

I am trying to configure and install a service in InstallShield 2016. I added the service using the component wizard. When I ran the installer, the Window Installer popup appeared on my screen with the different options that could be passed to the service. How do I passed these options to the service? I've tried creating the service using the component wizard and without the component wizard. In both case, it was the same outcome as described above. I have been unsuccessfully looking for explanation on how to do it.

Screenshots of the settings and popup window:

Answer 1

Finally I was able to get this to work. I am a novice to Installshield. This was my very first time using it.

1. Michael Urman comment was very helpful.

2. I've read the documentation on how to launch msi using msiexec.exe, and I am still confused. According to the documentation, deferred action must be between InstallInitialize and InstallFinalize and return processing should be synchronous(wait exit code). However, the system complained that there is another installation in progress, so it would not install the service.

3. In order to get around this, I set the working directory to [service] (the folder that contains my msi and exe files), I set the command line to msiexec.exe /i "[SERVICE]UserAgent.msi" /qn, I set returning processing to Asynchronous (no wait for completion), Install Exec Sequence to after schedule reboot, and add a condition to check for not installed.

4. With these options, I was able to silently installed the service. However, it will not uninstall when uninstalling the application. It has to be manually uninstall

Answer 2

For the records:

Check, if the file is marked as "key file". This was my fault.

Answer 3

That error dialog box is displayed when an msiexec command line is incorrect. It's not clear what you are doing, but you do not run an msiexec command on a service or any exe file. You build an MSI file then install it, and that MSI file will install the service. Even if you ARE running an msiexec command line on an MSI file you built, it is incorrect.