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: SMS Server|
On <date> <time> PM component SMS_COMPONENT_STATUS_SUMMARIZER on computer <computer> reported: SMS Component Status Summarizer set the status of component "<component>" running on computer "<computer>" to Warning.
Possible cause: The component is experiencing a problem.
Solution: Diagnose and fix the problem by:
1. Examining the status messages that the component reports.
2. Correcting the problem.
3. Instructing SMS Component Status Summarizer to reset the counts of Error, Warning, and/or Informational status messages reported by the component. To reset the counts, right-click Reset Counts on the component in the Component Status summary in the SMS Administrator console. When the counts are reset, SMS Component Status Summarizer will change the status of the component to OK. This might take some time if site <site> is a child site.
4. Delete any unwanted status messages from the SMS site database, if necessary.
5. Monitor the component occasionally to verify that the problem does not reoccur.
Possible cause: The component is OK and you were unnecessarily alerted because the component status thresholds are set too low for the component.
Solution: Increase the component status thresholds for the component using the Thresholds tab of the Component Status Summarizer Properties dialog box in the SMS Administrator console.
Possible cause: The component is flooding the status system by rapidly reporting the same message repeatedly.
Solution: Diagnose and control the flood of status messages by:
1. Verifying that the component is actually flooding the status system. View the status messages reported by the component and verify that the same message is continually reported every several minutes or seconds.
2. Noting the message ID of the flooded status message.
3. Creating a status filter rule for site <site> that instructs Status Manager to discard the flooded status message when component <component> on computer <computer> reports it. (See the Status information in the SMS 2.0 Administrator's Guide for an example.)
4. Verifying that your sites' databases were not filled up by the flooded status message. Delete any duplicate status messages from the site database, if necessary.
5. Refer to the Microsoft Knowledge Base for further troubleshooting information.
|English: Request a translation of the event description in plain English.|
No information available. If you have additional details about this event, please, send them to us!
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated