%1 (%2) %3Corruption was detected during hard recovery in logfile %4. The failing checksum record is located at position %5. Data not matching the log-file fill pattern first appeared in sector %6. This logfile has been damaged and is unusable. For more information, click http://www.microsoft.com/contentredirect.asp.
Corrupted log file '%1' for database copy '%2' was repaired by recopying the log file from the active copy on server '%3'. ...
Corruption has been detected in database '%1' ('%2'). The error may occur because of human errors, system, or storage problems. ...
Corruption has been detected in database '%4' ('%5'). The error may occur because of human errors, system, or storage problems. ...
Corruption was detected during hard recovery in logfile %1. The failing checksum record is located at position %2. Data not ...
Corruption was detected during hard recovery in logfile %4. The failing checksum record is located at position %5. Data not ...
Corruption was detected during soft recovery in logfile %1. The failing checksum record is located at position %2. Data not ...
Corruption was detected during soft recovery in logfile %4. The failing checksum record is located at position %5. Data not ...
Corruption was detected while restoring from backup logfile %1. The failing checksum record is located at position %2. Data ...
Corruption was detected while restoring from backup logfile %4. The failing checksum record is located at position %5. Data ...