Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am noticing on my new 2008 server that the Automatic(delayed Start ) services arent starting at all, even the default wndows ones, any ideas?

share|improve this question
That is strange. Have you checked your event log? If not, search for any events that may correlate to your services. – Joseph Kern Nov 10 '09 at 23:44
looks asif one of the automatic services is failing, woud cause all delayed seice to not start? – Brandon Grossutti Nov 11 '09 at 0:07
if so, that is a lil scary – Brandon Grossutti Nov 11 '09 at 0:08
well i set the servicethat was failing to manual and the delayed services started – Brandon Grossutti Nov 11 '09 at 0:19
up vote 0 down vote accepted

Well the answer seems to be if you have any services that ae set to auto and they fail that all services that are delayed will not start. IMO, that is a really bad idea and not really sure if that was the intended behaviour by MS, if nyone has any ideas on this or comments I wouldlove to hear them

share|improve this answer
You need to check the service dependencies. Did any other the other services that didn't start have this specific service as a dependency? – Izzy Nov 11 '09 at 2:14
the service that failed was one of my on custom services, which was why i was experimenting ith delayed start in the first place sice it had a binding to sockets issue, so rather than build a list of dependencies i decided t make it a delayed start, when it failed I saw other delayed service not start – Brandon Grossutti Nov 11 '09 at 18:02

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.