Exchange Server 2016

  1. Microsoft Exchange System Attendant does not have sufficient rights to read Exchange configuration objects in Active Directory. ...
  2. Microsoft Exchange System Attendant failed to add the local computer as a member of the DS group object '%1'. Please stop ...
  3. Microsoft Exchange System Attendant failed to read the membership of group '%1'. Error code '%2'. Please check whether the ...
  4. Microsoft Exchange System Attendant failed to read the membership of the universal security group '%1'; the error code was ...
  5. Microsoft Exchange System Attendant has detected a discrepancy in the published security data for Exchange server '%1'. This ...
  6. Microsoft Exchange System Attendant has detected that the local computer '%1' is not a member of group '%2'.System Attendant ...
  7. Microsoft Exchange System Attendant has detected that the password of the legacy Exchange service account has been modified. ...
  8. Microsoft Exchange System Attendant has detected that the system attendant object in the DS has been modified.System Attendant ...
  9. Microsoft Exchange System Attendant is querying for Outlook Anywhere back-ends to reset RPC Proxy Valid Ports. Config DC='%1' ...
  10. Microsoft Exchange System Attendant was unable to find the Exchange server object named '%1' in Active Directory. All known ...
  11. Microsoft Exchange Transport is rejecting message submissions because the available disk space has dropped below the configured ...
  12. Microsoft Exchange versions earlier than Exchange Server 2003 do not support Outlook Anywhere. The following servers cannot ...
  13. Microsoft Exchange versions earlier than Exchange Server 2013 do not support the Negotiate client authentication method. ...
  14. Microsoft Exchange VSS Writer failed with error %1 when collecting database information for '%2' in preparation for backup. ...
  15. Microsoft Exchange was unable to initialize the Content Filter agent. Check the access control lists (ACLs) on the files ...
  16. Microsoft Exchange was unable to initialize the Content Filter agent. It could not allocate sufficient memory for an internal ...
  17. Microsoft Exchange was unable to initialize the Content Filter agent. Notification of the file system change could not be ...
  18. Microsoft Filter Pack isn't installed on server {0}. The Microsoft Filter Pack is necessary to index and search Microsoft ...
  19. Microsoft Forefront Security 2010 for Exchange Server is running on Exchange server {0} with reverse DNS lookup enabled. ...
  20. Microsoft Forefront Security 2010 for Exchange Server is running on Exchange server {0} without reverse DNS lookup enabled. ...
  21. Microsoft Office 365 Best Practices Analyzer Beta 1.0 can allow you enter alternate credentials to run the on-premises checks. ...
  22. Modifying CompleteAfter within a short period of time before the original CompleteAfter may not take affect. Settings propagate ...
  23. Monitoring is not enabled for database {0}. Last reported monitoring (AutoDagExcludeFromMonitoring) state is {Probe.StateAttribute3} ...
  24. Monitoring item '{0}' of type '{1}' already has an override '{2}' applied for all target resources. Please remove the existing ...
  25. Monitoring item '{0}' of type '{1}' already has an override '{2}' applied for specific target resource(s). Please remove ...
  26. Monitoring item '{1}' of type '{2}' already has an override applied for Property '{0}'. Please remove the existing override ...
  27. More than 500 mailboxes in the entire forest have delivery restrictions set where at least one distribution group is used ...
  28. More than 8 logical processors exist on Exchange server {0}. If this server has more than 8 physical processors installed, ...
  29. More than 8 logical processors exist on Exchange server {2}. If this server has more than 8 physical processors installed, ...
  30. More than 8 processors were detected for the Exchange server {2}. If this server has more than 8 physical processors installed ...
  31. More than 8 processors were detected for the Exchange server {2}. If this server has more than 8 physical processors installed, ...
  32. More than 800 address lists exist in the organization '{0}'. If the Recipient Update Service is responsible for these, severe ...
  33. More than 800 address lists exist in the organization. If the Recipient Update Service is responsible for these, severe latencies ...
  34. More than 800 global address lists exist in the organization '{0}'. If the Recipient Update Service is responsible for these, ...
  35. More than 800 global address lists exist in the organization. If the Recipient Update Service is responsible for these, severe ...
  36. More than one accepted domain was found when searching for '{0}'. The following accepted domains were found: {1} and {2}. ...
  37. More than one Active Directory object is configured with the recipient address %1. Messages to this recipient will be deferred ...
  38. More than one administrator audit log configuration was found for the organization '{0}'. This may be caused by a replication ...
  39. More than one computer account in Active Directory has '{5}' set to '{3}'. This will result in Kerberos authentication failures ...
  40. More than one computer account in Active Directory has '{5}' set to '{3}'. This will result in Kerberos authentication failures ...
  41. More than one IIS Web service extension was found with the group ID {0} and the file {1}. Please remove the duplicate entries ...
  42. More than one mailbox plan is marked as default. Use Set-MailboxPlan to make sure that only one mailbox plan is marked as ...
  43. More than one network interface on server {0} has a default IP gateway listed. Communication errors may occur if these network ...
  44. More than one network interface on server {2} has a default IP gateway listed. Communication errors may occur if these network ...
  45. More than one organization mailbox was found that has 'UMDataStorage' capability: {0}, {1}. Only one organization mailbox ...
  46. More than one UM IP gateway object has been resolved to the same IP address. Modify the configuration so that each UM IP ...
  47. More than two connectors were found in ManagementAgent %1 for MetaVerse object %2. This could be because of invalid changes ...
  48. More than {0} results were found given the specified search criteria. Please have more restriction on your search criteria. ...
  49. More than {6}% of the messages in the '{4}' queue on server {2} appear to be addressed to distribution group '{3}'. The number ...
  50. More than {6}% of the messages in the '{4}' queue on server {2} appear to be addressed to server {1}. The number of such ...
  51. More than {6}% of the messages in the '{4}' queue on server {2} appear to be addressed to the mailbox store '{3}'. The number ...
  52. More than {6}% of the messages in the '{4}' queue on server {2} appear to be addressed to the public folder '{3}'. The number ...
  53. More than {6}% of the messages in the '{4}' queue on server {2} appear to be addressed to the public folder store '{3}'. ...
  54. More than {6}% of the messages in the '{4}' queue on server {2} appear to be addressed to user '{1}'. The number of such ...
  55. More than {8} Exchange mailbox stores exist in the organization. To avoid logon issues with Outlook Web Access, install the ...
  56. More than {8} Exchange servers exist in the organization. Exchange is limited to {1} total servers. Current number of Exchange ...
  57. More than {8} messaging connectors exist in the organization. This may cause additional load on Exchange and Active Directory ...
  58. Most common possible causes are 1)The message contains more than 250 attachments. More than 250 attachments cause the MAPI_E_TOO_BIG ...
  59. Most of the RPC load is in the category '{1}'. This category accounts for {2} RPC operations/second, out of the total rate ...
  60. Mount for database '{0}' failed due to timeout after {2} seconds on server '{1}'. Disk or controller issues may cause slow ...
  61. Mount point '{0}' on server {1} doesn't have a recommended amount of free disk space. Total: {2} GB of free space, which ...
  62. Move Collection Commands/sec is the number of MoveCollection commands that are processed each second. Clients that are running ...
  63. Move Collection Total is the total number of MoveCollections requests that have been processed since the service was started. ...
  64. Move for database '{0}' was suppressed because too many moves have happened recently. {1} moves have happened within {2}. ...
  65. Move for database '{0}' was suppressed due to a blackout between '{1}'UTC and '{2}'UTC. {3} previous moves have happened ...
  66. Move for mailbox '{0}' is stalled because DataMoveReplicationConstraint is not satisfied for the database '{1}' (agent {3}). ...
  67. Move for mailbox {0} has been postponed because the remote forest doesn't have enough resources to process the move. The ...
  68. Move Items Commands/sec is the number of MoveItems commands that are processed each second. Clients use this command to move ...
  69. Move request '{0}' is an offline mailbox move request. Only online mailbox move requests can be suspended automatically when ...
  70. Move-ActiveMailboxDatabase was called for server '{0}' with skip options, but ActivateOnServer is not specified (SkipClientExperienceChecks={1}, ...
  71. Move-DatabasePath is not allowed for replicated databases. For detailed steps to change the location of a replicated database, ...
  72. MoveFolder Average Response Time is the average elapsed time (in milliseconds) between the beginning and end of a MoveFolder ...
  73. MoveFolder Successful Requests is the total number of successful requests for the MoveFolder web method since the service ...
  74. MoveItem Average Response Time is the average elapsed time (in milliseconds) between the beginning and end of a MoveItem ...
  75. MoveItem Successful Requests is the total number of successful requests for the MoveItem web method since the service was ...