Quantcast
Channel: Windows Server General Forum forum
Viewing all articles
Browse latest Browse all 24879

Service won't start. Error 1053 (timeout) comes up within 2 seconds, but timeout set for much longer

$
0
0

I have a set of services on a Windows Server 2012 R@ server that I created myself, but when I try to start the service I get the following message:

Error 1053: The service did not respond to the start or control request in a timely fashion.

In the System Event Log, I see the following Error event with Service Control Manager as the source and Event ID 7009:

A timeout was reached (30000 milliseconds) while waiting for the <service name> service to connect.

The problem is that the error comes up within 2 seconds of when I try to start the service. I tried extending the timeout period to 240000 milliseconds in the Registry, but not only does the service still fail to start, but the Event Log entry reads the same.

I'm prepared to delete and re-create these services, but I'd like to know if there is a fix for this so I don't have to do that. Can someone please shed some light on this? Thank you in advance for any assistance you can provide.


Viewing all articles
Browse latest Browse all 24879

Trending Articles