asked on

Event 7011 Timeout Error Service Control Manager

On a Server 2008 R2, I get these timeout errors. Found hopeful solution on Microsoft website, as states below. The registry does not have the ServicesPipeTimeout Key. I know how to add the entry but the workaround does not say where to install the subkey or what to name it? Would anybody know ... thx....

When you start a computer that is running Windows Server 2003, Windows Server 2008, or Windows Server 2008 R2, a service does not start, and the following error events appear in the Application log:

The ServiceName service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
Event 2

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7011

Description:
Timeout (30000 milliseconds) waiting for a transaction response from the ServiceName service.
Event 3

Event Type: Error
Source: Service Control Manager
Event ID: 7009
Task Category: None

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

To work around this problem, modify the registry to increase the default time-out value for the service control manager. To increase this value to 60 seconds, follow these steps: 1.Click Start, click Run, type regedit, and then click OK.
2.Locate and then click the following registry subkey:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control

3. In the right pane, locate the ServicesPipeTimeout entry.

Note If the ServicesPipeTimeout entry does not exist, you must create it. To do this, follow these steps: a. On the Edit menu, point to New, and then click DWORD Value.
b. Type ServicesPipeTimeout, and then press ENTER.

4. Right-click ServicesPipeTimeout, and then click Modify.
5. Click Decimal, type 60000, and then click OK.

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

Note This workaround may resolve the problem where the service does not start. However, we recommend that you research this problem to determine whether it is a symptom of another problem.

Randy Downs

Try this.

Method 1: If it is recent problem try to perform a system restore and check.
http://windows.microsoft.com/en-us/windows7/What-is-System-Restore

Method 2: Verify these services are started, in order:
DCOM Server Process Launcher
RPC Endpoint Mapper
Remote Procedure Call (RPC)
Security Accounts Manager
Server
If they are not started, start them and check. Follow the steps below:
a) Click Start, type “services” on the start search box and press enter.
b) Scroll down and check for the above mentioned services.
c) Double click each of the services and start them if they are not started.

Method 3:

a) Click Start, click Run, type regedit, and then click OK.
b) Locate and then click the following registry subkey:

c) HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control

d) In the right pane, locate the ServicesPipeTimeout entry.

Note If the ServicesPipeTimeout entry does not exist, you must create it. To do this, follow these steps:
a) On the Edit menu, point to New, and then click DWORD Value.
b) Type ServicesPipeTimeout, and then press ENTER.

c) Right-click ServicesPipeTimeout, and then click Modify.
d) Click decimal, type 60000, and then click OK.

xav1963

ASKER

Yes... I had read that ... For Method 3, where do I create the subkey and what do I name it? I assume I place the subkey in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control? Do I name it ServicesPipeTimeout? Then inside of it create the entry ServicesPipeTimeout?

Is that correct?

ASKER CERTIFIED SOLUTION

Randy Downs

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

xav1963

ASKER

thx....