Windows Service Recovery Tab

[Manan]

Hi,

If you check the properties for any service in services mmc (start -->
control panel --> administrative tools --> services) there is a tab
called "Recovery" where one can specify the action needs to be taken
in case of service fails.

This recovery option works very well if service is up and running and
it has failed due to some reason. But think about the scenario where
machine is re-booted and as service is set to automatic it will try to
start but it is not able to start (may be because of network glitch or
what ever reason) and it never tries to start the service again
(though i have specified the recovery options).

Can someone confirm me whether this recovery option works only if
service is already running or it should work for 1st startup as
well???
Is there any way we can configure the service in a way that it re-
tries to start even if its 1st attempt to start the service?

I’m asking this because i have a service which talks to remote
database and we encountered the issue when application machine was
rebooted and service tried to start it couldn't because it was not
able to talk to SQL server (network glitch) and sql server was
available within few minutes but service never re-tried and we have to
start it manually.

Any help on this will be much appreciated.

Thanks in advance.

Cheers,
Manan

 

[Marcin]

Manan - service recovery option apply only in the situations when the
service fails while in a state other than stopped...

hth
Marcin

Hi,

If you check the properties for any service in services mmc (start -->
control panel --> administrative tools --> services) there is a tab
called "Recovery" where one can specify the action needs to be taken
in case of service fails.

This recovery option works very well if service is up and running and
it has failed due to some reason. But think about the scenario where
machine is re-booted and as service is set to automatic it will try to
start but it is not able to start (may be because of network glitch or
what ever reason) and it never tries to start the service again
(though i have specified the recovery options).

Can someone confirm me whether this recovery option works only if
service is already running or it should work for 1st startup as
well???
Is there any way we can configure the service in a way that it re-
tries to start even if its 1st attempt to start the service?

I’m asking this because i have a service which talks to remote
database and we encountered the issue when application machine was
rebooted and service tried to start it couldn't because it was not
able to talk to SQL server (network glitch) and sql server was
available within few minutes but service never re-tried and we have to
start it manually.

Any help on this will be much appreciated.

Thanks in advance.

Cheers,
Manan

 

[Manan]

Manan - service recovery option apply only in the situations when the
service fails while in a state other than stopped...

hth
Marcin


Hi,

If you check the properties for any service in services mmc (start -->
control panel --> administrative tools --> services) there is a tab
called "Recovery" where one can specify the action needs to be taken
in case of service fails.

This recovery option works very well if service is up and running and
it has failed due to some reason. But think about the scenario where
machine is re-booted and as service is set to automatic it will try to
start but it is not able to start (may be because of network glitch or
what ever reason) and it never tries to start the service again
(though i have specified the recovery options).

Can someone confirm me whether this recovery option works only if
service is already running or it should work for 1st startup as
well???
Is there any way we can configure the service in a way that it re-
tries to start even if its 1st attempt to start the service?

I’m asking this because i have a service which talks to remote
database and we encountered the issue when application machine was
rebooted and service tried to start it couldn't because it was not
able to talk to SQL server (network glitch) and sql server was
available within few minutes but service never re-tried and we have to
start it manually.

Any help on this will be much appreciated.

Thanks in advance.

Cheers,
Manan

Thanks Marcin for confirming this.
But is there any way by which can configure service to recover from
failure (retry) even if it's 1st attemp to start the service after
reboot.

Cheers!

 

[Marcin]

Manan,
one possible workaround is to create a script that will check a status of
the target service and attempt to start it if it's not already running. This
can be scheduled following computer startup using Scheduled Tasks. For a
sample script, refer to
http://www.microsoft.com/technet/scriptcenter/scripts/default.mspx?mfr=tr

hth
Marcin

Manan - service recovery option apply only in the situations when the
service fails while in a state other than stopped...

hth
Marcin


Hi,

If you check the properties for any service in services mmc (start -->
control panel --> administrative tools --> services) there is a tab
called "Recovery" where one can specify the action needs to be taken
in case of service fails.

This recovery option works very well if service is up and running and
it has failed due to some reason. But think about the scenario where
machine is re-booted and as service is set to automatic it will try to
start but it is not able to start (may be because of network glitch or
what ever reason) and it never tries to start the service again
(though i have specified the recovery options).

Can someone confirm me whether this recovery option works only if
service is already running or it should work for 1st startup as
well???
Is there any way we can configure the service in a way that it re-
tries to start even if its 1st attempt to start the service?

I’m asking this because i have a service which talks to remote
database and we encountered the issue when application machine was
rebooted and service tried to start it couldn't because it was not
able to talk to SQL server (network glitch) and sql server was
available within few minutes but service never re-tried and we have to
start it manually.

Any help on this will be much appreciated.

Thanks in advance.

Cheers,
Manan

Thanks Marcin for confirming this.
But is there any way by which can configure service to recover from
failure (retry) even if it's 1st attemp to start the service after
reboot.

Cheers!

 

[CoreTech]

Yes, I can also confirm that the recovery will only kick in when there is an explicit failure, not on a normal stop, or when the initialization fails.

You may want to look at our utility called Service Protector, which will automatically restart your service whenever it fails and ensure that your service is available 24/7. It goes above and beyond the normal service recovery functionality and even allows you to plug in your own, custom failure detection logic.

Service Protector comes with a free 30-day trial so you can make sure it works well before you spend any $$.