Monitor unlimited number of servers
Filter log events
Create email and web-based reports

Direct access to Microsoft articles
Customized keywords for major search engines
Access to premium content

Event ID: 7009 Source: ServiceControlManager

Timeout (<value> milliseconds) waiting for the <service name> service to connect.
- Service: Rational Cred Manager - Increased the time-out period for the Service Control Manager by adding registry DWORD key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ServicesPipeTimeout and setting to 60000 milliseconds (instead of the default 30000). This was occurring on Windows XP VMware VDI machines. See ME824344 for assistance.
- Service: Microsoft Exchange Transport Log Search - See ME944752.
- Service: Office Communications Server Access Edge - See ME941724.
- Service: Microsoft Exchange Information Store - See ME926204.
- Service: SQL Server Agent (InstanceName) - See ME955801.
- Service: SQLSERVERAGENT - See ME948907.
- Service: COM+ System Application - See ME910383.
- Service: Symantec Client Firewall Accounts Manager - See the link to "Symantec Knowledge Base Document ID: 2003121714401248"
- Service: Microsoft Message Queue Service - See ME234372.
- Service: Microsoft ISA Server Control - See ME838857.
- Service: Microsoft ISA Server Storage - See ME884495.
- Service: Windows SharePoint Services Administration - The problem appeared after applying ME934525 (Cumulative Security Update for Windows SharePoint Services 3.0) on a server running Microsoft Office Project Server 2007. Project Web Access also stopped working after applying this fix.

To correct the problem follow these steps:

1. Run "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\bin\psconfig –cmd upgrade –inplace b2b –wait –force".
2. In registry editor add/modify the following values on "HKLM\System\CurrentControlSet\Control":
a) ServicesPipeTimeout   DWORD   60000  (decimal).
b) WaitToKillServiceTimeout changed to “120000”.
3. Reboot the server.
- Service: GhostStartService - In one case, this happened after a computer (that had Norton Ghost 2003 on it) was rebuilt from a Ghost image. This was fixed by removing the computer from the domain and then rejoining the domain.
- Service: Microsoft Exchange Management - See ME309511.
- Service: SharePoint Portal Server - See ME316267.
- Service: MSSQLSERVER - See ME306034.
- Service: Microsoft Exchange MTA Stacks - See ME325907.
- Service: Savroam - See "Symantec Support Document ID:2004080513005448".
- Service: VERITAS VSS Provider - See the link to "Veritas Support Document ID: 272751".

There are several Microsoft articles with information about this event: ME157913, ME170072, ME190697, ME217339, ME246762, ME262962, ME288952, ME315194 and ME317140.

See MSW2KDB for more details on this event.

- Service: MetaFrame COM Server - Try reducing your "%path%" system variable to below 256 characters and make sure that "%systemroot%\System32\Citrix\IMA" and "%systemroot%\System32\Citrix\IMA\SubSystems" are both in the path variable. There is also a possibility that running "DSMAINT /RECREATELHC" could fix it too.
This error is not directly generated by the application experiencing the problem but by the Service Control Manager that cannot connect to the service (due to problems with that application). Look for error messages generated by the application itself.

Windows Event Log Analysis Splunk App

Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to



Cisco ASA Log Analyzer Splunk App

Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.