%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 %5 (generation %6) has damaged or invalid log (%7), ESE has removed the portion of log corrupted since these ...
The log range read from the file "%1" at offset %2 for %3 bytes failed verification due to a corrupted checksum log record. ...
The log range read from the file "%1" at offset %2 for %3 bytes failed verification due to a range checksum mismatch. The ...
The log range read from the file "%4" at offset %5 for %6 bytes failed verification due to a corrupted checksum log record. ...
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 %1 doesn't match the logfiles from the backup set. Logfile replay cannot succeed ...
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 %1 does not match the database engine version stamp. The logfiles may be the wrong version ...
The log version stamp of logfile %4 does not match the database engine version stamp. The logfiles may be the wrong version ...