Exchange Server 2010

  1. The maximum incoming message size maybe set too low. An administrative error may have occurred. Maximum message size is {9} ...
  2. The maximum latency (measured in microseconds) from the time the log file was generated until it was delivered to the Microsoft ...
  3. The maximum latency (measured in microseconds) from the time the log file was generated until it was sent on the network ...
  4. The maximum LDAP page size for the default query policy is set too high and may cause performance problems. The default of ...
  5. The maximum measured latency (in milliseconds) of this copy relative to the active copy. This value is only valid when running ...
  6. The maximum non-paged pool memory on server {2} is over the error threshold of {8} MB. System instability may occur. Current ...
  7. The maximum non-paged pool memory on server {2} is over the error threshold of {8} MB. This may cause system instability. ...
  8. The maximum non-paged pool memory on server {2} is over the warning threshold of {8} MB. System instability may occur. Current ...
  9. The maximum non-paged pool memory on server {2} is over the warning threshold of {8} MB. This may cause system instability. ...
  10. The maximum number of cached views ('msExchMaxCachedViews') for database {3} on server {2} is set too low. This can cause ...
  11. The maximum number of cached views (msExchMaxCachedViews) for database {3} on server {2} is set too high. This can cause ...
  12. The maximum number of Extensible Storage Engine (ESE) open tables for storage group '{3}' on server {2} is hard-coded. This ...
  13. The maximum number of recipients is limited to {0}. There are currently {1} recipients. Remove {2} recipients and try again. ...
  14. The maximum number of recipients of each type to return. The four types are: User, Contact, Group, and DynamicDistributionGroup. ...
  15. The maximum number of values that can be retrieved from a multi-valued attribute in a single LDAP query for policy '{3}' ...
  16. The maximum outgoing message size is set too high. This can cause reliability problems. Current maximum message size is {9} ...
  17. The maximum outgoing message size maybe set too low. An administrative error may have occurred. Current maximum message size ...
  18. The maximum outgoing message size maybe set too low. An administrative error may have occurred. Maximum message size is {9} ...
  19. The maximum value of '{0}' is {9}, which is greater than the threshold of {8}. The transaction log drive may be a bottleneck. ...
  20. The MaxRequestBytes HTTP parameter on server {2} has not been set to 32768. In large environments the absence of this value ...
  21. The meeting message couldn't be correlated because the target is a repeating master and the meeting message is an occurrence. ...
  22. The meeting will be permanently deleted. The attendees will not be notified that you canceled the meeting. Are you sure you ...
  23. The meeting will be permanently deleted. The attendees won't be notified that you canceled the meeting. Do you want to delete ...
  24. The member "{1}" can't be removed from the "{0}" management role group. The "{0}" role group can't be empty because it holds ...
  25. The member "{1}" can't be removed from the "{0}" management role group. The "{0}" role group can't be empty, because it holds ...
  26. The MemberDepartRestriction property value of group "{0}" is "ApprovalRequired", which is currently not supported. Only "Open" ...
  27. The membership depart restriction of the group "{0}" is set to closed because there is no arbitration mailbox within the ...
  28. The membership join restriction of the group "{0}" is set to closed because there is no arbitration mailbox within the organization ...
  29. The message classification settings couldn't be read from Active Directory for virtual directory "%1" under web site "%2". ...
  30. The message classification settings couldn't be read from Active Directory for virtual directory "%1" under web site "%2". ...
  31. The message could not be delivered because you do not have create permissions on this folder or it is only available to folder ...
  32. The message could not be delivered because you do not have create permissions on this folder or it is only available to folder ...
  33. The message could not be received from domain-secured domain %1 because of a configuration error on Receive connector %2. ...
  34. The message could not be received from domain-secured domain %1 because of a configuration error on Receive connector %2. ...
  35. The message could not be redirected to an alternate-recipient because that recipient had previously redirected the message ...
  36. The message could not be redirected to an alternate-recipient because that recipient had previously redirected the message ...
  37. The message couldn't be created because one of the contacts couldn't be found. The contact may have been moved or deleted. ...
  38. The message couldn't be delivered because the recipient's destination e-mail system is unknown or invalid. Check the address ...
  39. The message couldn't be delivered because the recipient's destination e-mail system is unknown or invalid. Check the address ...
  40. The message failed to be submitted because the storage limit for the mailbox that is submitting the message has been exceeded. ...
  41. The message failed to be submitted because the storage limit for the mailbox that is submitting the message has been exceeded. ...
  42. The message for user {0} will be deleted from the Unified Messaging pipeline because the pipeline is full. This could be ...
  43. The message has been queued on server '{0}' since {1} {3}. The last attempt to send the message was at {2} {3} and generated ...
  44. The message in the queue has expired. The sending server tried to relay or deliver the message, but the action was not completed ...
  45. The message in the queue has expired. The sending server tried to relay or deliver the message, but the action was not completed ...
  46. The message in the queue has expired. The server responsible for sending the message tried to relay or deliver it, but the ...
  47. The message is longer than the limit for text messages set by your administrator. For assistance, please contact your helpdesk. ...
  48. The message is too large for the local quota. For example, a remote Exchange user may have delivery restrictions set with ...
  49. The message reached the recipient's e-mail system, but delivery was refused. Try resending the message. If delivery is refused ...
  50. The message reached the recipient's e-mail system, but delivery was refused. Try resending the message. If delivery is refused ...
  51. The message submitted by '{4}' to '{3}' appears to be stuck on Exchange gateway server {2}. Further analysis is necessary ...
  52. The message submitted by '{4}' to '{3}' appears to be stuck on non-gateway server {2}. Further analysis is necessary to determine ...
  53. The message submitted by '{4}' to '{3}' was routed outside the Exchange organization by server {2} whereas the specified ...
  54. The message submitted by '{4}' was delivered successfully to recipient '{3}'. It appears that this message was not addressed ...
  55. The message transfer agent (MTA) configuration parameter '{4}' on server {2} is set too low and may cause mail flow issues. ...
  56. The message transfer agent (MTA) diagnostic logging level on server {2} is greater than 5. As such, the service is in debugging ...
  57. The message transfer agent (MTA) diagnostic logging level on server {2} is set to a non-zero value. This level is used for ...
  58. The Message Waiting Indicator Assistant failed to deliver the MWI notification '%1/%2 (unread/read)' for the UM-enabled mailbox ...
  59. The Message Waiting Indicator Assistant failed to deliver the MWI notification '%1/%2 (unread/read)' for the UM-enabled mailbox ...
  60. The Message Waiting Indicator Assistant was unable to obtain the MWI state for mailbox '%1' on database '%2'. You can safely ...
  61. The Message Waiting Indicator Assistant was unable to obtain the MWI state for mailbox '%1' on database '%2'. You can safely ...
  62. The Message Waiting Indicator Assistant was unable to query the mailbox database '%1'. The MWI assistant will try to query ...
  63. The Message Waiting Indicator Assistant was unable to query the mailbox database '%1'. The MWI assistant will try to query ...
  64. The message was not delivered because of Administrator action through the queue viewer interface in Exchange System Manager. ...
  65. The message was received by an e-mail system running an older version of your e-mail software. This is the farthest that ...
  66. The message was rejected by a rule set at the organization level. For more information, check your organization's Transport ...
  67. The message was relayed to the destination {0} in your organization. However, it didn't arrive and no further information ...
  68. The message was removed from your mailbox and redirected to the delegate that you selected in your Delegate Access settings. ...
  69. The message was transferred from {0} to server {1}, which has an older version of the email system. This is the farthest ...
  70. The message was transferred to another part of your organization's e-mail system. Final delivery couldn't be confirmed at ...
  71. The message was undeliverable because the recipient specified has changed address permanently and forwarding was not applicable ...
  72. The message was undeliverable because the recipient specified has changed address permanently and forwarding was not applicable ...
  73. The message was undeliverable because the recipient specified has changed address temporarily (departed) and forwarding was ...
  74. The message was undeliverable because the recipient specified has changed address temporarily (departed) and forwarding was ...
  75. The message was undeliverable because the recipient specified has changed address temporarily (on travel) and forwarding ...