Several Service Control Manager Issues (Event ID's 7000, 7009, 7011)

https://answers.microsoft.com/en-us/windows/forum/windows_7-performance/several-service-control-manager-issues-event-ids/5eb047bb-e5bf-47b3-a661-299f6f9835ba

Were there any changes made to the computer prior to the issue?

 

Please follow the methods and check if it works fine.

 

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:

Important this section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

http://support.microsoft.com/kb/322756

How to back up and restore the registry in Windows

 

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

Computer\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.

 

https://corengen.wordpress.com/2009/12/18/the-limits-of-servicespipetimeout-and-servicebaserequestadditionaltime/

根据这个里面的说明，The MSDN documentation doesn’t mention this but it appears that the value specified in RequestAdditionalTime is not actually ‘additional’ time. Instead, it replaces the value in ServicesPipeTimeout. Worse still, any value greater than two minutes (120000 milliseconds) is ignored, i.e. capped at two minutes.

 

https://support.threattracksecurity.com/support/solutions/articles/1000071019-error-1053-the-service-did-not-respond-in-a-timely-fashion-when-attempting-to-start-stop-or-pause

Click Decimal, type '180000', and then click OK   这个里面设置了3分钟，不知道是否可以。

 

 

https://www.cnblogs.com/awpatp/archive/2013/02/19/2916929.html

这个链接里，提到另外一个配置(本地当前配置是5000)

• WaitToKillServiceTimeout SZ “120000” (string). Default值是12000.

 

 最后发现是因为自己的windows service的问题，内部有自己的判断逻辑。如果配置有问题，则直接中断。

 

 

错误提示

powershell中的提示

Start-Service : Service 'LISA_60_Dev_Batch (LISA_60_Dev_Batch)' cannot be started due to the following error: Cannot start service LISA_60_Dev_Batch on computer '.'.

event viewer中，查看windows logs下的system的log

 

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

 

 A timeout was reached (60000 milliseconds) while waiting for the LISA_60_Dev_Batch service to connect.

 

作者:Chuck Lu    GitHub