%11Site Backup was unable to initiate command file "%1" .%12 Possible cause: Unable to find command shell to execute this file. Solution: Install command shell (CMD.EXE) in the system directory. Possible cause: Command shell failed to execute this file. Solution: Verify that CMD.EXE or "%1" are not corrupted.%0
Site Backup was unable to back up %1 database %2 to %3.%12 Possible cause: %3 or its directory are not writable. Solution: ...
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 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 ...