Site Component Manager could not stop the %1 service on site system "%2".%12 Possible cause: Site Component Manager does ...

%11Site Component Manager could not stop the %1 service on site system "%2".%12

Possible cause: 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 the site to administer the site system.

If this problem persists, refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information.%0

Site Component Manager could not start the %1 service on site system "%2" to install component %4 with the service logging ... Site Component Manager could not start the %1 service on site system "%2" with the service logging on as account "%3".%12 ... Site Component Manager could not start the %1 service on site system "%2" with the service logging on as account "%3".%12 ... Site Component Manager could not start this component on this site system because the SMS Executive service is not running. ... Site Component Manager could not stop the %1 service on site system "%2".%12 Possible cause: Site Component Manager does ... Site Component Manager could not verify that the "%2" account exists on site system "%1".%12 Possible cause: The site system ... Site Component Manager could not write Network Connection account data to the installation directory "%2" on site system ... Site Component Manager created the "%2" account on site system "%1". When Site Component Manager installs services on the ... Site Component Manager created the Configuration Manager Server Components' installation directory "%2" on site system "%1". ...