Exchange Server 2010

  1. The action couldn't be completed because the Microsoft Exchange Information Store service is unavailable. Be sure the service ...
  2. The action you requested couldn't be performed because you've selected too many items. Select fewer than 500 items and try ...
  3. The action you tried to perform couldn ft be completed because there fs a configuration problem on the server. If the problem ...
  4. The action you tried to perform couldn't be completed because there's a configuration problem on the server. If the problem ...
  5. The activation of all modules took longer than expected to complete. Total Load Time: %1 Total Start Time: %2 Load Time Breakdown: ...
  6. The activation of all modules took longer than expected to complete. Total Load Time: %1 Total Start Time: %2 Load Time Breakdown: ...
  7. The active copy of %1 has a missing or corrupted log file (%2). As a result, existing log files and any partial data will ...
  8. The active copy of %1 has a missing or corrupted log file (%2). As a result, existing log files and any partial data will ...
  9. The active copy of %1 has a missing or corrupted log file (%2). To keep this copy healthy, replication will restart at generation ...
  10. The active copy of %1 has a missing or corrupted log file (%2). To keep this copy healthy, replication will restart at generation ...
  11. The Active Directory access rule "{0}" doesn't have valid public folder administrative rights. Valid public folder administrative ...
  12. The Active Directory configuration indicates that server '{0}' is a member of database availability group '{1}', which can't ...
  13. The Active Directory Connector (ADC) software on server {2} is from Exchange Server 2003 (initial release). A more recent ...
  14. The Active Directory Connector (ADC) software on server {2} is from Exchange Server 2003 Service Pack 1. A more recent version ...
  15. The Active Directory Connector server {2} is down or unreachable. This error could also be the result of a network or permissions ...
  16. The Active Directory domain configuration version ({0}) is higher than Setup's version({1}). Therefore, PrepareDomain can't ...
  17. The Active Directory forest functionality level has been raised. A modification to recipient policy '{3}' is required to ...
  18. The Active Directory forest functionality level has been raised. A modification to the system policies is required to avoid ...
  19. The Active Directory forest is prepared for Windows Server 2003. To avoid incorrect e-mail address generation when the forest ...
  20. The Active Directory forest is prepared for Windows Server 2003. To avoid mailbox re-homing issues when the forest is upgraded ...
  21. The Active Directory Lightweight Directory Services (AD LDS) instance uninstallation process {0} failed with error code {1}. ...
  22. The Active Directory must be modified with 'Setup /PrepareAD' and this user account lacks required permissions even though ...
  23. The Active Directory needs to be prepared for Exchange Server and Ldifde.exe is not installed on this computer. You must ...
  24. The Active Directory needs to be prepared for Exchange Server and Ldifde.exe is not installed on this computer. You must ...
  25. The Active Directory node %3 has %1 %2 entries, but Exchange can accept only one. Contact your administrator for help in ...
  26. The Active Directory node %3 has %1 %2 entries, but Exchange can accept only one. Contact your administrator for help in ...
  27. The Active Directory object for Recipient Update Service '{3}' is in conflict with another object. This may cause duplicate ...
  28. The Active Directory object for virtual directory '{1}' on '{0}' could not be created. This might be because the object already ...
  29. The Active Directory object {0} isn't visible to authenticated users. Authenticated users need "Read Properties", "List Object", ...
  30. The Active Directory organization configuration version ({0}) is higher than Setup's version({1}). Therefore, PrepareAD can't ...
  31. The Active Directory page information in the cookie can only be used against the originating domain controller. Please retry ...
  32. The Active Directory property "msExchMetabasePath" for the Exchange ActiveSync virtual directory named "{0}" is set to "{1}", ...
  33. The Active Directory property "msExchMetabasePath" for the Exchange ActiveSync virtual directory named "{0}" is set to "{1}", ...
  34. The Active Directory property "msExchMetabasePath" for the Outlook Web App virtual directory named "{0}" is set to "{1}", ...
  35. The Active Directory property "msExchMetabasePath" for the Outlook Web App virtual directory named "{0}" is set to "{1}", ...
  36. The Active Directory resource couldn't be accessed. This may be because the Active Directory object doesn't exist or the ...
  37. The Active Directory Schema is not up-to-date and Ldifde.exe is not installed on this computer. You must install Ldifde.exe ...
  38. The Active Directory Schema is not up-to-date and Ldifde.exe is not installed on this computer. You must install Ldifde.exe ...
  39. The Active Directory Schema is not up-to-date, and this user account is not a member of the 'Schema Admins' and/or 'Enterprise ...
  40. The Active Directory schema is not up-to-date. You must run setup with the "/ForestPrep" switch. If you have already done ...
  41. The Active Directory schema version ({0}) is higher than Setup's version ({1}). Therefore, PrepareSchema can't be executed. ...
  42. The Active Directory schema will need to be upgraded (via the /PrepareSchema switch of Exchange Server 2007 setup) before ...
  43. The Active Directory site for Exchange server %1 was not determined in routing tables with timestamp %2. Recipients will ...
  44. The Active Directory site for Exchange server %1 was not determined in routing tables with timestamp %2. Recipients will ...
  45. The Active Directory split permissions security model is typically used by large organizations that completely separate the ...
  46. The Active Directory split permissions security model is typically used by large organizations that completely separate the ...
  47. The Active Directory topology service could not discover any route to connector %1 in the routing tables with the timestamp ...
  48. The Active Directory topology service could not discover any route to connector %1 in the routing tables with the timestamp ...
  49. The ActiveX control needs to be enabled in Internet Explorer for Outlook Web App to work correctly. Click {0}here{1} to sign ...
  50. The actual name that will be used for the UM-enabled user with the display name '{0}' and the PhoneticName '{1}' is '{2}'. ...
  51. The AD LDS schema import process {0} failed with error code {1}. No schema has been imported into AD LDS. View the Setup ...
  52. The AD Topology Service on server {2} is hard-coded to exclude Active Directory Directory Domain Controller server(s) {1}. ...
  53. The AD Topology Service on server {2} is hard-coded to use Active Directory Domain Controller server(s) {1} for configuration. ...
  54. The AD Topology service on server {2} is hard-coded to use Active Directory domain controller server(s) {1}. This configuration ...
  55. The ADAccess Topology service on server {2} did not detect any Active Directory global catalog servers in the local Active ...
  56. The address "{0}" is the e-mail address of your account or a proxy address that points to your account. You can't create ...
  57. The Address Book custom properties couldn't be parsed. "%1" attribute wasn't found in "%2" at line number = "%3". Having ...
  58. The Address Book custom properties couldn't be parsed. "%1" attribute wasn't found in "%2" at line number = "%3". Having ...
  59. The Address Book custom properties couldn't be parsed. An invalid value was provided for the attribute "%1" and in the file ...
  60. The Address Book custom properties couldn't be parsed. An invalid value was provided for the attribute "%1" and in the file ...
  61. The Address Book custom properties couldn't be parsed. Invalid attribute count in "%1" at line number = "%2".Each CustomProperty ...
  62. The Address Book custom properties couldn't be parsed. Invalid attribute count in "%1" at line number = "%2".Each CustomProperty ...
  63. The Address Book custom properties couldn't be parsed. Invalid element found in "%1" at line number ="%2" position = "%3". ...
  64. The Address Book custom properties couldn't be parsed. Invalid element found in "%1" at line number ="%2" position = "%3". ...
  65. The Address Book custom properties couldn't be parsed. Invalid file "%1" Line number = %2 Position = %3 Message = "%4" . ...
  66. The Address Book custom properties couldn't be parsed. Invalid file "%1" Line number = %2 Position = %3 Message = "%4" . ...
  67. The Address Book custom properties couldn't be parsed. RootElementNotFound in "%1" at line number = "%2". Make sure that ...
  68. The Address Book custom properties couldn't be parsed. RootElementNotFound in "%1" at line number = "%2". Make sure that ...
  69. The address book functionality may not work correctly for Exchange Server 2007 Outlook Web Access clients with this version ...
  70. The address list "{0}" has been created or modified, but recipients have not been updated. To update the address list membership, ...
  71. The address list '%1' has an invalid filter rule (PurportedSearch). The error is '%2'. No directory entries will belong to ...
  72. The address list '%1' has an invalid filter rule (PurportedSearch). The error is '%2'. No directory entries will belong to ...
  73. The Address List '%1' on directory %2 could not be loaded due to an error. Make sure that the Address List is configured ...
  74. The Address List '%1' on directory %2 could not be loaded due to an error. Make sure that the Address List is configured ...
  75. The address list couldn't be edited. Address lists created using legacy versions of Exchange must be upgraded using the Set-AddressList ...