up vote 1 down vote favorite
share [g+] share [fb]

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

link|improve this question
Is it the same service each time? If so, what is it? – Randolph West 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
1  
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). – Randolph West Oct 19 '11 at 0:16
feedback

Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

Your Answer

 
or
required, but never shown
discard

Browse other questions tagged or ask your own question.