%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 TLS failure occured because the remote end disconnected while TLS negotiation was in progress. The Error Code = {0} and ...
A TLS failure occured because the target name specified in its certificate is incorrect. The Error Code = {0} and the Message ...
A TLS failure occured during TLS negotiation. Either the local certificate is unusable or the remote does not trust it. The ...
A top-level auto attendant is one that has one or more extensions configured. It will answer incoming calls to one or more ...
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 %4. The failing checksum record is located at position %5. The ...
A torn-write was detected while restoring from backup in logfile %4 of the backup set. The failing checksum record is located ...
A transaction log file in the sequence of logs accessed during transaction log replay is missing or mismatched with the other ...
A transient failure has occurred. The problem may resolve itself in a while. The service will retry in %1 minutes. Message: ...