Exchange Server 2016

  1. The action '{1}', '{2}', may not be performed on the management role group '{0}' with capablity '{3}'. Membership of a partner ...
  2. The action couldn't be completed because the Microsoft Exchange Information Store service is unavailable. Be sure the service ...
  3. The action you are trying to configure already exists for this locale. You can only apply each action one time for each locale. ...
  4. The activation of all modules took longer than expected to complete. Total Load Time: %1 Total Start Time: %2 Breakdown:%3 ...
  5. The active copy of %1 has a missing or corrupted log file (%2). As a result, existing log files and any partial data will ...
  6. The active copy of %1 has a missing or corrupted log file (%2). To keep this copy healthy, replication will restart at generation ...
  7. The Active Directory configuration for database copy '{0}\{1}' appears to be invalid or corrupted. Verify the health of this ...
  8. The Active Directory configuration indicates that server '{0}' is a member of database availability group '{1}', which can't ...
  9. The Active Directory Connector (ADC) software on server {2} is from Exchange Server 2003 (initial release). A more recent ...
  10. The Active Directory Connector (ADC) software on server {2} is from Exchange Server 2003 Service Pack 1. A more recent version ...
  11. The Active Directory Connector server {2} is down or unreachable. This error could also be the result of a network or permissions ...
  12. The Active Directory domain configuration version ({0}) is higher than Setup's version({1}). Therefore, PrepareDomain can't ...
  13. The Active Directory forest functionality level has been raised. A modification to recipient policy '{3}' is required to ...
  14. The Active Directory forest functionality level has been raised. A modification to the system policies is required to avoid ...
  15. The Active Directory forest is prepared for Windows Server 2003. To avoid incorrect e-mail address generation when the forest ...
  16. The Active Directory forest is prepared for Windows Server 2003. To avoid mailbox re-homing issues when the forest is upgraded ...
  17. The Active Directory Lightweight Directory Services (AD LDS) instance uninstallation process {0} failed with error code {1}. ...
  18. The Active Directory object for Recipient Update Service '{3}' is in conflict with another object. This may cause duplicate ...
  19. The Active Directory object for virtual directory '{1}' on '{0}' could not be created. This might be because the object already ...
  20. The Active Directory operation has responded after %1 seconds in service instance '%3'. The response is slower than expected. ...
  21. The Active Directory organization configuration version ({0}) is higher than Setup's version({1}). Therefore, PrepareAD can't ...
  22. The Active Directory page information in the cookie can only be used against the originating domain controller. Please retry ...
  23. The Active Directory property "msExchMetabasePath" for the Exchange ActiveSync virtual directory named "{0}" is set to "{1}", ...
  24. The Active Directory property "msExchMetabasePath" for the Exchange ActiveSync virtual directory named "{0}" is set to "{1}", ...
  25. The Active Directory property "msExchMetabasePath" for the Outlook Web App virtual directory named "{0}" is set to "{1}", ...
  26. The Active Directory property "msExchMetabasePath" for the Outlook Web App virtual directory named "{0}" is set to "{1}", ...
  27. The Active Directory schema is not up-to-date. You must run setup with the "/ForestPrep" switch. If you have already done ...
  28. The Active Directory schema isn't up-to-date and the Active Directory management tools aren't installed on this computer. ...
  29. The Active Directory schema isn't up-to-date, and this user account isn't a member of the 'Schema Admins' and/or 'Enterprise ...
  30. The Active Directory schema version ({0}) is higher than Setup's version ({1}). Therefore, PrepareSchema can't be executed. ...
  31. The Active Directory schema will need to be upgraded (via the /PrepareSchema switch of Exchange Server 2007 setup) before ...
  32. The Active Directory site for Exchange server %1 was not determined in routing tables with timestamp %2. Recipients will ...
  33. The Active Directory split permissions security model is typically used by large organizations that completely separate the ...
  34. The Active Directory Topology service on server {0} detected Active Directory global catalog servers in the local Active ...
  35. The Active Directory Topology service on server {0} didn't detect any Active Directory global catalog servers in the local ...
  36. The Active Directory Topology service on server {0} is hard coded to use Active Directory domain controller servers {1} for ...
  37. The Active Directory Topology service on server {0} is hard-coded to exclude Active Directory Directory Domain Controller ...
  38. The Active Directory Topology service on server {0} is hard-coded to use Active Directory domain controller server(s) {1}. ...
  39. The Active Directory Topology service on server {0} is hard-coded to use Active Directory global catalog server(s) {1}. This ...
  40. The Active Directory Topology service on server {0} isn't hard coded to use Active Directory domain controller servers {1} ...
  41. The Active Directory Topology service on server {0} isn't hard-coded to exclude Active Directory Directory Domain Controller ...
  42. The Active Directory Topology service on server {0} isn't hard-coded to use Active Directory global catalog server(s) {1}. ...
  43. The Active Directory Topology service on server {0} isn't hard-coded to use any Active Directory domain controller server(s) ...
  44. The Active Directory Topology service on server {2} is hard coded to use Active Directory domain controller servers {1} for ...
  45. The Active Manager component of the Microsoft Exchange Replication service is not in a healthy state on {0}. A restart of ...
  46. The AD LDS schema import process {0} failed with error code {1}. No schema has been imported into AD LDS. View the Setup ...
  47. The AD Topology Service on server {2} is hard-coded to exclude Active Directory Directory Domain Controller server(s) {1}. ...
  48. The AD Topology service on server {2} is hard-coded to use Active Directory domain controller server(s) {1}. This configuration ...
  49. The ADAccess Topology service on server {2} did not detect any Active Directory global catalog servers in the local Active ...
  50. The address "{0}" is the e-mail address of your account or a proxy address that points to your account. You can't create ...
  51. The Address Book custom properties couldn't be parsed. "%1" attribute wasn't found in "%2" at line number = "%3". Having ...
  52. The Address Book custom properties couldn't be parsed. An invalid value was provided for the attribute "%1" and in the file ...
  53. The Address Book custom properties couldn't be parsed. Invalid attribute count in "%1" at line number = "%2".Each CustomProperty ...
  54. The Address Book custom properties couldn't be parsed. Invalid element found in "%1" at line number ="%2" position = "%3". ...
  55. The Address Book custom properties couldn't be parsed. Invalid file "%1" Line number = %2 Position = %3 Message = "%4" . ...
  56. The Address Book custom properties couldn't be parsed. RootElementNotFound in "%1" at line number = "%2". Make sure that ...
  57. The address book functionality may not work correctly for Exchange Server 2007 Outlook Web Access clients with this version ...
  58. The Address Book Policy with ID '%1' in Organization '%2' could not be retrieved because of an Active Directory access error. ...
  59. The address list "{0}" has been created or modified, but recipients have not been updated. To update the address list membership, ...
  60. The address list couldn't be edited. Address lists created using legacy versions of Exchange must be upgraded using the Set-AddressList ...
  61. The Address List service on {0} cannot be contacted to calculate proxy addresses or address list membership. {0} must have ...
  62. The address type '{0}' is missing from the current Active Directory. This will result in an Exchange Address List Service ...
  63. The address type '{4}' is missing from current Active Directory. This will result in Exchange Recipient Update Service error. ...
  64. The address type '{4}' is missing from the current Active Directory. This will result in an Exchange Address List Service ...
  65. The Admin audit logs of tenant %1 is approaching the recoverable items quota limit of system arbitration mailbox. Current ...
  66. The administrative group '{0}' contains one or more routing groups, but the 'Servers' container is missing. This may cause ...
  67. The administrator has paused public folder content replication for the organization. This option should only be set if an ...
  68. The AdvertiseClientSettings parameter can't be set to $true on a Receive connector unless ExchangeUsers is added to the list ...
  69. The agents listed above have been installed. Please restart the Microsoft Exchange Transport service for changes to take ...
  70. The aggregation task requires mailboxes, but a mailbox for "{0}" couldn't be found. Please make sure that the mailbox name ...
  71. The alternate witness server wasn't specified for database availability group '{0}'. Please use the -AlternateWitnessServer ...
  72. The AlwaysUseCachedCredsForSPA registry entry isn't correct. This can cause Outlook to prompt you for your credentials every ...
  73. The amount of processor time not spent in the store.exe, inetinfo.exe, emsmta.exe, lsass.exe, w3wp.exe, exmgmt.exe, or mad.exe ...
  74. The amount of processor time not spent in the store.exe, inetinfo.exe, emsmta.exe, lsass.exe, w3wp.exe, or mad.exe processes ...
  75. The anti-malware agent could not send a notification for the following message. The configured email address from which to ...