en[EVENT7009] Service Control Manager (SCM)

SC2 2018-07-27

2024-04-07

Atom | RSS

このサイトを検索 | Search this site

,Japan

to japanese

Thank you for accessing.

This article has been removed.

The content of this blog can be searched by keyword.

Use the search window in the sidebar or at the top. Alternatively, please translate the original article using Google or other means.

Please find alternative content.

Remnants of articles that had been published

This article is about Event ID 7009 recorded in the event log.

Result from the research,

We have found that this is due to the time it takes for the program registered in the service to start [default 30000 milliseconds].

This error is now recorded when you update to Windows10 version1803.

I understand the cause of the error and the repair method, so I will share it.

I'm glad if you can use it as a reference.

Event Log

The event log is reprinted.

Event Log
message	Timeout (30000 milliseconds) waiting for NetMsmqActivator service to connect.
log name	system
Source	Service Control Manager
Event ID	7009
level	error
user	N /A
Opcode	information

30000 ms

Reading Microsoft Docs,

The Service Control Manager monitors the time when the program registered in the service starts, and by default, records the event as an error when the program does not start within 30000 milliseconds (30 seconds).

Therefore,

You can prevent it from being recorded in the event log by changing the default value of Service Control Manager.

In particular,

Change the value of ServicesPipeTimeout set in the registry.

Steps to change ServicesPipeTimeout

Use Registry Editor to change the value of ServicesPipeTimeout to 60 seconds.

Registry operations are at your own risk

Before working with Registry Editor
Make a backup copy of your registry in case something goes wrong.

1. Start Registry Editor

Launch Run and enter name: regedit.

How to start Registry Editor: Scrap 2nd.

2. Find Control

\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control

3. Create a new ServicesPipeTimeout

Control: Right click> New> DWORD (32 bit) value> Name: ServicesPipeTimeout

ServicesPipeTimeout did not exist on my computer, so I created a new one and set the value to 60000 milliseconds (60 seconds).

4. Settings value of ServicesPipeTimeout


Value name	ServicesPipeTimeout
Value data	60000
Notation	Decimal number

5. End of procedure

The procedure ends when you exit Registry Editor and restart your computer.

Summary

Once the event log for Service Control Manager is logged, let's check the default timeout value.

And

Since it only records in the event log that the service did not start within the monitoring time (default value) of SCM, it is not necessary to change the default value because it is not a fatal error.

Overview of SCM

The results of examining the functions of Service Control Manager (SCM, Service Control Manager) are as follows.

Launched at system boot
A remote procedure call (RPC) server that allows service configurations and service control programs to manipulate services on remote machines
Send control requests to running and driver services
Manage status information about services and report configuration changes and state changes

Since SCM is monitoring the Windows service, if it is recorded as "Source: Service Control Manager" like [Event ID7009] recorded this time, it is the shortest way to repair it if you suspect an error related to the Windows service. I thought it was a distance.

The explanation about SCM on the official Microsoft website is reproduced.

Google Translate
The Service Control Manager (SCM) starts at system boot. This is a remote procedure call (RPC) server, so service configuration and service control programs can interact with services on remote machines.

The service control manager (SCM) is started at system boot.It is a remote procedure call (RPC) server, so that service configuration and service control programs can manipulate services on remote machines.
Microsoft Docs

External link

Verification: Windows 10 Pro April 2018, 1803

：SC2