%1 (%2) %3A torn-write was detected during hard recovery in logfile %4. The failing checksum record is located at position %5. This logfile has been damaged and is unusable. For more information, click http://www.microsoft.com/contentredirect.asp.
A token has been assigned to mailbox GUID %1 for %2 minutes. This token may not have been properly released and is preventing ...
A torn-write was detected during hard recovery in log file %1. The failing checksum record is located at position %2. This ...
A torn-write was detected during hard recovery in log file %1. The failing checksum record is located at position %2. This ...
A torn-write was detected during hard recovery in logfile %4. The failing checksum record is located at position %5. This ...
A torn-write was detected during hard recovery in logfile %4. The failing checksum record is located at position %5. This ...
A torn-write was detected during soft recovery in log file %1. The failing checksum record is located at position %2. The ...
A torn-write was detected during soft recovery in log file %1. The failing checksum record is located at position %2. The ...
A torn-write was detected during soft recovery in logfile %4. The failing checksum record is located at position %5. The ...
A torn-write was detected during soft recovery in logfile %4. The failing checksum record is located at position %5. The ...