Table 26.42 SMS Component Summarizer (Message IDs 4600 to 4628)

Message ID	Severity	Message
4600	Informational	SMS Component Status Summarizer detected that the list of component status display intervals specified in the site control file has changed. SMS Component Status Summarizer will reconfigure itself to use the new set of display intervals.
4601	Warning	SMS Component Status Summarizer detected that entry %1 of the component thresholds property list in the site control file is corrupt. Possible cause: The site control file entry does not contain a component name. Solution: SMS Component Status Summarizer will ignore this entry, which might result in the Status column of the Component Status display in the SMS Administrator console being improperly set for a particular component. This problem might be the result of a code defect. If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.
4602	Informational	SMS Component Status Summarizer received a status message from component %1, running on computer %2, but there is no record of this component in the site control file. Possible cause: SMS Component Status Summarizer will now begin tracking the status of this component as if it were properly listed in the site control file. If this component is an SMS component, it could mean the component should have been deinstalled sometime in the past by Site Component Manager. Solution: Investigate whether or not the component should really be installed and running on this computer. If it should not be installed, the problem might be the result of defective code. If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.
4603	Informational	SMS Component Status Summarizer detected that component %1, running on computer %2, has reported %3 or more Informational status messages during the component status threshold period. Possible cause: The count equals or exceeds the component status Critical threshold (%5 status messages) for Informational status messages for the component. Solution: SMS Component Status Summarizer will set the component’s status to Critical in the Component Status summary in the SMS Administrator console.
4604	Informational	SMS Component Status Summarizer detected that component %1, running on computer %2, has reported %3 or more Warning status messages during the component status threshold period. Possible cause: The count equals or exceeds the component status Critical threshold (%5 status messages) for Warning status messages for the component. Solution: SMS Component Status Summarizer will set the component’s status to Critical in the Component Status summary in the SMS Administrator console.
4605	Informational	SMS Component Status Summarizer detected that component %1, running on computer %2, has reported %3 or more Error status messages during the component status threshold period. Possible cause: The count equals or exceeds the Component Status Critical Threshold (%5 status messages) for Error status messages for the component. Solution: SMS Component Status Summarizer will set the component’s status to Critical in the Component Status summary in the SMS Administrator console.
4606	Informational	SMS Component Status Summarizer detected that component %1 running on computer %2 has reported %3 or more Informational status messages during the component status threshold period. Possible cause: The count equals or exceeds the component status Warning threshold (%5 status messages) for Informational status messages for the component. Solution: If the component’s status is not already set to Warning, SMS Component Status Summarizer will set the component’s status to Warning in the Component Status summary in the SMS Administrator console.
4607	Informational	SMS Component Status Summarizer detected that component %1, running on computer %2, has reported %3 or more Warning status messages during the component status threshold period. Possible cause: The count equals or exceeds the component status Warning threshold (%5 status messages) for Warning status messages for the component. If the component’s status is not already set to Warning, SMS Component Status Summarizer will set the component’s status to Warning in the Component Status summary in the SMS Administrator console.
4608	Informational	SMS Component Status Summarizer detected that component %1, running on computer %2, has reported %3 or more Error status messages during the component status threshold period. Possible cause: The count equals or exceeds the component status Warning threshold (%5 status messages) for Error status messages for the component. Solution: If the component’s status is not already set to Warning, SMS Component Status Summarizer will set the component’s status to Warning in the Component Status summary in the SMS Administrator console.
4609	Informational	SMS Component Status Summarizer set the status of component %1, running on computer %2, to Critical. 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 %3 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 %3 that instructs Status Manager to discard the flooded status message when component %1 on computer %2 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.
4610	Informational	SMS Component Status Summarizer set the status of component %1 running on computer %2 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 %3 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 %3 that instructs Status Manager to discard the flooded status message when component %1 on computer %2 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.
4611	Informational	SMS Component Status Summarizer reset the status of component %1, running on computer %2, to OK. SMS Component Status Summarizer will automatically reset a component’s status to OK every time the component status threshold period elapses and a new threshold period begins. For example, if the threshold period is “Since 12:00:00 AM,” SMS Component Status Summarizer will reset the component’s status to OK every 24 hours at midnight. At this time, the counts of status messages reported by the component for the threshold period will be reset to zero. Solution: SMS Component Status Summarizer will also reset a component’s status to OK when an administrator manually resets the counts of status messages reported by the component for the threshold period. Solution: SMS Component Status Summarizer will also reset a component’s status to OK when an administrator adjusts the component status thresholds to be higher than the current counts of status messages reported by the component.
4612	Warning	SMS Component Status Summarizer has not received a status message from component %1, running on computer %2, in %3 hours. Possible cause: There is no record of this component in the site control file. Solution: The SMS Component Status Summarizer will assume the component was deinstalled and will remove it from the Component Status summary.
4613	Warning	SMS Component Status Summarizer received a status message that was reported by component %1, running on computer %2 at site %3, which is not the site where SMS Component Status Summarizer is running. Possible cause: SMS Component Status Summarizer is designed to process only status messages reported by components at the site where SMS Component Status Summarizer is running. Solution: SMS Component Status Summarizer will ignore this status message. Possible cause: This problem might be the result of defective software. Solution: If you suspect a software defect, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.
4614	Informational	SMS Component Status Summarizer reset the count of Error status messages reported by component %1 on computer %2 for the “Since %9” display interval (%9 is a 24-hour interval). The count is now %3; before the reset, the count was %4. The reset was requested on %5 by user %6 running the %7 application on computer %8.
4615	Informational	SMS Component Status Summarizer reset the count of Error status messages reported by component %1 on computer %2 for the “Since %9” display interval (1 is Sunday, 2 is Monday, and so on). The count is now %3; before the reset, the count was %4. The reset was requested on %5 by user %6 running the %7 application on computer %8.
4616	Informational	SMS Component Status Summarizer reset the count of Error status messages reported by component %1 on computer %2 for the “Since Day %9 of the Month” display interval. The count is now %3; before the reset, the count was %4. The reset was requested on %5 by user %6 running the %7 application on computer %8.
4617	Informational	SMS Component Status Summarizer reset the count of Error status messages reported by component %1 on computer %2 for the “Since Site Installation” display interval. The count is now %3; before the reset, the count was %4. The reset was requested on %5 by user %6 running the %7 application on computer %8.
4618	Informational	SMS Component Status Summarizer reset the count of Error status messages reported by component %1 on computer %2 for the %9 display interval. The count is now %3; before the reset, the count was %4. The reset was requested on %5 by user %6 running the %7 application on computer %8. Possible cause: %9 is a custom display interval you have configured the SMS Component Status Summarizer to use. SMS Component Status Summarizer cannot display an unencrypted version of %9 in a status message. Solution: If you wish to decode %9 into something more readable, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.
4619	Informational	SMS Component Status Summarizer reset the count of Warning status messages reported by component %1 on computer %2 for the “Since %9” display interval (%9 is a 24-hour interval). The count is now %3; before the reset, the count was %4. The reset was requested on %5 by user %6 running the %7 application on computer %8.
4620	Informational	SMS Component Status Summarizer reset the count of Warning status messages reported by component %1 on computer %2 for the “Since %9” display interval (1 is Sunday, 2 is Monday, and so on). The count is now %3; before the reset, the count was %4. The reset was requested on %5 by user %6 running the %7 application on computer %8.
4621	Informational	SMS Component Status Summarizer reset the count of Warning status messages reported by component %1 on computer %2 for the “Since Day %9 of the Month” display interval. The count is now %3; before the reset, the count was %4. The reset was requested on %5 by user %6 running the %7 application on computer %8.
4622	Informational	SMS Component Status Summarizer reset the count of Warning status messages reported by component %1 on computer %2 for the “Since Site Installation” display interval. The count is now %3; before the reset, the count was %4. The reset was requested on %5 by user %6 running the %7 application on computer %8.
4623	Informational	SMS Component Status Summarizer reset the count of Warning status messages reported by component %1 on computer %2 for the %9 display interval. The count is now %3; before the reset, the count was %4. The reset was requested on %5 by user %6 running the %7 application on computer %8. %9 is an encrypted version of the custom Display Interval you configured the SMS Component Status Summarizer to use. SMS Component Status Summarizer cannot display an unencrypted version of %9 in a status message.
4624	Informational	SMS Component Status Summarizer reset the count of Informational status messages reported by component %1 on computer %2 for the “Since %9” display interval (%9 is a 24-hour interval). The count is now %3; before the reset, the count was %4. The reset was requested on %5 by user %6 running the %7 application on computer %8.
4625	Informational	SMS Component Status Summarizer reset the count of Informational status messages reported by component %1 on computer %2 for the “Since %9” display interval (1 is Sunday, 2 is Monday, and so on). The count is now %3; before the reset, the count was %4. The reset was requested on %5 by user %6 running the %7 application on computer %8.
4626	Informational	SMS Component Status Summarizer reset the count of Informational status messages reported by component %1 on computer %2 for the “Since Day %9 of the Month” display interval. The count is now %3; before the reset, the count was %4. The reset was requested on %5 by user %6 running the %7 application on computer %8.
4627	Informational	SMS Component Status Summarizer reset the count of Informational status messages reported by component %1 on computer %2 for the “Since Site Installation” display interval. The count is now %3; before the reset, the count was %4. The reset was requested on %5 by user %6 running the %7 application on computer %8.
4628	Informational	SMS Component Status Summarizer reset the count of Informational status messages reported by component %1 on computer %2 for the %9 display interval. The count is now %3; before the reset, the count was %4. The reset was requested on %5 by user %6 running the %7 application on computer %8. %9 is an encrypted version of the custom display interval that you configured the SMS Component Status Summarizer to use. SMS Component Status Summarizer cannot display an unencrypted version of %9 in a status message.