Exchange Server 2010

  1. The Mailbox Search Service is unavailable on server: '{0}'. Please make sure 'Microsoft Exchange Mailbox Assistants' is running ...
  2. The Mailbox server %1 that hosts the mailbox for mobile phone user %2 is running version %3]. Exchange ActiveSync only supports ...
  3. The Mailbox server %1 that hosts the mailbox for mobile phone user %2 is running version %3]. Exchange ActiveSync only supports ...
  4. The Mailbox server resource pool limit of %1 has been reached. This may be due to resources not being properly released after ...
  5. The Mailbox server role provides e-mail storage and advanced scheduling services. The Mailbox server role also includes public ...
  6. The mailbox specified, '{0}', isn't valid. Check to be sure the user exists and is UM-enabled in the same dial plan as this ...
  7. The mailbox store '{3}' on server {2} is {9} GB in size. Standard Editions of Microsoft Exchange Server 2003 Service Pack ...
  8. The mailbox store '{3}' on server {2} is {9} GB in size. Standard editions of Microsoft Exchange Server are limited to a ...
  9. The mailbox store '{3}' on server {2} is {9} GB in size. Standard Editions of Microsoft Exchange Server are limited to a ...
  10. The mailbox that you specified is connected to "{0}". Only disconnected mailboxes can be reconnected. Specified mailbox: ...
  11. The mailbox you requested couldn't be opened because no match was found for the address "{0}". Make sure the address is spelled ...
  12. The mailbox you specified couldn't be found. Close the dialog box and try to find the mailbox again. Make sure you've typed ...
  13. The mailbox you're trying to access isn't available. The host name entry should be in the format "http :// : ]/owa", but ...
  14. The mailbox {0} can't be one of the mailboxes that you search or the mailbox in which results are saved. Select a different ...
  15. The mailbox's dial plan in the source forest is of type '{0}'. However, the matching dial plan in the target forest is of ...
  16. The major version for routing group '{3}' appears to be changing very rapidly on server {2} ({9} version change(s) detected ...
  17. The major version for routing group '{3}' has been changed on server {2} while the tool was running. Latest major version ...
  18. The major version for routing group '{3}' may be changing rapidly on server {2} ({9} version change(s) detected over {8} ...
  19. The major version of the server is {0}. However, a Client Access server with the same major version as the Mailbox server, ...
  20. The managed folder assistant audit log is enabled, but the path to the audit log is missing in Active Directory. Current ...
  21. The managed folder assistant could not configure the audit log. It will stop processing the current database: '%1'. It will ...
  22. The managed folder assistant could not configure the audit log. It will stop processing the current database: '%1'. It will ...
  23. The Managed Folder Assistant detected a circular reference in Managed Content Settings in mailbox '{0}' that will enforce ...
  24. The managed folder assistant detected a cycle among the policies in mailbox %1 that will enforce retention by moving items ...
  25. The managed folder assistant detected a cycle among the policies in mailbox %1 that will enforce retention by moving items ...
  26. The managed folder assistant did not write to the audit log. It will stop processing the current database: '%1'. It will ...
  27. The managed folder assistant did not write to the audit log. It will stop processing the current database: '%1'. It will ...
  28. The managed folder assistant failed to provision mailbox %1 because of damaged data in Active Directory. Exception details: ...
  29. The managed folder assistant failed to provision mailbox %1 because of damaged data in Active Directory. Exception details: ...
  30. The managed folder assistant skipped processing all databases on the local server because it could not read the audit log ...
  31. The managed folder assistant skipped processing all databases on the local server because it could not read the audit log ...
  32. The managed folder assistant skipped processing all databases on the local server because the audit log is enabled but the ...
  33. The managed folder assistant skipped processing all databases on the local server because the audit log is enabled but the ...
  34. The managed folder assistant was unable to create the managed root folder %1 in mailbox %2 because the mailbox has several ...
  35. The managed folder assistant was unable to create the managed root folder %1 in mailbox %2 because the mailbox has several ...
  36. The managed folder assistant will not process mailboxes on this server because one or more managed folders in Active Directory ...
  37. The managed folder assistant will not process mailboxes on this server because one or more managed folders in Active Directory ...
  38. The managed folder mailbox policy '{0}' for the mailbox '{1}' is invalid because it is linked to more than one managed default ...
  39. The managed folder mailbox policy '{0}' is invalid because it is linked to more than one default managed folder of the same ...
  40. The ManagedContentSetting {0} was upgraded from {1}. The MessageClass on this ManagedContentSetting is now set to "*". Please ...
  41. The management role "{0}" can't be assigned to the role assignment policy because it isn't an end-user role. Only end-user ...
  42. The management role "{0}" couldn't be upgraded. Consider removing this role and associated role assignments when the entire ...
  43. The management role "{0}" couldn't be upgraded. Consider removing this role and associated role assignments when the entire ...
  44. The management role "{0}" couldn't be upgraded. Remove the role and associated role assignments using Active Directory tools ...
  45. The management role "{0}" couldn't be upgraded. Remove the role and associated role assignments using Active Directory tools ...
  46. The management role "{0}" is in the process of being deprecated. New role assignments referring this role aren't allowed. ...
  47. The management role 'Role Management' should be assigned (with a delegating role assignment) to one security group with members. ...
  48. The management role 'Role Management' should be assigned (with a regular role assignment) to one security group with members. ...
  49. The management role '{0}' can't be renamed to '{1}' because there is already a root role or Administrative role with the ...
  50. The management role assignment "{0}" couldn't be created. The role group "{1}" and its management role assignments have been ...
  51. The management role assignment "{0}" is invalid and can't be automatically upgraded. Consider removing this role assignment ...
  52. The management role assignment {0} is associated with a policy; however, its RoleAssigneeType isn't RoleAssignmentPolicy. ...
  53. The management role assignment {0} is associated with a policy; however, its RoleAssignmentDelegationType isn't Regular. ...
  54. The management role assignment {0} isn't associated with a management role. The management role might have been deleted. ...
  55. The management role assignment {0} isn't associated with a role group, assignment policy, user, or universal security group. ...
  56. The management role assignments "{0}" and "{1}" have conflicting domain or configuration scopes. The reason for this error ...
  57. The management role entry "{0}" is invalid for the current role. Only management roles of type '{1}' can contain {2} management ...
  58. The management role name "{0}" is invalid because it either contains commas or it's empty. Remove any commas that are in ...
  59. The MAPI interface for Active Directory is disabled on server {2}. Microsoft Office Outlook clients will not be able to contact ...
  60. The MAPI property type with property tag (0x{0:x4}) doesn't match the MAPI property type found for this property in the Active ...
  61. The masquerade domain '{1}' configured for SMTP virtual server '{3}' on server {2} is also defined as an SMTP address in ...
  62. The master category list can't be saved because it is too large: {0} bytes. The maximum allowed size is {1} bytes. Delete ...
  63. The MasterServerOrAvailabilityGroup property for database copy '{0}' contains an invalid value. This may be due to a corrupted ...
  64. The max hop count was exceeded for the message. This code may occur if a loop situation exists between a sending server and ...
  65. The Max number of retries to load resolver configuration data on startup has been reached. The Microsoft Exchange Transport ...
  66. The MaxDSNSize registry value has not been set on server {2}. Implementing this option can increase overall performance and ...
  67. The MaxFieldLength HTTP parameter on server {2} has not been set to 32768. In large environments, the absence of this value ...
  68. The maximum allowable incoming message size ({8} KB) does not match the outgoing size ({9} KB). These values should be the ...
  69. The maximum database cache size is {9} on server {2}. The recommended database cache size on Edge Transport servers that ...
  70. The maximum database cache size is {9} on server {2}. The recommended database cache size on Hub Transport servers that have ...
  71. The maximum download size per item for transport synchronization should be less than the maximum download size per connection. ...
  72. The maximum Extensible Storage Engine (ESE) cache on server {2} has been increased and may cause low virtual memory conditions. ...
  73. The maximum Extensible Storage Engine (ESE) cache on server {2} is set too high and is causing low virtual memory conditions. ...
  74. The maximum incoming message size is set too high. This can cause reliability problems. Current maximum message size is {9} ...
  75. The maximum incoming message size maybe set too low. An administrative error may have occurred. Current maximum message size ...