%11Site Backup was unable to run command line "%1" (error #%2).%12 Possible cause: "%1" does not exist at the specified location or is not in the system path. Solution: Install "%1" at the specified location, or add its directory to the system path. Possible cause: An application is using %2 or some component of its path (for example, Windows Explorer may be viewing %2's parent directory.) Solution: Verify that %2 and its parent directories are not in use by any application.%0
Site Backup was unable to back up file system object %1 to %2.%12 Possible cause: %1 is not readable, or %2 is not writable. ...
Site Backup was unable to back up registry key %1 to %2.%12 Possible cause: Site Backup was unable to connect to or set backup ...
Site Backup was unable to initiate command file "%1" .%12 Possible cause: Unable to find command shell to execute this file. ...
Site Backup was unable to open control file "%1". Site backup did not occur.%12 Possible cause: Wrong name specified or permissions ...
Site Backup was unable to run command line "%1" (error #%2).%12 Possible cause: "%1" does not exist at the specified location ...
Site Component Manager cannot install this component on this site system because %1 bytes are required on the drive containing ...
Site Component Manager could not access site system "%1" due to an unexpected failure within the network abstraction layer ...
Site Component Manager could not access site system "%1".%12 Possible cause: The site system is turned off, not connected ...
Site Component Manager could not add machine account "%1" to the SQL Access Group "%2" on the SQL Server machine "%3". Possible ...