%11SMS Site Backup was unable to back up registry key %1 to %2.%12 Possible cause: SMS Site Backup was unable to connect to or set backup privileges for the source registry. Solution: If %1 is in a remote registry, verify that the Site System Connection accounts are properly configured to allow SMS to administer the remote computer; otherwise, reboot. Possible cause: %1 specifies a registry key relative to a hive other than HKEY_LOCAL_MACHINE. Solution: Change %1 so it is relative to HKEY_LOCAL_MACHINE. Possible cause: %2 or its directory are not writable. Solution: Adjust file attributes and/or permissions on %2 and/or its directory. 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 run, but the backup destination directory ( %1 ) is invalid. Site backup did not occur.%12 Possible cause: ...
SMS Site Backup was unable to back up %1 database %2 to %3.%12 Possible cause: %3 or its directory are not writable. Solution: ...
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 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 ...