The log file sequence in "%1" has been halted due to a fatal error. No further updates are possible for the databases that use this log file sequence. Please correct the problem and mount the database, or restore the database from a backup.
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 file %5 (generation %6) has damaged or invalid log (%7), ESE has removed the portion of log corrupted since these ...
The log file sequence in "%1" has been halted due to a fatal error. No further updates are possible for the databases that ...
The log file sequence in "%1" has been halted due to a fatal error. No further updates are possible for the databases that ...
The log files %1 and %2 are not in a valid sequence. Log file replay cannot succeed if there are gaps in the sequence of ...
The log files %1 and %2 are not in a valid sequence. Log file replay cannot succeed if there are gaps in the sequence of ...
The log range read from file "%1" at offset %2 for %3 bytes failed verification due to a corrupted checksum log record. The ...
The log range read from file "%1" at offset %2 for %3 bytes failed verification due to a corrupted checksum log record. The ...