%11SMS Status Manager has created %1 instances of the "SMS Status Messages" performance object, which is the maximum allowed number of instances. Every time SMS Status Manager receives a status message it will update the performance counters contained by this performance object. You can measure SMS Status Manager's processing performance by monitoring this performance object with the Windows NT Performance Monitor. Because the maximum limit was reached, SMS Status Manager will not create any more instances of this performance object. SMS Status Manager builds the list of instances as it receives status messages. You can reset the list by restarting SMS Status Manager.%12%0
SMS SQL Monitor is executing database maintenance SQL command/task "%1". You can configure the execution schedule for this ...
SMS SQL Monitor is installing trigger "%1" for table "%2" and actions "%3" in the SMS site database. Server components such ...
SMS SQL Monitor is removing trigger "%1" from the SMS site database. Server components such as SMS Hierarchy Manager, SMS ...
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. ...