I have an issue with service control on one of my packages. Hope you can help me with it. I am using installshield and there is a service called 'Gateway' in the msi that I have created. When installing the msi via command line msiexec /i, the install succeeds and at the end it gives a prompt for the reboot. After a reboot, the service starts and the app functions properly. However, when installaing via group policy the msi tries to start the service during installation and it fails with error 1920. I have also noticed this error when I install via command line with REBOOT=ReallySuppress. Based on the install logs, it seems as if the msi doesn't try to start the service in the former case (where reboot is not suppressed), while it does in the latter and fails. How can I stop the msi from trying to start the service during installation? Here are my direct editor entries

ServiceInstall table:

ServiceInstall Name DisplayName ServiceType StartType Error
NewServiceInstall1 Gateway Gateway 16 2 1

So, it is set to Automatic and the startname password is empty (LocalSystem).

ServiceControl Table:

ServiceControl Name Event Wait
Gateway Gateway 163 0

Thanks in advance.
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
Just install the service as automatic but don't start it. It will start after the reboot automatically.
Answered 08/25/2009 by: turbokitty
Sixth Degree Black Belt

Please log in to comment
0
Yes, that is what I want to do. How do I modify the servicecontrol so that it doesn't try to start during installation? What would be the event id??
Thanks.
Answered 08/25/2009 by: rkm
Senior Yellow Belt

Please log in to comment
0
Under the component for the executable, browse to "advanced" > "Install NT services". Set it up as required.
The end. [:D]
Answered 08/25/2009 by: turbokitty
Sixth Degree Black Belt

Please log in to comment
0
Set the service control value to 160 (to cover the uninstall)

You already set it to SERVICE_AUTO_START in the service install table so the service should start after the reboot.

Regards,
Rob.
Answered 08/25/2009 by: MSIPackager
Third Degree Black Belt

Please log in to comment
0
turbokitty :-) and Rob, thanks for the suggestions. I have tried in that way and this time, when installed via policy, the install succeeds, which was good. But, when I restarted the machine, the service did not start automatically. When I try to start myself, it fails saying access denied.
The same package when installed via command line or as a simple double click of the msi, the service starts properly after reboot. What could be the difference when applying group policies??
Answered 08/25/2009 by: rkm
Senior Yellow Belt

Please log in to comment
0
What does this service do? Does it have a user interface?
Is it being installed as the local system account via GPO but your account when run from the command-line?

Also, is this for XP or Vista/W7?
Answered 08/25/2009 by: turbokitty
Sixth Degree Black Belt

Please log in to comment
0
It gets installed for LocalSystem account either via GPO or via cmd line. This is for XP and yes, it has a user interface.
Answered 08/25/2009 by: rkm
Senior Yellow Belt

Please log in to comment
0
There should be no difference deploying via GP.. do you have other apps installing in the same policy ok?

I'm assume you have the standard windows installer policies also set.. alwaysinstallelevated etc?
Answered 08/25/2009 by: MSIPackager
Third Degree Black Belt

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