%1 (%2) %3The log file %5 (generation %6) has damaged or invalid log (%7), ESE has removed the portion of log corrupted since this 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. Details: Log directory: %8
The log file "%1" has grown too large (over %2!d!KB). Subsequent log entries will not be logged to a file. To resume logging ...
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 this ...
The log files folder must not be the same as the source folder: %1. Type the name of another folder or change the name of ...
The log is pinned due to reservation consuming most of the log space. Free some reserved records to make space available. ...
The log of the subscription is in disabled state, and can not be used to forward events to. The log must first be enabled ...
The log range read from the file "%4" at offset %5 for %6 bytes failed verification due to a corrupted checksum log record. ...