sms server 4610 event id

[Leonard Verge]

Under site status (sms 2003) red error on my secondary site, component
services.

Error on event log on my primary sms system is .

Anyone ever see this?, not getting much hits on the internet.

any help appreciated.

Event Type: Information

Event Source: SMS Server

Event Category: SMS_COMPONENT_STATUS_SUMMARIZER

Event ID: 4610

Date: 7/22/2004

Time: 3:12:23 PM

User: N/A

Computer: LABSMS02

Description:

On 7/22/2004 3:06:47 PM, component SMS_COMPONENT_STATUS_SUMMARIZER on
computer LABSMS03 reported: SMS Component Status Summarizer set the status
of component "SMS_CLIENT_CONFIG_MANAGER" running on computer "LABSMS03" to
Warning.



Possible cause: The component is experiencing a problem.

Solution: Diagnose and fix the problem by:

1. Examine 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 "012" is a child site.

4. Deleting any unwanted status messages from the site database, if
necessary.

5. Monitor the component occasionally to verify 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 "012" that instructs Status
Manager to discard the flooded status message when component
"SMS_CLIENT_CONFIG_MANAGER" on computer "LABSMS03" reports it.

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.



For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

[Stan White [MS]]

Look for other error or status messages from the secondary site.
This message simply says that some other component has experienced errors
beyond the threshhold that causes concern, and now the site is 'worried' for
lack of a better word.
--
--
Stan [MSFT]
--
--
This posting is provided "AS IS" with no warranties, and confers no rights.
--
--

Post by Leonard Verge
Under site status (sms 2003) red error on my secondary site, component
services.
Error on event log on my primary sms system is .
Anyone ever see this?, not getting much hits on the internet.
any help appreciated.
Event Type: Information
Event Source: SMS Server
Event Category: SMS_COMPONENT_STATUS_SUMMARIZER
Event ID: 4610
Date: 7/22/2004
Time: 3:12:23 PM
User: N/A
Computer: LABSMS02
On 7/22/2004 3:06:47 PM, component SMS_COMPONENT_STATUS_SUMMARIZER on
computer LABSMS03 reported: SMS Component Status Summarizer set the status
of component "SMS_CLIENT_CONFIG_MANAGER" running on computer "LABSMS03" to
Warning.
Possible cause: The component is experiencing a problem.
1. Examine 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 "012" is a child site.
4. Deleting any unwanted status messages from the site database, if
necessary.
5. Monitor the component occasionally to verify 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.
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 "012" that instructs Status
Manager to discard the flooded status message when component
"SMS_CLIENT_CONFIG_MANAGER" on computer "LABSMS03" reports it.
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.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.