| Event Id | 7011 |
| Source | Service Control Manager |
| Description | Timeout (%1 milliseconds) waiting for a transaction response from the %2 service. |
| 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 inAdministrators, or you must have been delegated the appropriate authority. Caution: Incorrectly editing the registry may severely damage your system. Before making changes to the registry, you should back up any valued data. 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. 4.ClickDecimal, enter the new timeout value in milliseconds, and then click OK. 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.Type sc 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. 5.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: The specified service did not respond to a control request (such as pause, continue, interrogate, or stop) from Service Control Manager within the specified time. 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 unresponsive, 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. --------------------------------------------------------------------------------- This event will be logged whenever a service trapped in to a loop and not able to respond to service control managers control request. This service may hung due to resource not available properly or some other particular reason.Following MS article will give more information about this event. According to News Group "Event 7011, Description:"Timeout (30000 milliseconds) waiting for a transaction response from the MSExchangeIS service. Data:" This can happen if any SMTP sink, either from Microsoft of third party is acting weird. What third party software, such as Anti-virus, Anti-spam do have installed on the machine? Try uninstalling them and see if that fixes the problem. A lot of software, both from MS and third party, run in IISs (inetinfo.exe) memory space. Although this is very efficient mechanism as far as response time goes, it creates a big dependency tree. If any one of this dependent corrupts the memory, it brings down all other services along with it. Following software run in inetinfo.exe IIS Admin Most of Exchange services SMTP NNTP FTP Any Anti-Virus, Anti-Spam written as Sink" |
| Reference Links | Event ID 7011 from Source Service Control Manager Event ID 7011 Messages and Computer Stops Responding After You Install Windows XP by Using the Sysprep Utility The SMTP service on your Exchange 2000 Server computer may stop responding The Information Store service repeatedly stops responding and event ID 467 is logged MOM Server Is Unstable After You Install Office XP Errors Occur After Creating or Modifying Application, Directory, or Site The Inetinfo.exe Process Stops Responding You may receive an "Access violation c0000005" error message and event ID 7031 and 7011 messages on an Exchange 2000 computer |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.