%11Site Component Manager could not remove the Configuration Manager installation directory "%2" on site system "%1".%12 Possible cause: The site system is not exporting the default drive letter shares, such as "%1\C$", "%1\D$", and so on. Solution: Enable the default drive letter shares on the site system. Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: Site Component Manager does not have sufficient access rights to remotely administer the site system. Solution: Verify that the Site System Installation accounts are properly configured to allow the site to remotely administer the site system. Possible cause: Network problems are preventing Site Component Manager from properly accessing the site system. Solution: Investigate and correct any problems on your network.%0
Site Component Manager could not install the %1 service on site system "%2" with the service logging on as account "%3".%12 ...
Site Component Manager could not install the %1 service on site system "%2" with the service logging on as account "%3".%12 ...
Site Component Manager could not read the Network Connection account data, which is stored in the installation directory ...
Site Component Manager could not remove the "%2" account from site system "%1".%12 Possible cause: The site system is turned ...
Site Component Manager could not remove the Configuration Manager installation directory "%2" on site system "%1".%12 Possible ...
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. ...