Unable to start a service on a Windows server.

Timeout error or unable to start a service on a Windows server

While starting a computer running Windows server, if a service does not start or shows one of the following error messages,
  • The service did not respond to the start or control request in a timely fashion (Error: 1053/Event ID: 7000)
  • Timeout (30000 milliseconds) waiting for a transaction response from the ServiceName service (Event ID: 7011)
  • A timeout was reached (30000 milliseconds) while waiting for the ServiceName service to connect (Event ID: 7009)
Please make sure the below steps are followed with the help of sys admin:
  1. Go to Start > Click Run  > Type regedit > click OK
  2. Locate and click on the following registry subkey "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control"

  3. In the right pane, check for  ServicesPipeTimeout entry
Note : If the ServicesPipeTimeout entry does not exist, you have to create it. 

Kindly follow the below steps to create a new entry called ServicesPipeTimeout:
  1. Go to Edit  > New >  DWORD Value

  2. Name the entry as ServicesPipeTimeout

  3. Right-click ServicesPipeTimeout, and click Modify
  4. Choose the base type as Decimal
  5. Under Value Data , enter 60000

  6. Click OK
This value represents the time in milliseconds before a service times out. Restart the computer

    • Related Articles

    • How to uninstall the Site24x7 Windows Server Monitoring Agent

      Method 1: To uninstall the Site24x7 Windows Server Monitoring Agent, click the link below: https://staticdownloads.site24x7.com/server/Site24x7WindowsAgentUninstall.zip Unzip and execute the Uninstall.bat file in the Command Prompt as an ...

    • No data for service and process in Windows server monitor

      If you see "No Data" for process and service metrics (such as CPU or memory usage of monitored services) in the Site24x7 Windows server monitor user interface, follow the troubleshooting steps below. Run PowerShell Commands Open PowerShell as ...

    • Troubleshoot the Error 404 and Error 99 for RabbitMQ

      When installing the RabbitMQ plugin, you may encounter the following errors: HTTP Error 404: Not Found: This error usually occurs when Site24x7's RabbitMQ monitoring plugin attempts to access the /api/overview page of RabbitMQ, but the resource ...

    • Troubleshoot the Unauthorized user (Error 401) when installing Tomcat plugins

      When installing Tomcat plugins, you may encounter the following error: Unauthorized user. Does not have permissions. HTTP Error 401: This error usually occurs when the user accessing the Tomcat Manager application does not have the necessary ...

    • API exceeded error

      Why do I get an API exceeded error after a few attempts? Every API has a certain limit to the number of requests a user can hit within a period of time, called the rate limit. An error message is triggered when a user does one of the following ...