%11SMS Executive is scheduled to start this component now, but cannot because it is already running. Possible cause: The component is scheduled to run so frequently that it cannot complete its work before the next scheduled run time. Solution: Adjust the component's schedule in the Configuration Manager Console so that it will not run so frequently. Possible cause: The component is running for an abnormally long time. Solution: Examine the other status messages reported by the component. If the component is experiencing a problem, correct it.%0
SMS CI Assignment has been directly deleted from the site Database. Deletion of collection may cause the deletion of all ...
SMS Executive could not start this component because it could not determine the address of the ThreadMain() function exported ...
SMS Executive could not start this component because it could not load \"%1\" using the MFC AfxLoadLibrary() function.%12 ...
SMS Executive detected that this component stopped unexpectedly.%12 Possible cause: The component is experiencing a severe ...
SMS Executive is scheduled to start this component now, but cannot because it is already running. Possible cause: The component ...
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 ...