Exchange Server 2016

  1. The maximum Extensible Storage Engine (ESE) cache on server {2} is set too high and is causing low virtual memory conditions. ...
  2. The maximum incoming message size is set too high. This can cause reliability problems. Current maximum message size is {9} ...
  3. The maximum incoming message size maybe set too low. An administrative error may have occurred. Current maximum message size ...
  4. The maximum incoming message size maybe set too low. An administrative error may have occurred. Maximum message size is {9} ...
  5. The maximum LDAP page size for the default query policy is set at a recommended level. The default of 1000 is recommended. ...
  6. The maximum LDAP page size for the default query policy is set too high and may cause performance problems. The default of ...
  7. The maximum LDAP page size for the default query policy is set too high. If this value is set too high, it can cause performance ...
  8. The maximum non-paged pool memory on server {2} is over the error threshold of {8} MB. System instability may occur. Current ...
  9. The maximum non-paged pool memory on server {2} is over the error threshold of {8} MB. This may cause system instability. ...
  10. The maximum non-paged pool memory on server {2} is over the warning threshold of {8} MB. System instability may occur. Current ...
  11. The maximum non-paged pool memory on server {2} is over the warning threshold of {8} MB. This may cause system instability. ...
  12. The maximum number of bytes that a Live Views web sandbox fetch (HTML, JSS, or CSS) can have in the transformation pipeline. ...
  13. The maximum number of cached views ('msExchMaxCachedViews') for database {3} on server {2} is set too low. This can cause ...
  14. The maximum number of cached views (msExchMaxCachedViews) for database {3} on server {2} is set too high. This can cause ...
  15. The maximum number of Extensible Storage Engine (ESE) open tables for storage group '{3}' on server {2} is hard-coded. This ...
  16. The maximum number of Html elements allowed in a web sandbox document. Each element includes a begin tag and a potentially ...
  17. The maximum number of incremental syncs, {0}, must be less than the maximum number of concurrent migrations, which is currently ...
  18. The maximum number of recipients of each type to return. The four types are: User, Contact, Group, and DynamicDistributionGroup. ...
  19. The maximum number of values that can be retrieved from a multi-valued attribute in a single LDAP query for policy '{3}' ...
  20. The maximum outgoing message size is set too high. This can cause reliability problems. Current maximum message size is {9} ...
  21. The maximum outgoing message size maybe set too low. An administrative error may have occurred. Current maximum message size ...
  22. The maximum outgoing message size maybe set too low. An administrative error may have occurred. Maximum message size is {9} ...
  23. The maximum value of '{0}' is {9}, which is greater than the threshold of {8}. The transaction log drive may be a bottleneck. ...
  24. The maximum {0} message size is set too low for your Exchange organization '{1}'. Current maximum message size is {2} KB. ...
  25. The maximum {0} message size isn't set correctly for your Exchange organization '{1}'. Improperly configuring your message ...
  26. The MaxRequestBytes HTTP parameter on server {0} hasn't been set to 32768. In large environments the absence of this value ...
  27. The MaxRequestBytes HTTP parameter on server {2} has not been set to 32768. In large environments the absence of this value ...
  28. The meeting is out of date. The calendar response couldn't be processed but a message with the response content was sent ...
  29. The meeting message couldn't be correlated because the target is a repeating master and the meeting message is an occurrence. ...
  30. The member "{1}" can't be removed from the "{0}" management role group. The "{0}" role group can't be empty because it holds ...
  31. The member "{1}" can't be removed from the "{0}" management role group. The "{0}" role group can't be empty, because it holds ...
  32. The member count "{0}" of the distribution group "{1}" from tenant "{2}" exceeds the threshold. It will be skipped for out-of-band ...
  33. The MemberDepartRestriction property value of group "{0}" is "ApprovalRequired", which is currently not supported. Only "Open" ...
  34. The membership depart restriction of the group "{0}" is set to closed because there is no arbitration mailbox within the ...
  35. The membership join restriction of the group "{0}" is set to closed because there is no arbitration mailbox within the organization ...
  36. The message classification settings couldn't be read from Active Directory for virtual directory "%1" under web site "%2". ...
  37. The message could not be received from domain-secured domain %1 because of a configuration error on Receive connector %2. ...
  38. The message expiration policy can't be retrieved because the approval process hasn't started. The ModeratedRecipient retention ...
  39. The message for user {0} will be deleted from the Microsoft Exchange Unified Messaging service message pipeline on the Mailbox ...
  40. The message in the queue has expired. The sending server tried to relay or deliver the message, but the action was not completed ...
  41. The message in the queue has expired. The sending server tried to relay or deliver the message, but the action was not completed ...
  42. The message in the queue has expired. The server responsible for sending the message tried to relay or deliver it, but the ...
  43. The message is longer than the limit for text messages set by your administrator. For assistance, please contact your email ...
  44. The message is too large for the local quota. For example, a remote Exchange user may have delivery restrictions set with ...
  45. The message rejection text and custom status code that you created are ignored because you have configured the policy to ...
  46. The message submitted by '{4}' to '{3}' appears to be stuck on Exchange gateway server {2}. Further analysis is necessary ...
  47. The message submitted by '{4}' to '{3}' appears to be stuck on non-gateway server {2}. Further analysis is necessary to determine ...
  48. The message submitted by '{4}' to '{3}' was routed outside the Exchange organization by server {2} whereas the specified ...
  49. The message submitted by '{4}' was delivered successfully to recipient '{3}'. It appears that this message was not addressed ...
  50. The message transfer agent (MTA) configuration parameter '{4}' on server {2} is set too low and may cause mail flow issues. ...
  51. The message transfer agent (MTA) diagnostic logging level on server {2} is greater than 5. As such, the service is in debugging ...
  52. The message transfer agent (MTA) diagnostic logging level on server {2} is set to a non-zero value. This level is used for ...
  53. The Message Waiting Indicator Assistant failed to deliver the MWI notification '%1/%2 (unread/read)' for the UM-enabled mailbox ...
  54. The Message Waiting Indicator Assistant was unable to obtain the MWI state for mailbox '%1' on database '%2'. You can safely ...
  55. The Message Waiting Indicator Assistant was unable to query the mailbox database '%1'. The MWI assistant will try to query ...
  56. The message was not delivered because of Administrator action through the queue viewer interface in Exchange System Manager. ...
  57. The message you tried to open is protected with Information Rights Management but it can't be viewed because it's corrupted. ...
  58. The message you tried to open is protected with Information Rights Management. Pre-licensing failed. Try opening the message ...
  59. The message you tried to open is protected with Information Rights Management. The Rights Management server isn't available ...
  60. The message you tried to open is protected with Information Rights Management. The RMS server isn't set up correctly. To ...
  61. The message you tried to open is protected with Information Rights Management. The sender didn't give you the rights necessary ...
  62. The messaging notifications payload size has grown too large for user "%1". The notifications infrastructure is either not ...
  63. The Microsoft Distributed Transaction Coordinator (MSDTC) resource appears to be missing from cluster server {2}. This may ...
  64. The Microsoft Distributed Transaction Coordinator (MSDTC) resource currently running on cluster node {2} is set to affect ...
  65. The Microsoft Exchange Active Directory Topology service on server {0} did not return any suitable domain controllers for ...
  66. The Microsoft Exchange Active Directory Topology service on server {0} did not return any suitable global catalog for forest ...
  67. The Microsoft Exchange Active Directory Topology service on server {2} is hard-coded to use the following Active Directory ...
  68. The Microsoft Exchange Address Book service couldn't find the local server object in Active Directory. The service will stop. ...
  69. The Microsoft Exchange Background Audit Search servicelet completed an Audit Log search. The host process ID is %1. The search ...
  70. The Microsoft Exchange Background Audit Search servicelet initiated an Audit Log search. The host process ID is %1. The search ...
  71. The Microsoft Exchange Chat resource is running on this node. You must failover the Microsoft Exchange Chat resource to at ...
  72. The Microsoft Exchange component specified is configured to use circular database logs.It cannot be backed up without a full ...
  73. The Microsoft Exchange DAG Management service provides storage management and database layout management functionality for ...
  74. The Microsoft Exchange Event service is running on server {2}. Exchange Server 2007 does not support this facility. This ...
  75. The Microsoft Exchange Forward Sync Service '%1' could not push data to Insights Engine as queue is full. Data will be dropped. ...