%11SMS Outbox Monitor took %1 seconds to complete a cycle. This exceeds its configured interval of %2 seconds by %3 seconds.%12 Possible cause: Site system "%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 system "%4" has a high backlog of files in its outboxes. 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 Object Replication Manager failed to process SMS Object Replication File %1. This SMS Object Replication file has been ...
SMS Offer Status Summarizer cannot process a status message because it contains the invalid Advertisement ID "%6". As a result, ...
SMS Offer Status Summarizer cannot process a status message because it does not contain an Advertisement ID. As a result, ...
SMS Offer Status Summarizer cannot process a status message because it has an invalid message ID %1. The message ID must ...
SMS Outbox Monitor took %1 seconds to complete a cycle. This exceeds its configured interval of %2 seconds by %3 seconds.%12 ...
SMS Policy Provider failed to process Machine Settings changes. These changes will be retried on next processing cycle.%12 ...
SMS Policy Provider failed to process Machine Settings for Machine %1. This Machine Settings will be retried on the next ...
SMS Policy Provider successfully created a policy and a policy assignment based on package %1 (%2), program %3 and advertisement ...
SMS Policy Provider successfully updated the policy and the policy assignment that were created from Distribution Point %1 ...