%11Status Manager received a status message reported by component "%1" running on computer "%2", and the time stamp on the message is more recent than the current system time on the site server. Possible cause: The system clock on computer "%2" is %3 or more seconds ahead of the site server's system clock. Solution: Synchronize the system clock of computer "%2" with the site server's system clock. Please refer to your Windows Server documentation or the Microsoft Knowledge Base for further information. Status Manager will process status messages with improper time stamps when the site server's system clock surpasses the improper time stamps. For example, this status message will not be processed for %3 seconds. Status Manager will continue to report this problem every 24 hours until you fix it. Status Manager will not report this problem if the system clock of computer "%2" is less than %4 seconds ahead of the site server's system clock. This interval is configurable in the site control file. Please refer to the Microsoft Knowledge Base for further information.%0
StartUpload replicationgroup %1 last sync version %2 failed with status code %3 and error code %4. Please refer to dmpuploader.log ...
State Migration Point failed to read the SignedSerializedSMPKey from the registry on computer %1. Possible reasons are SMP ...
Status Manager has created %1 instances of the "SMS Status Messages" performance object, which is the maximum allowed number ...
Status Manager received a status message reported by component "%1" running on computer "%2", and the time stamp on the message ...
Status Manager received a status message reported by component "%1" running on computer "%2", and the time stamp on the message ...
Status Manager received a status message with an invalid time stamp. The status message was reported by component "%1" running ...
Status Manager successfully initialized an in-memory queue to forward status messages to the summarizer component %1. The ...
Status Manager successfully initialized the "SMS Status Messages" performance object. Every time Status Manager receives ...
Status Manager was instructed by a Status Filter Rule to execute program "%1" with command-line arguments "%2" upon receipt ...