Exchange Server 2016

  1. The Search query has sustained a high failure percentage or is slow for the database '{0}'. The last probe error was: {Probe.Error} ...
  2. The Search query test transaction failed. A zero hit count was returned by querying the keyword '{0}' in the inbox of user ...
  3. The Search query test transaction failed. The catalog is in the simple query mode. Search results returned may not be properly ...
  4. The Search query test transaction failed. The operation timed out after {2} seconds querying the keyword '{0}' in the inbox ...
  5. The Search query test transaction for the database '{0}' has failed {1} times running every {2} seconds. The last probe error ...
  6. The Search transport indexing agent has a high failure percentage. {3} documents were processed and {4} failed during the ...
  7. The Search WLM resource for the database '{0}' has been unhealthy for the last {1} minutes and is affecting mailbox moves. ...
  8. The Search WLM resource is not healthy for the database '{0}'.Details about the copies:{1}The move job affected:{2}The resource ...
  9. The Search-Mailbox cmdlet returns up to {0} results per mailbox if a search query is specified. To return more than {0} results, ...
  10. The second highest source of RPC load is in the category '{1}'. This category accounts for {2} RPC operations/second, out ...
  11. The secondary address {0} is in an invalid format. The secondary address must be a valid extension or in the form @contoso.com. ...
  12. The secondary WINS server address for network interface '{1}' on server {2} is blank. If primary WINS resolution fails this ...
  13. The security context couldn't be established due to a failure in the requested quality of service (for example, mutual authentication ...
  14. The security features that are required for delivery of this e-mail message are not supported by the recipient e-mail system. ...
  15. The security features that are required for delivery of this e-mail message aren't supported by the recipient's e-mail system. ...
  16. The seeding was cancelled for database '{0}' because the copy configuration changed on the seeding source '{1}' ( a failover ...
  17. The seeding was cancelled for database '{0}' from '{1}' because the database copy on server '{1}' has transitioned to failed ...
  18. The selected mailbox will be enabled for Unified Messaging. Upon completion, an email message will be sent to the mailbox ...
  19. The selected search was created using a previous version of Exchange. To start or edit the search in Exchange 2013, it must ...
  20. The send or update operation could not be performed because the change key passed in the request does not match the current ...
  21. The sender e-mail address is invalid. There may be an error in the e-mail account configuration. Check for configuration ...
  22. The sender has a malformed or missing mail attribute in the directory structure. The Transport categorizer cannot deliver ...
  23. The sender is not authorized to send e-mail messages to this e-mail address. Possible causes: 1)The session is not authenticated ...
  24. The sender isn't authorized to send e-mail messages to this e-mail address. The possible reasons for this are: 1)The session ...
  25. The sending external RMS server {0} doesn't allow the receiving organization {1} to store a decrypted copy of the IRM-protected ...
  26. The SendProtocolLogPath parameter is set to $null. Microsoft Exchange will continue to use the old location for protocol ...
  27. The SendProtocolLogPath parameter is set to $null. Setting the value of this parameter to $null disables protocol logging ...
  28. The Sensitive Information Type '{0}' is referenced by DLP Compliance rules and cannot be deleted. The following rules are ...
  29. The sepcified mailbox location identity "{0}" is invalid. The correct format for store mailbox location identity is " \ ", ...
  30. The sepcified mailbox store object identity "{0}" is invalid. The correct format for mailbox store object identity is " \ ...
  31. The server "{0}" can't support OAB with Version 4 enabled. You must install Exchange 2003 Service Pack 2 or KB 922817 before ...
  32. The server "{0}" doesn't have the Client Access server role installed. Provisioning Agent tasks can only be run locally on ...
  33. The server "{0}" doesn't have the Mailbox server role installed. Only Exchange servers that have the Mailbox server role ...
  34. The server "{0}" is running an older version of Exchange. You can run remote log searches only against Exchange 2007 or later. ...
  35. The server "{0}" isn't running Exchange 2010 or a later version. Only servers running Exchange 2010 or later can be assigned ...
  36. The server '{2}' is unlicensed and has exceeded its trial period for licensing. If you do not have a product key, see ht ...
  37. The server '{2}' is unlicensed. If you have a product key, select the Enter Product Key action on the server work center ...
  38. The server couldn't be contacted in the specified time. Check that you have network connectivity and that the server is running. ...
  39. The server couldn't retrieve the following message:Subject: "{0}"From: "{1}" ("{2}")Sent date: {3}The message hasn't been ...
  40. The server did not return authentication headers to an HTTP GET with no credentials. This virtual directory may not have ...
  41. The server for this account hasn't responded for at least {0} day. Please confirm that the server settings are correct in ...
  42. The server for this account hasn't responded for at least {0} day. Please make sure the server address below is correct, ...
  43. The server for this account hasn't responded for at least {0} days. Please confirm that the server settings are correct in ...
  44. The server for this account hasn't responded for at least {0} days. Please make sure the server address below is correct, ...
  45. The server for this account hasn't responded for at least {0} hour. Please confirm that the server settings are correct in ...
  46. The server for this account hasn't responded for at least {0} hour. Please make sure the server address below is correct, ...
  47. The server for this account hasn't responded for at least {0} hours. Please confirm that the server settings are correct ...
  48. The server for this account hasn't responded for at least {0} hours. Please make sure the server address below is correct, ...
  49. The server for this account hasn't responded. Please confirm that the server settings are correct in the {0}. After your ...
  50. The server for this account hasn't responded. Please make sure the server address below is correct, and then click Save. ...
  51. The server from which this offline address book is being moved, "{0}", no longer exists in Active Directory. The OAB will ...
  52. The server information for the database '%1' could not be located for discovery search request with request id '%2' in retry ...
  53. The server IP address received by the Test-UMConnectivity task from the Microsoft Exchange Unified Messaging service on the ...
  54. The server object for this server ("%s") is a clustered Exchange Virtual Server . You may not perform maintenance on this ...
  55. The server rejected an incoming call with the ID "%1" because the associated UM IP gateway with address "%2" is disabled. ...
  56. The server that you specified, {0}, appears more than once, Provide a unique server name in the WritableServerObject parameter. ...
  57. The server {0} does not have Exchange Server installed. This tool will only investigate computers running Microsoft Exchange ...
  58. The server {0} exhibited a problem with RPC latencies or a high number of RPC requests. A high number of RPC latencies or ...
  59. The server {0} exhibited a problem with RPC latencies or high RPC requests. High RPC latencies or RPC requests are an indicator ...
  60. The server {0} is configured for Office 365 hybrid, and Get-federationinformation works successfully for the customer domain ...
  61. The server {0} is configured for Office 365 hybrid, and MRSProxy is enabled in Exchange web services virtual directory '{1}' ...
  62. The server {0} is configured for Office 365 hybrid, and the certificate '{1}' is proper in place for federation and mail ...
  63. The server {0} is configured for Office 365 hybrid, and the federation trust is working properly on server {0} for Office ...
  64. The server {0} is configured for Office 365 hybrid, and the move request for mailbox '{1}' from database '{2}' to database ...
  65. The server {0} is configured for Office 365 hybrid, and WSSecurity is enabled in Exchange Autodiscover virtual directory ...
  66. The server {0} is configured for Office 365 hybrid, and WSSecurity is enabled in Exchange web services virtual directory ...
  67. The server {0} is configured for Office 365 hybrid, but Get-federationinformation does not work successfully for the customer ...
  68. The server {0} is configured for Office 365 hybrid, but MRSProxy is not enabled in Exchange web services virtual directory ...
  69. The server {0} is configured for Office 365 hybrid, but the certificate '{1}' is not proper in place for federation and mail ...
  70. The server {0} is configured for Office 365 hybrid, but the federation trust is not working properly on server {0} for Office ...
  71. The server {0} is configured for Office 365 hybrid, but WSSecurity is not enabled in Exchange Autodiscover virtual directory ...
  72. The server {0} is configured for Office 365 hybrid, but WSSecurity is not enabled in Exchange web services virtual directory ...
  73. The server {0} is listed as a Client Access server in the HybridConfiguration Active Directory object, but it doesn't have ...
  74. The server {1} isn't responding to an attempt to connect to remote PowerShell. This will prevent you from managing this server ...
  75. The Server, Database and PartnerDelegatedTenant management scopes can only be defined in the top level organization. The ...