%11Status Manager has created %1 instances of the "SMS Status Messages" performance object, which is the maximum allowed number of instances. Every time Status Manager receives a status message it will update the performance counters contained by this performance object. You can measure Status Manager's processing performance by monitoring this performance object with the Windows Performance Monitor. Because the maximum limit was reached, Status Manager will not create any more instances of this performance object. Status Manager builds the list of instances as it receives status messages. You can reset the list by restarting Status Manager.%12%0
SQL Server Backup path is empty or invalid. For remote SQL Server scenarios you should provide either a UNC path for entire ...
SQL Server memory should not be left to its default configuration of unlimited memory usage. Please configure SQL server ...
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 ...