Exchange Server 2010

  1. A secure connection from domain-secured domain '%1' on connector '%2' failed to authenticate because validation of the Transport ...
  2. A secure connection to domain secure domain '%1' on connector '%2' could not be established because TLS was not offered. ...
  3. A secure connection to domain secure domain '%1' on connector '%2' could not be established because TLS was not offered. ...
  4. A secure connection to domain-secured domain '%1' on connector '%2' could not be established because the DomainSecureEnabled ...
  5. A secure connection to domain-secured domain '%1' on connector '%2' could not be established because the DomainSecureEnabled ...
  6. A secure connection to domain-secured domain '%1' on connector '%2' could not be established because the validation of the ...
  7. A secure connection to domain-secured domain '%1' on connector '%2' could not be established because the validation of the ...
  8. A secure connection to the domain %1 could not be established because the Transport Layer Security (TLS) certificate for ...
  9. A secure connection to the domain %1 could not be established because the Transport Layer Security (TLS) certificate for ...
  10. A secure connection to the server couldn't be established. Message signing and encryption functionality won't be available. ...
  11. A secure connection to the server couldn't be established. You need a secure connection to read or compose signed or encrypted ...
  12. A secure connection with Exchange server %1 could not be established because the protocol negotiation did not find a mutually ...
  13. A secure connection with Exchange server %1 could not be established because the protocol negotiation did not find a mutually ...
  14. A secured connection couldn't be established to this account. Not all providers offer secured connections. Would you like ...
  15. A security error occurred while trying to deliver your e-mail message. Security policies prohibit further explanation of ...
  16. A serious error is preventing proper operation of database '%1' ('%2'). Review the event logs for failures of the database ...
  17. A serious error is preventing proper operation of database '%1' ('%2'). Review the event logs for failures of the database ...
  18. A serious error is preventing proper operation of database '%4' ('%5'). Review the application and system event logs for ...
  19. A serious error is preventing proper operation of database '%4' ('%5'). Review the application and system event logs for ...
  20. A server configuration change is temporarily preventing access to your account. Please close all Internet Explorer windows ...
  21. A server object for this server ("%s") already exists in the Administrative Group "%s". If you are attempting to recover ...
  22. A server object for this server ("%s") must exist in the Active Directory in order to recover this server. If you are attempting ...
  23. A server roles specification is invalid with this operation. To list the available command-line parameters, type Setup /? ...
  24. A server roles specification is invalid with this operation. To list the available command-line parameters, type Setup /? ...
  25. A server-side administrative operation has failed with this error: {0} You can try the operation again, and you may not get ...
  26. A server-side database availability group administrative operation failed with a transient error. Please try the operation ...
  27. A server-side operation for user {0} failed with error 0x{1:X}. For more information, please see the event logs on the server ...
  28. A server-side operation for user {0} has failed. You may be able to try the operation again. For more information, see the ...
  29. A Setup failure previously occurred while installing the {1} role. Either run Setup again for just this role, or remove the ...
  30. A shadow copy backup is starting. For more information, click http://www.microsoft.com/contentredirect.asp.
  31. A shadow copy backup is starting. For more information, click http://www.microsoft.com/contentredirect.asp.
  32. A significant portion of the database buffer cache has been written out to the system page file. This may result in severe ...
  33. A significant portion of the database buffer cache has been written out to the system page file. This may result in severe ...
  34. A significant portion of the database buffer cache has been written out to the system paging file. This may result in severe ...
  35. A significant portion of the database buffer cache has been written out to the system paging file. This may result in severe ...
  36. A single recipient address must be specified using the RecipientFilter parameter in order for the RecipientPath template ...
  37. A single replica of folder '{1}' for offline address book '{2}' exists in the organization. To increase performance and resilience, ...
  38. A single replica of the free/busy folder for administrative group '{3}' exists in the organization, and more than 10,000 ...
  39. A single replica of the free/busy folder for administrative group '{3}' exists in the organization. In some situations, multiple ...
  40. A single-labeled DNS domain prepared for Exchange was detected. This is not a recommended configuration, and will not be ...
  41. A situation where the server is configured to loop back on itself was detected. If you have multiple SMTP virtual servers ...
  42. A slow file IO operation was encountered on file '%1' for copy '%2'. The observed latency was %3 ms while performing a '%4'. ...
  43. A slow file IO operation was encountered on file '%1' for copy '%2'. The observed latency was %3 ms while performing a '%4'. ...
  44. A stack exception was thrown in module %1; some parameters and their values were %2. A significant section of the call stack ...
  45. A stack exception was thrown in module %1; some parameters and their values were %2. A significant section of the call stack ...
  46. A stagnation of events in the notification queue has been detected for database %1. The number of notifications waiting in ...
  47. A stagnation of events in the notification queue has been detected for database %1. The number of notifications waiting in ...
  48. A tag can be created based on the settings of an existing managed folder. Only one tag is created per selected managed folder. ...
  49. A target checkpoint file '{0}' already exists. You must remove this file before database seeding or reseeding can be performed. ...
  50. A temporary change has occurred that requires you to connect to a different server. To connect, click the button below. For ...
  51. A temporary routing condition on the server prevented the delivery of the message. Please try to send the message again. ...
  52. A test API has been used to corrupt page %4 of database '%5'. For more information, click http://www.microsoft.com/contentredirect.asp. ...
  53. A test API has been used to corrupt page %4 of database '%5'. For more information, click http://www.microsoft.com/contentredirect.asp. ...
  54. A test message was addressed to SMTP domain '{1}', but no recipient policy matches this address. Please ensure that this ...
  55. A test-only prereq has failed. If you see this and didn't expect to, delete the registry key HKLM\SOFTWARE\Microsoft\Exc ...
  56. A third-party display driver '{9}' is installed on server {2}. This may cause excessive nonpaged pool memory usage on the ...
  57. A throttling RPC client failed to be created for Mailbox server %1 with error code %2. Failure details: %3. Inner exception: ...
  58. A throttling RPC client failed to be created for Mailbox server %1 with error code %2. Failure details: %3. Inner exception: ...
  59. A time-out occurred while trying to evaluate the call answering rule for user %1 in the call with ID %2. This resulted in ...
  60. A time-out occurred while trying to evaluate the call answering rule for user %1 in the call with ID %2. This resulted in ...
  61. A time-out occurred while trying to retrieve mailbox data for user '%1' in the call with ID '%2'. If this event occurs frequently, ...
  62. A time-out occurred while trying to retrieve mailbox data for user '%1' in the call with ID '%2'. If this event occurs frequently, ...
  63. A TLS failure occurred because the certificate presented by the remote server has expired. The error code = 0x{0:X} and the ...
  64. A TLS failure occurred because the certificate presented by the remote server wasn't trusted. The error code = 0x{0:X} and ...
  65. A TLS failure occurred because the local certificate specified wasn't found in the local store. The error code = 0x{0:X} ...
  66. A TLS failure occurred because the remote certificate doesn't have the necessary enhanced key usage information. The error ...
  67. A TLS failure occurred because the remote certificate that was presented has been revoked. The error code = 0x{0:X} and the ...
  68. A TLS failure occurred because the remote server disconnected while TLS negotiation was in progress. The error code = 0x{0:X} ...
  69. A TLS failure occurred because the target name specified in the certificate isn't correct. The error code = 0x{0:X} and the ...
  70. A TLS failure occurred during TLS negotiation. Either the local certificate is unusable or the remote server doesn't trust ...
  71. A token has been assigned to mailbox GUID %1 for %2 minutes. This token may not have been properly released and is preventing ...
  72. A torn-write was detected during hard recovery in log file %1. The failing checksum record is located at position %2. This ...
  73. A torn-write was detected during hard recovery in log file %1. The failing checksum record is located at position %2. This ...
  74. A torn-write was detected during hard recovery in logfile %4. The failing checksum record is located at position %5. This ...
  75. A torn-write was detected during hard recovery in logfile %4. The failing checksum record is located at position %5. This ...