Exchange Server 2016

  1. The anti-malware agent could not stamp the attachment details header for the message with MessageId: %1. Error Details: %2 ...
  2. The anti-malware agent could not submit a message to the hygiene management service. MessageId: %1 Message sent: %2 From: ...
  3. The anti-malware agent could not write a message to the recovery store. MessageId: %1 Message sent: %2 From: %3 Size: %4 ...
  4. The anti-malware agent deferred a message the maximum number of times, and has moved it to the undeliverable folder. ( \ ...
  5. The anti-malware agent encountered an error while scanning. MessageId: %1 Message sent: %2 From: %3 Size: %4 Bytes Error: ...
  6. The anti-malware agent has detected malware. MessageId: %1 Message sent: %2 From: %3 Size: %4 Bytes Engine: %5 (%6) Malware ...
  7. The anti-malware agent wrote a message to the recovery store after a previous attempt to write failed. MessageId: %1 Message ...
  8. The API version ({0}) required by this app isn't supported by the Exchange Server version ({1}) that you're connecting to. ...
  9. The apiVersionSupported parameter is invalid. It should be in the form of major version, minor version, separated by '.', ...
  10. The app with the same ID has already been installed by your organization's administrator. Check the manifest and change the ...
  11. The application '{0}' specified in -Application parameter is not defined in ProvisioningCache. Valid applications are: Powershell, ...
  12. The application is missing a linked account for RBAC roles, or the linked account has no RBAC role assignments, or the calling ...
  13. The application log on server {0} is correctly configured. The current size is {1} MB. For servers running Exchange, a size ...
  14. The application pool '{4}' is selected for virtual directory '{3}' on server {2}. It's recommended that you select application ...
  15. The application pool '{4}' is selected for virtual directory '{3}' on server {2}. This will cause Direct Push failures. It's ...
  16. The appropriate permissions have been granted for the Lync servers and Administrators to be able to read the UM dial plan ...
  17. The appropriate permissions haven't been granted for the Lync servers and administrators to be able to read the UM dial plan ...
  18. The arbitration mailbox %1 in organization %2 is approaching its quota. The mailbox is currently using %3 bytes of the limit ...
  19. The arbitration mailbox 'SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}' for the organization '{0}' is located on a ...
  20. The arbitration mailbox 'SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}' for the organization '{0}' is located on a ...
  21. The Arbitration mailbox can't be created on server '{0}'. The database must be on a server running Exchange 2010 or a later ...
  22. The archive database ('{0}') is different from its value in AD ('{1}'). Hence a primary only move cannot be allowed for this ...
  23. The archive GUIDs on source '{0}' and target '{1}' recipients don't match. Source archive GUID: {2}, target archive GUID: ...
  24. The argument on parameter 'CustomReponseString' can't be validated because it contains non-ASCII characters. Supply a response ...
  25. The argument on parameter 'TimeInterval' can't be validated. The argument '{0}' does not specify a value that's greater than ...
  26. The argument on the parameter 'Condition' can't be validated. The format of the argument '{0}' isn't valid. See the Help ...
  27. The argument on the parameter 'Condition' can't be validated. When matching headers, 'HeaderName' is a required condition ...
  28. The argument on the parameter 'Condition' can't be validated. When matching headers, 'HeaderValue' is a required condition ...
  29. The argument on the parameter 'ExpireTime' can't be validated. The argument '{0}' doesn't specify a date or time in the future. ...
  30. The attachment filtering configuration couldn't be read from Active Directory. Either the configuration is corrupt, or you ...
  31. The AttachmentSize Limit for the EDiscovery mailbox for Tenant '{0}' seems too low. Please check the MaxSendSize and MaxReceiveSize ...
  32. The attempt to access '%1' failed with error 52 (ERROR_DUP_NAME). Please follow the instructions at http://go.microsoft.com/fwlink/?LinkId=100484 ...
  33. The attempt to unregister from change notifications for virtual directory "%1" under web site "%2" failed. Exception message: ...
  34. The attempt to unregister from message classification change notifications for virtual directory "%1" under web site "%2" ...
  35. The Audio Compression Manager failed to convert from the audio format "%1" to audio format "%2": "%3". If this conversion ...
  36. The Auth Metadata document contains the Identifier '{0}' and Realm '{1}' and Issuer '{2}' information. One or more of these ...
  37. The Auth Metadata document contains the Identifier '{0}' and Realm '{1}' information. One or more of these are different ...
  38. The authentication method for Outlook Web Access virtual directory '{0}' on server {1} which has the Client Access server ...
  39. The authentication method for Outlook Web Access virtual directory '{3}' on server {2} which has the Client Access server ...
  40. The authentication method for the OWA virtual directory '{0}' on server {1}, which has the Client Access server role installed, ...
  41. The auto attendant doesn't have any features enabled, including Operator, key mappings, name lookups, call someone, or send ...
  42. The auto attendant shouldn't be changed to have all options disabled. To disable an auto attendant, use the "Disable-Autoattendant" ...
  43. The auto attendant with ID {0} will be disabled. Calls to the numbers associated with this auto attendant won't be answered. ...
  44. The auto-group ApprovalApplication object wasn't found in organization "{0}". This organization is corrupted. Please contact ...
  45. The Autodiscover request for federation information sent to '{0}' returned an unsecure redirect to '{1}'. If you trust host ...
  46. The Autodiscover service can use a URL in either a long format (example: autodiscover.contoso.com) or in a shorter format ...
  47. The Autodiscover service can't process the given e-mail address. Only mailboxes and contacts can be used for Exchange ActiveSync. ...
  48. The automatic database operation on database {0} was attempted too soon after the previous failure. Manual intervention may ...
  49. The automatic repair operation for database copy '{0}\{1}' will not be run because it has been throttled by the throttling ...
  50. The automatic repair operation for database copy '{0}\{1}' will not be run because one of the prerequisite checks failed. ...
  51. The Automatic Reseed Manager failed to perform an in-place reseed of database copy '{0}\{1}' after multiple attempts over ...
  52. The average '{0}' is beyond the error threshold of {8}% of the reported capacity. The measured value is {9}. The measured ...
  53. The average disk write latency on {0} has been higher than {1}ms for {2} hours. The disk cache has been reset and event (387) ...
  54. The average of the most recent heartbeat intervals %1 for request %2 used by clients is less than or equal to %3]. Make sure ...
  55. The average time to synchronize a folder during a successful request in seconds. This time includes both synchronous and ...
  56. The average value of '{0}' is {9}, which is greater than the threshold of {8}. The transaction log drive may be a bottleneck. ...
  57. The average value of '{0}' is {9}, which is greater than the threshold value of {8}. The log disk drive may be a bottleneck. ...
  58. The average value of '{0}' is {9}, which is greater than the threshold value of {8}. The transaction log drive may be a bottleneck. ...
  59. The average value of '{0}' is {9}, which is higher than the recommended maximum of {8}. This indicates the server has a processor ...
  60. The average value of '{0}' should always be below {8}%, and ideally should average below {7}%. The measured value is {9}%. ...
  61. The average value of '{0}' should always be below {8}%. The measured value is {9}%. This indicates the server has a processor ...
  62. The average value of '{0}' should be less than {8}% on a back-end server. Actual measured processor usage is {9}%. If this ...
  63. The average value of '{0}' should be less than {8}. The measured value is {9}. This indicates the server has a processor ...
  64. The average wait time, in milliseconds, for a queued scan request. This indicates the average time a scan request waits in ...
  65. The Away greeting is played to callers who ask to leave a message when automatic replies are turned on. If you don't record ...
  66. The background scan of the transport queue database has been stopped. %1 message(s) loaded so far. There are %2 other messages ...
  67. The BackgroundDatabaseMaintenance parameter change will not be applied on this database before it's remounted. Dismount and ...
  68. The backup database %4 must be a multiple of 4 KB. For more information, click http://www.microsoft.com/contentredirect.asp. ...
  69. The backup has been stopped because it was halted by the client or the connection with the client failed. For more information, ...
  70. The backup has been stopped prematurely (possibly because the instance is terminating). For more information, click http ...
  71. The backup procedure has been successfully completed. For more information, click http://www.microsoft.com/contentredirect.asp. ...
  72. The basic input/output system (BIOS) on server {2} (model {0}) requires an update. Data corruption may result if the BIOS ...
  73. The BccSuspiciousOutboundAdditionalRecipients value is not set. Notifications for suspicious outbound email messages cannot ...
  74. The beta feature %4 is enabled in %5 due to the beta site mode settings %6. For more information, click http://www.microsoft.com/contentredirect.asp. ...
  75. The bootstrap account specified in the subscription file indicates it will expire in the next 5 minutes. To ensure proper ...