Component Monitor took %1 seconds to complete a cycle. This exceeds its configured interval of %2 seconds by %3 seconds.%12 ...

%11Component 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

Collection Evaluator failed to write to file "%1".%12 Possible cause: low disk space on the drive containing the file "%1". ... Collection Evaluator successfully processed %1 client updates for collection %2. Original clients number: %3, added: %4, ... Collection migration jobs migrate collections and the objects related to the collections that you specify. Object migration ... Communication issues on mobile devices that are managed by the Configuration Manager client for Windows CE and that are not ... Component Monitor took %1 seconds to complete a cycle. This exceeds its configured interval of %2 seconds by %3 seconds.%12 ... Component Status Summarizer detected that component "%1" running on computer "%2" has reported %3 or more Informational status ... Component Status Summarizer detected that component "%1", running on computer "%2", has reported %3 or more Error status ... Component Status Summarizer detected that component "%1", running on computer "%2", has reported %3 or more Error status ... Component Status Summarizer detected that component "%1", running on computer "%2", has reported %3 or more Informational ...