%11SMS Site Component Manager could not stop the %1 service on site system "%2".%12 Possible cause: SMS Site Component Manager does not have sufficient access rights to administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to administer the site system. If this problem persists, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information.%0
SMS Site Component Manager could not start the %1 service on site system "%2" with the service logging on as account "%3".%12 ...
SMS Site Component Manager could not start the %1 service on site system "%2" with the service logging on as account "%3".%12 ...
SMS Site Component Manager could not start the %1 service on site system "%2" with the service logging on as account "%3".%12 ...
SMS Site Component Manager could not start this component on this site system because the SMS Executive service is not running. ...
SMS Site Component Manager could not stop the %1 service on site system "%2".%12 Possible cause: SMS Site Component Manager ...
SMS Site Component Manager could not verify that the "%2" account exists on site system "%1".%12 Possible cause: The site ...
SMS Site Component Manager created the "%2" account on site system "%1". When SMS Site Component Manager installs SMS services ...
SMS Site Component Manager created the SMS server components' installation directory "%2" on site system "%1". SMS Site Component ...
SMS Site Component Manager detected that %1 bytes are required by this component on the drive containing the "%2" directory, ...