| Event Id | 7009 |
| Source | Service Control Manager |
| Description | Description1: Timeout (%1 milliseconds) waiting for the %2 service to connect. Description 2: The Certificate Authority 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 Information | According to Microsoft : Cause : This event is logged when a service does not respond within the defined timeout period (the default timeout period is 30000 milliseconds). Resolution : Increase the service timeout period Note: To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority. To change the service timeout period: 1.Click theStart button, then clickRun, typeregedit, and clickOK. 2.In theRegistry Editor, click the registry subkey HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control. 3.In the details pane, locate theServicesPipeTimeout entry, right-click that entry and then selectModify. Note: If theServicesPipeTimeout entry does not exist, you must create it by selectingNew on theEdit menu, followed by theDWORD Value, then typing ServicesPipeTimeout, and clickingEnter. 4.ClickDecimal, enter the new timeout value in milliseconds, and then clickOK. 5.Restart the computer. Verify : To perform this procedure, you must have membership inAdministrators, or you must have been delegated the appropriate authority. To verify the state in which a service is operating: 1.Click theStart button, Run, then typecmd to open a command prompt. 2.Typesc interrogate service_name (where service_name is the name of the service) at the command prompt to update the status of that service in Service Control Manager. 3.Typesc qc service_name at the command prompt to display the configuration status of the service. 4.Typesc queryex service_name at the command prompt to display the extended status of the service. This command will provide the following information about a service: SERVICE_NAME (the service's registry subkey name), TYPE (the type of service, for example, shared process, interactive), STATE (for example, running, paused, and the states that are not available), WIN32_EXIT_CODE (the Windows exit error code), SERVICE_EXIT_CODE (the service exit code), CHECKPOINT, WAIT_HINT (the time period the SCM waits before reporting a service failure), PID (ID of the process running the service), and FLAGS. If the service was started successfully, the WIN32_EXIT_CODE field should contain a zero (0). If the service failed to start when an attempt was made, this field should contain an exit code provided by the service when it could not start. 4.Typenet helpmsg exit_code (where exit_code is the 4 digit number of the error code) at the command prompt to display the meaning of the exit code. ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Cause 1: Within a specified time period after a new service starts, it notifies Service Control Manager (SCM) that it is ready to connect. In this case, the service did not notify SCM within the time period. The service might be stuck in a loop or waiting on a system resource, such as additional memory. Resolution : To determine why the service is not connecting, do the following: 1)Verify that the service is configured correctly. 2)Verify that the system is in a healthy state, for example, it is not running low on resources. ------------------------------------------------------------------------------------------ Cause2: This is caused by a User DSN being created in the 32-Bit ODBC applet in Control Panel for the Certificate Servers Access Database. This DSN needs to be created as a System DSN. Resolution: To work around this problem, run the following registry script to create the "CertSrv" ODBC data source.Please note that the path specified in the "Driver" and "DBQ" entries must be adjusted according to the actual configuration. If simply creating the System DSN does not resolve the issue, then try the following steps: 1. In the ODBC Data Source Administrator, make sure that there is a System DSN for Certificate Server, and that there is not a User DSN. If a User DSN exists, delete it. 2. In the Certificate Server Service Configuration found in Services under Control Panel, check to see if the service is running under the context of the System Account. If it is, try selecting Allow Service to Interact with Desktop. 3. Also in the Certificate Server Service Configuration, change the account to an account that has local administrative rights. 4. In the ODBC Data Source Administrator on the System DSN tab, highlight the Certificate Server DSN and choose Configure. Select Repair the Database. The database name is Certsrv.mdb, and by default it is located in %winnt%\system32\certlog. Cause 3: The Address.dll file located in the Exchsrvr\Bin folder was not replaced during the upgrade. Resolution: To resolve this problem, 1. Rename the Address.dll file and copy the original Address.dll file from the Server\Setup\I386\Bin folder on the Exchange Server 5.5 CD to the Exchsrvr\Bin folder on the server. 2. Start the MTA service. Cause 4: The Proxy Server Setup program deletes the Mspclnt.ini file in the Proxy Servers Client folder when the Proxy Server documentation is either installed or removed. This missing Mspclnt.ini file causes the proxy services to fail starting. |
| Reference Links | Event ID 7009 from Source Service Control Manager Certificate Server Fails to Start with Event ID 7000 or 7009 Error Starting the MTA After Upgrading to Exchange 5.5 from Exchange 4.0 Certificate Server Fails to Start with Event ID 7000 or 7009 Event ID 3870, 7023, 2504 and 7002 messages are logged when you restart your Windows NT 4.0 server MSMQ Service Fails to Start Automatically on Restart Proxy Services Start to Fail When Documentation Is Installed or Removed Host Security Update Renames SNAREG.DLL XADM: Error 2186 Occurs When You Start the Microsoft Exchange Information Store Service |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.