One of the 1053 wrong solutions to Windows services: Modify the allowed response time in the registry

Error: ' The service did not respond in a timely fashion ' (servicespipetimeout) when attempting when attempting to start, s Top or pause a serviceproblemwhen attempting to start, stop or pause a service, one of the following error messages is ENC Ountered:

• ' Error 1053:the Service did not respond to the start or control request in a timely fashion. '
• ' Error 7000:the <ServiceName> failed to start due to the following Error:the service do not respond to the start or control request in a timely fashion. '
• ' Error 7009:timeout (30000 milliseconds) waiting for the <ServiceName> service to connect. '

Environment

• Microsoft Server 2003 32/64 bit
• Microsoft Server 32/64 bit
• Microsoft Server R2
• Windows XP 32/64 bit
• Windows Vista 32/64 bit
• Windows 7 32/64 bit

Solutionimportant:incorrect use of the Microsoft Windows Registry Editor could cause serious problems with your computer, u P to and including general operating system corruption and inability to boot. Registry editing should only being performed by those who is sufficiently experienced in the use of the Registry editor APPL Ication.

1. Go to Start > Run > and type regedit
2. Navigate To:hkey_local_machine\system\currentcontrolset\control
3. With the control folder selected, right-click in the pane to the right and select new DWORD Value
4. Name the new Dword:servicespipetimeout
5. Right-click ServicesPipeTimeout, and then click Modify
6. Click Decimal, type ' 180000 ', and then click OK
7. Restart the computer

Causethe Microsoft Windows Service Control Manager controls the state (i.e., started, stopped, paused, etc.) of all instal LED Windows Services. By default, the service Control Manager would wait 30,000 milliseconds (seconds) for a Service to respond. However, certain configurations, technical restrictions, or performance issues may result in the service taking longer tha   n seconds to start and report ready to the Service Control Manager. By editing or creating the ServicesPipeTimeout DWORD value, the Service Control Manager-Timeout period can be overridden,  Thereby giving the service more time-to-start up and on the the service. http://www.gfi.com/support/products/gfi-archiver/ Error-the-service-did-not-respond-in-a-timely-fashion-servicespipetimeout-when-attempting-when-attempting-to-start-stop-o R-pause-a-service

One of the 1053 wrong solutions to Windows services: Modify the allowed response time in the registry