Hi,
I appologize in advanced if I sound a little frustrated. I've been at this for quite a number of days on end.
I noticed that the statement Control Service isn't able to control a service outside of the apply install/uninstall time frame. Any solutions to this? i.e. Starting a service after configurations of the install are complete? And not immediately after the files and services are made? Another feature request please?
Here's my situation: I have an installer that needs to install services, configure the services through modifying the configuration files, and then start the service. However, after installing the services (the moment Apply Install is called), the services start without proper configurations, which fails, and then causes the installation to fail.
Will I have to call the run command to start the services at the proper time like I have with everything else?
Thanks,
Kenneth
Controlling services outside install/uninstall time frame
-
KennethLee
- Posts: 16
- Joined: Wed Sep 16, 2009 4:00 pm
It seems the problem here is that the service interaction is occuring when you don't expected it because it is actually carried out by the MSI Exec. It sounds like what you need is some way of calling (something like) NET STOP and NET START command line commands in our boot stapper logic (which would allow it to execute seperately from the file install etc), and allow you to detect configuration etc.
Unfortunatly this is not present in the current releases, however, you could implement it using batch files and / or the Run Program As script function (and passing in the relevant parameters).
Unfortunatly this is not present in the current releases, however, you could implement it using batch files and / or the Run Program As script function (and passing in the relevant parameters).
Andy Neillans
-
KennethLee
- Posts: 16
- Joined: Wed Sep 16, 2009 4:00 pm

