%1 (%2) %3The log range read from the file "%4" at offset %5 for %6 bytes failed verification due to a range checksum mismatch. The expected checksum was %8 and the actual checksum was %9. The read operation will fail with error %7. If this condition persists then please restore the logfile from a previous backup. For more information, click http://www.microsoft.com/contentredirect.asp.
The log file %4 is damaged, invalid, or inaccessible (error %5) and cannot be used. If this log file is required for recovery, ...
The log file %4 is missing (error %5) and cannot be used. If this log file is required for recovery, a good copy of the log ...
The log folder path that you specified contains one or more files. You must specify an empty directory for the log folder ...
The log path that you specified for the local continuous replication copy already contains files with a matching prefix. ...
The log range read from the file "%4" at offset %5 for %6 bytes failed verification due to a range checksum mismatch. The ...
The log signature of the existing logfile %4 doesn't match the logfiles from the backup set. Logfile replay cannot succeed ...
The log version stamp of logfile %4 does not match the database engine version stamp. The logfiles may be the wrong version ...
The logfile sequence in "%4" has been halted due to a fatal error. No further updates are possible for the databases that ...
The logfiles %4 and %5 are not in a valid sequence. Logfile replay cannot succeed if there are gaps in the sequence of available ...