Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

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'm trying to start a Windows service by right-clicking on it in Services and choosing Start.

Immediately (less than a second) a dialog comes up with error 1053. Odd because I thought services were given 30 seconds to start.

In the event log, I get two entries, first saying the 30,000 ms timeout was reached, and the second about the service no responding in a timely fashion.

I don't find any other relevant event log entries. Are there any ways to track down why the service doesn't start?

Thanks, Mike

share|improve this question
Is it the same service each time? If so, what is it? – user3914 Oct 14 '11 at 19:17
Yes, it's the same service each time. The service was purchased from a third party, it's not a normal Windows one. – Mike Hildner Oct 18 '11 at 15:06
FWIW, uninstalling .NET 4.0 fixed this issue, the service does use CLR 2. Still wondering if there's any tools/logs to track down the root cause. – Mike Hildner Oct 18 '11 at 18:26
Glad to hear it's fixed. You could investigate the logs for .NET (I'm not at a Windows machine right now to tell you exactly where to look). – user3914 Oct 19 '11 at 0:16

Your Answer


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

Browse other questions tagged or ask your own question.