%11SMS Status Manager received a status message with an invalid time stamp. The status message was reported by component "%1" running on computer "%2". Possible cause: The system clock on computer "%2" is not synchronized with the site server's system clock. Most likely, the system clock on computer "%2" is set to some date greater than 2035 or less than 1970. Solution: Synchronize the system clock of computer "%2" with the site server's system clock. Please refer to your Windows NT Server documentation or the Microsoft Knowledge Base for further information. When SMS Status Manager receives status messages with invalid time stamps, it will stamp these messages with the current system time on the site server. The messages will then be processed successfully, but their time and date might not be truly representative of when they were reported in real time. SMS Status Manager will continue to report this problem every 24 hours until you fix it.%0
SMS State Migration Point failed to read the SignedSerializedSMPKey from the registry on computer %1. Possible reasons are ...
SMS Status Manager has created %1 instances of the "SMS Status Messages" performance object, which is the maximum allowed ...
SMS Status Manager received a status message reported by component "%1" running on computer "%2", and the time stamp on the ...
SMS Status Manager received a status message reported by component "%1" running on computer "%2", and the time stamp on the ...
SMS Status Manager received a status message with an invalid time stamp. The status message was reported by component "%1" ...
SMS Status Manager successfully initialized an in-memory queue to forward status messages to the summarizer component %1. ...
SMS Status Manager successfully initialized the "SMS Status Messages" performance object. Every time SMS Status Manager receives ...
SMS Status Manager was instructed by a Status Filter Rule to execute program "%1" with command-line arguments "%2" upon receipt ...
SMS Status Manager was instructed by a Status Filter Rule to execute program "%1" with command-line arguments "%2" upon receipt ...