If the service stops "gracefully" (e.g. with a 0 exit code) then the Service Control Manager isn't going to restart the service - it's the equivalent of you manually stopping the service, or the service stopping itself.
Additionally you can only configure a certain amount of retries - so if the service is actually crashing (or invoking DEP or similar), then it might just do that over and over again until SCM gives up (but IIRC that logs an event to the event log) Cheers Ken From: Bob Fronk [mailto:b...@btrfronk.com] Sent: Tuesday, 11 August 2009 10:00 PM To: NT System Admin Issues Subject: Service recovery tab (Windows 2003 server R2) I have a 3rd party service that regularly stops. (unresolved issue from software). I have it set in the recovery tab to restart service. However, it never seems to restart without manually opening services.msc and clicking "start". It does start at reboot, so the settings in the recovery tab should cause it to start, but they don't. My question is this: has anyone seen the recovery tab actually recover a service that has stopped? What should the "reset fail count after - days" setting be? I have mine set at 0. -- Bob Fronk P Please print only as needed. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
