Not able to stop Windows service

Posted on

Not able to stop Windows service – Managing your servers can streamline the performance of your team by allowing them to complete complex tasks faster. Plus, it can enable them to detect problems early on before they get out of hand and compromise your business. As a result, the risk of experiencing operational setbacks is drastically lower.

But the only way to make the most of your server management is to perform it correctly. And to help you do so, this article will share nine tips on improving your server management and fix some problem about windows, windows-server-2008, windows-server-2012-r2, service, .

All this while, I was able to successfully start and stop a windows service that I created, but all of a sudden for the last 1 week, I get the following error when I stop it:

Windows could not stop the Apache Tomcat service A on Local computer.Error 1053: The service did not respond to the start or control request in a timely fashion

This is happening on both Windows 2008 & Windows 2012. This happens only for Tomcat service A and not for Tomcat service B which runs on the same servers.

Any help is appreciated!

Solution :

This message simply means the service did not communicate with the Service Control Manager within the amount of time permitted in the registry.

You can try to increase the amount of time the service has to communicate with the service but that will require you to restart the computer.

You can modify the service timeout (HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlServicesPipeTimeout) to 80000 and restart the computer. That might solve the problem.

Leave a Reply

Your email address will not be published.