Exchange Server 2016

  1. The results reported by the script can be restricted to some subset by using the "-Database" or "-ReportFilter" options. ...
  2. The Resume operation won't have an effect on database replication because database '{0}' hosted on server '{1}' is the active ...
  3. The retention policy can be set as a default retention policy for only one mailbox type - user mailboxes or arbitration mailboxes. ...
  4. The retention policy folder '%1' in mailbox '%2' will not be applied. The managed folder assistnat is unable to process managed ...
  5. The retention policy for folder '%1' in mailbox '%2' will not be applied. The managed folder assistant is unable to process ...
  6. The retention policy for the Arbitration mailbox is not available. Requests will not expire. Please assign a retention policy ...
  7. The retention policy tag can be set as a default retention policy for only one approval application - AutoGroup or ModeratedRecipients. ...
  8. The retention tag for {0} approval application in organization "{1}" doesn't exist. The organization-level configuration ...
  9. The RfrHttpPort value configured for the Exchange Address Book Service on server {0} has changed. The port is currently set ...
  10. The RMS template "{0}" has changed from Distributed to Archived. NDRs may occur when Transport Protection Rules use archived ...
  11. The RMS template you're trying to use is corrupted or malformed. Please recreate the template on your RMS server and try ...
  12. The RMS trusted publishing domain (TPD) {0} is configured as the default RMS TPD. Removing the default TPD will cause all ...
  13. The role assignment policy "{0}" you specified is outside of the organization "{1}" where the management role assignment ...
  14. The RoleAssignee parameter was specified. The cmdlet will attempt to resolve the value in the {0} configuration naming context ...
  15. The room mailbox is for room scheduling and is not owned by a user. The user account associated with resource mailbox will ...
  16. The root directory "%s" can't be used as the installation directory. Please specify a folder in which to install Exchange. ...
  17. The root of a folder hierarchy synchronization cannot be set to the id of a public folder. Use FindFolder to synchronize ...
  18. The routing group (GUID: {1}) does not exist in Active Directory. However, the link state information maintained by server ...
  19. The routing group (GUID: {1}) does not exist in Active Directory. However, the link state information maintained by server ...
  20. The routing group (GUID: {1}) does not exist in Active Directory. However, the link state information maintained by server ...
  21. The routing group (GUID: {1}) does not exist in Active Directory. However, the link state information maintained by server ...
  22. The routing group (GUID: {1}) found in the link state information maintained by server {2} cannot be resolved to an object ...
  23. The routing group (GUID: {1}) found in the link state information maintained by server {2} was successfully resolved to the ...
  24. The routing group for Exchange server %1 was not determined in routing tables with timestamp %2. Recipients will not be routed ...
  25. The routing group master (GUID: {1}) found in the link state information maintained by server {2} cannot be resolved to an ...
  26. The routing group master (GUID: {1}) found in the link state information maintained by server {2} was successfully resolved ...
  27. The routing group member (GUID: {1}) found in the link state information maintained by server {2} cannot be resolved to an ...
  28. The routing group member (GUID: {1}) found in the link state information maintained by server {2} was successfully resolved ...
  29. The routing table lookup for the UM IP gateway failed after the UM IP gateway was created, leaving the UM IP gateway in an ...
  30. The RPC over HTTP Proxy component is currently disabled. This prevents Outlook Anywhere from being configured correctly. ...
  31. The RPC over HTTP Proxy component is not installed or is not properly configured. Use the Windows Component Wizard to add ...
  32. The RPC port range on server {0} is manually set to {1}. If RPC errors are occurring, the port range may need to be expanded. ...
  33. The RPC port range on server {2} is manually set to {9}. If RPC errors are occurring, the port range may need to be expanded. ...
  34. The RPC proxy server extension installed on server {2} points to a non-standard path ({5}). Please verify that this file ...
  35. The RPC query to retrieve the copy status for databases on server '{0}' failed. The Microsoft Exchange Replication service ...
  36. The RPCs for user '{1}' had a large number of failures. {2} out of {3} operations failed. This accounts for {0}% of this ...
  37. The RpcTcpPort value configured for the Exchange Address Book service on server {0} is invalid. It's currently set to {1}. ...
  38. The RpcTcpPort value configured for the Exchange Address Book service on server {0} isn't within the recommended range. It's ...
  39. The rule can't be created because it is too large. It has {0} characters, and the maximum number of characters is {1}. Reduce ...
  40. The rule collection file name that you just specified already exists. Do you want to continue and overwrite the existing ...
  41. The rule collection you are trying to import contains older rule actions that are not compatible with the new rule actions ...
  42. The rule collection you are trying to import contains the LogEvent action that is no longer supported. The LogEvent action ...
  43. The rule contains NotifySender action with an option that may reject the message. In case the message gets rejected, other ...
  44. The rule load time has exceeded the monitoring threshold configured in the 'TransportRuleLoadTimeAlertingThresholdInMilliseconds' ...
  45. The rule mode is set to '{0}' while DLP policy mode is '{1}'. DLP policy mode is overriden by explicit rule Mode parameter. ...
  46. The rule pack contains sensitive information types referenced by DLP Compliance rules and cannot be deleted. The following ...
  47. The Rules quota of mailbox %1 has been reached and the automatic reply rules can't be enabled or updated. Delete some existing ...
  48. The SACL Watcher servicelet encountered an error while monitoring SACL change. Returned error %2 enumerating group policies ...
  49. The SACL Watcher servicelet encountered an error while monitoring SACL change. The domain controller name is null or empty. ...
  50. The Scalable Networking Pack is installed on server '{2}' and its network offloading features are enabled. Make sure the ...
  51. The scan you have requested is being prepared. Depending on the amount of data in the scan, this may take several minutes ...
  52. The Schema Master role '{2}' is not running Windows Server 2003 Service Pack 1 or later. Exchange Server 2007 requires this ...
  53. The schemaVersionSupported parameter is invalid. It should be in the form of major version, minor version, separated by '.', ...
  54. The SCL threshold value is outside of the allowed range. The threshold value must be from 0 though 9. Provide a value that ...
  55. The scope of the management role assignments "{0}" and "{1}" couldn't be compared because the associated management scopes ...
  56. The script can also email reports of the database status. To configure this, admins should edit the Send-HANotificationMailCorpHub ...
  57. The script starts PowerShell jobs to collect the data from each server. These jobs run for the full duration that data is ...
  58. The search catalog didn't become healthy after seeding. Use the CatalogOnly parameter to reseed the search catalog if required. ...
  59. The Search catalog for database '{0}' is suspended but the database is not in the suspended state. The database state is ...
  60. The Search catalog for the database '{0}' is being seeded, but it is not making progress. It is stuck at {1} percent. The ...
  61. The Search catalog for the database '{0}' is in the '{1}' state on the local server '{4}'. However, there is a healthy copy ...
  62. The Search catalog for the database '{0}' is too big. The database is {1} GB and the catalog is {2} GB. The catalog size ...
  63. The Search catalog for the mounted database '{0}' is being seeded, but there is a heathy copy available on server '{1}'. ...
  64. The Search catalog is crawling the mounted database '{0}', but there is a healthy copy available on server '{1}'. The attempt ...
  65. The Search catalog is in the '{1}' state for the mounted database '{0}'. The attempt to fail over either failed or was throttled. ...
  66. The Search catalog is unhealthy for mounted database '{0}'. Its status is '{1}' and the content indexing error message is ...
  67. The Search catalog is unhealthy for the database '{0}'. Its status is '{1}' and the content indexing error message is '{2}'.Error ...
  68. The search exceeded the maximum number of keywords that can be searched at a time. Please try searching less than {0} keywords. ...
  69. The search exceeded the maximum number of mailboxes that can be searched at a time. If you're an Exchange Server 2016 organization, ...
  70. The Search feeding controller for database '{0}' contains the following error in the diagnostic information: '{1}'.Please ...
  71. The Search feeding controller for the database '{0}' has failed {1} times in the last {2} minutes. Service restarts were ...
  72. The search filter is invalid: '{0}'. Only 'Description -like' or 'DescriptionAndName -like' filters are supported. For example, ...
  73. The Search indexing feeding instance was not loaded for the database '{0}' by the Exchange Search service. Please use the ...
  74. The Search notification feeder's last processed event ID is 0 for the database '{0}'. Notifications are not being processed ...
  75. The search operation could not be completed within the allotted time limit. Please try to narrow down your scope to reduce ...