%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 Executive will never start this component because it is never scheduled to run. If you want SMS Executive to start the ...
SMS Hardware Inventory Agent cannot update the SMS Hardware Inventory Schema. The new Managed Object Format (MOF) file from ...
SMS Inbox Monitor took %1 seconds to complete a cycle. This exceeds its configured interval of %2 seconds by %3 seconds.%12 ...
SMS installation cannot complete until the required component, Microsoft .NET Framework Version 4.0, is installed. The component ...
SMS Outbox Monitor took %1 seconds to complete a cycle. This exceeds its configured interval of %2 seconds by %3 seconds.%12 ...
SMS provider cannot be installed on SQL server as it is clustered and it cannot be installed on the site server as SMS provider ...
SMS Site Component Manager cannot remove HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS subkeys from the registry on server %s. ...
SMS Site Component Manager cannot stop component %s on component server %s. The component is probably performing clean up ...
SMS Site Component Manager cannot stop component %s on multisite component server %s. The component is probably performing ...