%11SMS Component Monitor took %1 seconds to complete a cycle. This exceeds its configured interval of %2 seconds by %3 seconds.%12 Possible cause: Site server "%4" is under heavy load and is either CPU or I/O constrained. Solution: Use Task Manager to check for processes causing high CPU or I/O utilization. Possible cause: Site server "%4" has a high backlog of files in its inboxes. Solution: Give the system time to work through the current backlog. Do not create any additional tasks that would load the system further.%0
SMS Collection Evaluator has removed duplicate resources for collection "%1".%12 Resources can be included in the same collection ...
SMS Collection Evaluator received an .adc (add collection) file for collection "%1", but failed to create a result table ...
SMS Collection Evaluator received an .adc (add collection) file for collection "%1", created a result table in the SMS site ...
SMS Collection Evaluator received an .adc (add collection) file for collection "%1", is creating a result table in the SMS ...
SMS Component Monitor took %1 seconds to complete a cycle. This exceeds its configured interval of %2 seconds by %3 seconds.%12 ...
SMS Component Status Summarizer detected that component "%1" running on computer "%2" has reported %3 or more Informational ...
SMS Component Status Summarizer detected that component "%1", running on computer "%2", has reported %3 or more Error status ...
SMS Component Status Summarizer detected that component "%1", running on computer "%2", has reported %3 or more Error status ...
SMS Component Status Summarizer detected that component "%1", running on computer "%2", has reported %3 or more Informational ...