Event ID 7011 Source Service Control Manager
| Event ID | 7011 |
| Source | Service Control Manager |
| Type | Error |
| Description | Timeout (<number> milliseconds) waiting for transaction response from the <service name> service. |
| English, please! | This information is only available to subscribers. An example of English, please! |
| Concepts to understand |
What is a service? What is the role of the Service Control Manager? |
| Comments |
Adrian Grigorof
As per Microsoft: "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. To determine why the service is unresponsive, do the following: - Verify that the service is configured correctly. - Verify that the system is in a healthy state, for example, it is not running low on resources" As per M311517, this event can show up when the Inetinfo.exe process may stop responding due to a conflict with Exchange 2000. A stack overflow in the Mailmsg.dll file might be the reason that the Inetinfo.exe process stops responding and that you may receive event ID messages that point to problems with disks or controllers. M179265 points to a potential conflict between Exchange and ARCserve, the solution being to stop manually ARCServe before shutting down Exchange. M238665 indicates that this may occur when changes made to the application, directory, virtual directory, or site are interrupted while they are being written to the metabase. This can, in certain condition, corrupt the metabase. Services: AudioSrv and ShellHWDetection. This can occur on Windows XP because the -pnp parameter was used when the Sysprep utility was run on the master computer. See M811428. Mihai Andrei - Service: BTSSvc$BizTalkServerApplication - See M942221 for a hotfix applicable to Microsoft BizTalk Server 2006. - Service: MSExchangeIS - See M938673 for a hotfix applicable to Microsoft Exchange Server 2003. - Service: cisvc - From a newsgroup post: "Try turning off index server cisvc (catalog index service)". - Service: SMTPSVC - See M906557. - Service: W3SVC - See M906557. - Service: IISADMIN - See M906557. - Service: IMAP4Svc - See M906557. - Service: NntpSvc - See M906557. - Service: RESvc - See M906557. See M922918 and "JSI Tip 6203" for additional information about this event. Chris Hill - Service: Messenger - If the Messenger service is enabled under XP SP2 on a laptop with a wireless card, and the laptop goes into Suspend/Standby/Hibernate, the service may hang on resume. This may also cause other services hosted by svchost.exe to hang, so that the computer stops responding to requests to shut down or perform other commands. This seems to be a problem especially if there is another network connection on the system at the same time (e.g. disconnected network port on a laptop). I have found this problem on multiple laptop models with multiple wireless cards. The only solution I could find that solved the problem 100% of the time was to disable the Messenger service. You may also find that disabling all other network connections (inside Windows) and then rebooting, helps. This second solution may lead to the Messenger service crashing (with service-specific error 2270) rather than hanging on resume - but at least the computer remains responsive. Bernardo van Hoof - Service: stisvc - From a newsgroup: “Stisvc.exe is an executable which is installed by Windows together with digital cameras, scanners or other graphical input devices. Hardware device drivers use this service and it should not be terminated whilst these devices are used”. In our case, we have a HP 6110 All-In-One installed. The error appeared when a cartridge alignment error occurred on the device and we turned it off and then on again. Matthew C. Miller - Service: NtFrs - From a newsgroup post: "I stopped the errors by changing the autodisconnect value for the LAN setting under the registry key HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters. I set my Autodisconnect value to 0xfffff. See M138365 for an article describing the Autodisconnect parameter". The value 0xfffff is the highest value allowed on a domain controller. In my case, I used 0xfff. The default value on my SBS 2003 server was 0xf. Why bother deciphering Event logs when GFI EventsManager can do everything for you? Free trial here! Matt Wehnes - Service: VxSvc - In my case, the error was caused by Dell's Open Manage Disk Management. Stopping and restarting the "Disk Management Service" fixed the error. You have to forcefully kill the vxsvc.exe process, if the service doesn't stop. Anonymous - Service: Spooler - I had to delete some old spool jobs in the folder: C:\WINNT\System32\Spool\PRINTERS\*.SHD and *.SPL (for Windows 2000). After I deleted those old jobs, I was able to start the spooler service without this error in the event log. Ionut Marin - Service: InoRT – From a newsgroup post: "Looks like a problem with InoculateIT antivirus. InoRT is the real-time scanner component. You should try to reinstall it, this may fix the problem. Or you can download the most recent real time driver for your version and give that a "whirl" (reboot required)". - Service: Information Store - See M329817. - Service: SMTPSVC - See M831572. - Service: RESvc - See M831572. - Service: IISADMIN - See M831572. - Service: W3SVC - See M831572. - Service: MSExchangeIS - See M835437. - Service: McShield - Read McAfee Solution ID kb44876. Go to the McAfee Knowledge Search page and search for this solution to read it. This event appears if a service does not respond to a control request (such as pause, continue, interrogate, or stop) from Service Control Manager within the specified time. See MSW2KDB for more details on this event. Anonymous - Service: VxSvc - I typed from the command prompt: C:\diskperf -y <enter> and rebooted the server. This solved my problem. Kamil Niklasinski Service: IISADMIN - My suggestions: - possible IIS metadatabase corruption: M238665. Other related to MS Exchange 2K: M311517 (Inetinfo.exe stops responding), You might need manaually Remove and Reinstall IIS and Exchange: M320202 - possible third-party software (e.g. AntiVir). Anonymous Service: Naimagent32 - no info. Service: dmserver - no info. Service: NtmsSvc - no info. Service: HidServ - no info. Service: TermService - no info. Service: LcAgent - no info. Service: Spooler - I had to stop the printer spooler service in order to get rid of this error (obviously not a fix, but if you do not need to print from that machine it should be ok). Tom Rockefeller The MOM Onepoint service was crashing on an Exchange server. It turns out that Outlook XP was once installed on this machine. Installing Outlook 2000 resolved the problem. Adrian Florin Moisei Service: DNSCache - From a newsgroup post: "I had the same problem. It was an application that I installed called "Spybot - Search & Destroy". It modifies the %root%/winnt/system32/drivers/ etc/hosts file by adding a few hundred entries all pointing to 127.0.0.1 which is the local host. By deleting the hosts file and renaming the backup hosts file back to its original name, the problem was fixed." From a newsgroup post: "Indeed, there are issues with “hosts” files that have 1000 entries. I removed Search and Destroy and renamed the “hosts” file and achieved similar results. I have had many DNS timeouts, I thought that by removing Ares 1.8.1 build 2922 I had fixed the problem, but the problem came back with Kazaar. Whatever I have installed, it seems to knock out my route to my DNS server (ADSL router) which is behind my Linksys WAP. Every 60 seconds my network loses the ability to connect beyond the Linksys router for exactly 60 seconds. Normal service then returns. Something is locking up the DNS cache/database. Disabling Zone Alarm didn’t help. Removing Ares helped until I installed Kazaar. Removing kazaar has got rid of 90% of occurrences". Service: Netman - From a newsgroup post: "I disabled Zone Alarm and the problem was solved." Austin Tovey On our server it was caused by having the "Microsoft Exchange Event" service set to manual. Why bother deciphering Event logs when GFI EventsManager can do everything for you? Free trial here! |
| Links | M138365, M179265, M238665, M311517, M320202, M329295, M329817, M811428, M814626, M831572, M835437, M906557, M922918, M938673, M942221, JSI Tip 6203, McAfee Knowledge Search, MSW2KDB |
| Search | Google Web - Microsoft Support - Bing - EventID.Net Queue - More links... |
| Custom search | The custom search information is available to subscribers only. |
| Feedback | Send comments - Notify me when updated |
| Print version |