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 www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
|Source: Microsoft Operations Manager|
The response <response> has been running more than <value> seconds and exceeded the time allowed to run. This might indicate the response is engaged in an infinite loop or is hanging.
|English: Request a translation of the event description in plain English.|
This problem occurs under heavy load conditions or when the network connection is unavailable. See ME900333 and ME906858 for two hotfixes applicable to Microsoft Operations Manager (MOM) 2005.
See ME938911 for a hotfix applicable to Microsoft SQL Server 2005.
See ME904747 and ME917665 for additional information about this event.
- Response: "script: AD Topology Discovery" - From a newsgroup post: "In environments where there is a large AD infrastructure or many DCs, this script may not complete in a timely manner. Check the Script frequency setting in the rule. Right click on Rule Groups in the Admin Console and search for all rules that run the script AD Topology Discovery. Open the rule properties and under the DataProvider tab, you can notice the "Provider name" indicates that it is scheduled for every 30 minutes. Choose the Modify button and raise it to 90 minutes and the problem will go away".
|Private comment: Subscribers only. See example of private comment|
|Links: ME900333, ME904747, ME906858, ME917665, ME938911|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated