%1 (%2) %3The log file %5 (generation %6) has damaged or invalid log (%7), ESE has removed the portion of log corrupted since these committed logs are specified as unneeded, so that ESE can recover (through generation %4) any attached databases to a consistent state, but with data loss. For more information, click http://www.microsoft.com/contentredirect.asp.
The log file %2 (generation %3) has damaged or invalid log (%4), ESE has removed the portion of log corrupted since these ...
The log file %4 is damaged, invalid, or inaccessible (error %5) and cannot be used. If the log file cannot be found, the ...
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 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 ...