%11SMS Site 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
SMS 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. ...
SMS Site Backup was unable to back up registry key %1 to %2.%12 Possible cause: SMS Site Backup was unable to connect to ...
SMS Site Backup was unable to initiate command file "%1" .%12 Possible cause: Unable to find command shell to execute this ...
SMS Site Backup was unable to open control file "%1". Site backup did not occur.%12 Possible cause: Wrong name specified ...
SMS Site Backup was unable to run command line "%1" (error #%2).%12 Possible cause: "%1" does not exist at the specified ...
SMS Site Component Manager cannot install this component on this site system because %1 bytes are required on the drive containing ...
SMS Site Component Manager cannot remove HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS subkeys from the registry on server %s. ...
SMS Site Component Manager cannot stop component %s on component server %s. The component is probably performing clean up ...
SMS Site Component Manager cannot stop component %s on multisite component server %s. The component is probably performing ...