%1 (%2) %3A torn-write was detected during soft recovery in logfile %4. The failing checksum record is located at position %5. The logfile damage will be repaired and recovery will continue to proceed. For more information, click http://www.microsoft.com/contentredirect.asp.
A TLS failure occurred during TLS negotiation. Either the local certificate is unusable or the remote server doesn't trust ...
A torn-write was detected during hard recovery in logfile %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 soft recovery in logfile %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 while restoring from backup in logfile %1 of the backup set. The failing checksum record is located ...
A torn-write was detected while restoring from backup in logfile %4 of the backup set. The failing checksum record is located ...
A total of {1} message tracking log entries were generated on server {2} indicating that messages could not be delivered ...
A total of {1} messages found in the Poison Message queue were submitted by mailboxes in a remote Active Directory site or ...