Exchange Server 2016

  1. The recipient policy "{0}" does not contain e-mail address properties. The operation cannot be completed for a recipient ...
  2. The recipient policy "{0}" with mailbox manager settings cannot be managed by the current version of Exchange Management ...
  3. The recipient policy '{0}' uses an unsupported SMTP addressing format ({1}). The value must be changed before Setup can continue. ...
  4. The recipient preview filter string "{0}" is neither a valid OPath filter nor a valid LDAP filter. Please use the Exchange ...
  5. The recipient preview filter string "{0}" is neither a valid OPath filter nor a valid LDAP filter. Use the -RecipientPreviewFilter ...
  6. The recipient type for recipient '{0}' is '{1}'. This recipient type is not valid for delivery restriction or moderation ...
  7. The recipient's e-mail address has changed. The address this message was sent to isn't accepting e-mail messages. No forwarding ...
  8. The recipient's e-mail system doesn't have enough information to deliver the message. Please see the diagnostic text in the ...
  9. The recipient's mailbox is over its storage limit. Troubleshooting: Verify the mailbox storage and the queue storage quota ...
  10. The recommended value for 'MinUserDc' registry entry on server '{0}' is configured correctly. This value should be between ...
  11. The recommended value for 'MinUserDc' registry entry on server '{0}' isn't configured correctly. This value should be between ...
  12. The RedirectToRecipients value is not set. If no value is set, detected messages will be redirected to a non-existent email ...
  13. The registry value %3 is the wrong Type. Expected Type: %1 Found Type: %2 This may prevent Outlook Anywhere settings from ...
  14. The registry value 'FCheckTcpTimedWaitDelayEntry' on registry key 'System\CurrentControlSet\Services\Tcpip\Parameters' is ...
  15. The registry value 'FCheckTcpTimedWaitDelayEntry' on registry key 'System\CurrentControlSet\Services\Tcpip\Parameters' isn't ...
  16. The registry value 'MaxUserPort' on registry key 'System\CurrentControlSet\Services\Tcpip\Parameters' isn't set to {0}. This ...
  17. The registry value '{0}' on registry key '{1}' is not currently set to {6}. This may cause connection problems for clients ...
  18. The registry value '{0}' on registry key '{1}' is not currently set to {6}. This may cause connection problems to clients ...
  19. The registry value for the OAB Extension attribute is invalid. The current value is "%1". The value should be between "extensionAttribute1" ...
  20. The Registry value {0}\{1} couldn't be updated due to insufficient permissions. Make sure the user performing this operation ...
  21. The remote bridgehead server (GUID: {1}) found in the link state information maintained by server {2} cannot be resolved ...
  22. The remote bridgehead server (GUID: {1}) found in the link state information maintained by server {2} was successfully resolved ...
  23. The Remote Domain can't be created because the maximum number of Remote Domains already exists. The maximum number is {0}. ...
  24. The remote Exchange Server 2007 {0} is not in the same Active Directory forest (Exchange organization) as {3} and is advertising ...
  25. The remote organization relationship {0} has flag {1} set, but the local organization relationship {2} has property {3} set ...
  26. The remote organization uses a different security token service than the local organization does. The local organization ...
  27. The remote server for this account has been changed and no longer makes it possible to retrieve messages from the account ...
  28. The remote server for this account has been changed and no longer makes it possible to retrieve messages from the account ...
  29. The remote server {2} failed the SMTP connectivity test but is either not running Exchange Server 2007 or is not in the same ...
  30. The Remove-ApprovalApplication cmdlet doesn't support the Identity parameter, Instead, use the AutoGroup or ModeratedRecipients ...
  31. The replacement string '{0}' was previously defined in a speech grammar file used for converting directory names. The patterns ...
  32. The replication instance for database %1 has corrected log file divergence. Log files after generation %4 have been moved ...
  33. The replication instance for database %1 has started replaying log files. Log files up to generation %4 have been replayed. ...
  34. The replication instance for database copy '{0}' could not be restarted because a database copy is being seeded. The operation ...
  35. The replication instance for database copy '{0}' could not be restarted because a database switchover or failover is in progress. ...
  36. The request can't be handled because the Microsoft Exchange Unified Messaging service is processing the maximum number of ...
  37. The request couldn't be created because it exceeds the organization's limit of {0} maximum concurrent migrations. Please ...
  38. The request for mailbox {0} has been temporarily postponed because a database has failed over. The Mailbox Replication Service ...
  39. The request has already been removed. Continuing to contact the Microsoft Exchange Mailbox Replication service in order to ...
  40. The request has been temporarily postponed because a database has failed over. The Microsoft Exchange Mailbox Replication ...
  41. The request has been temporarily postponed because DataMoveReplicationConstraint is not satisfied (agent CA). The Microsoft ...
  42. The request has been temporarily postponed because DataMoveReplicationConstraint is not satisfied (agent HA). The Microsoft ...
  43. The request has been temporarily postponed because DataMoveReplicationConstraint is not satisfied. The Microsoft Exchange ...
  44. The request has been temporarily postponed because the mailbox is locked. The Microsoft Exchange Mailbox Replication service ...
  45. The request has been temporarily postponed because the target database is not healthy. The Microsoft Exchange Mailbox Replication ...
  46. The request has been temporarily postponed because the user has not logged on since {0}. The Microsoft Exchange Mailbox Replication ...
  47. The request has been temporarily postponed due to unfavorable server health or budget limitations. MRS will attempt to continue ...
  48. The request is valid but does not specify the correct server version in the RequestServerVersion SOAP header. Ensure that ...
  49. The request to disable replay lag for database copy '{0}' failed because the value could not be set in the registry. This ...
  50. The request to enable replay lag for database copy '{0}' failed because an administrative action has already been taken to ...
  51. The request to join or depart group '{0}' has expired because the owners of this group didn't respond to your request within ...
  52. The RequestDetailsLogger request data has already been committed, and the object was disposed. Any logging data that's being ...
  53. The requested data move replication constraint, {0}, isn't valid for mailbox database {2} because it either has only one ...
  54. The requested operation failed due to a permissions problem encountered while accessing a remote directory. Check that your ...
  55. The requested operation isn't valid for an object that is of type MultiValuedProperty and has IsChangesOnlyCopy set to True. ...
  56. The requested search root '{0}' is not in the current default scope '{1}'. Cannot perform searches outside the current default ...
  57. The requested search root '{0}' is not in the current session scope '{1}'. Cannot perform searches outside the current session ...
  58. The requested search root '{0}' is not within the scope of this operation. Cannot perform searches outside the scope '{1}'. ...
  59. The required log file %2 for %1 is missing on the active copy. If you removed the log file, please replace it. If the log ...
  60. The required MAPI profile couldn't be created. Please verify that you have sufficient permissions to write to the MAPISVC.INF ...
  61. The resource associated with data classification identifier "{0}" contains Description value(s) in invalid language code(s): ...
  62. The resource associated with data classification identifier "{0}" contains Name value(s) in invalid language code(s): {1}. ...
  63. The resource associated with data classification identifier "{0}" contains non-unique language code(s) for Description value(s): ...
  64. The resource associated with data classification identifier "{0}" contains non-unique language code(s) for Name value(s): ...
  65. The Resource Booking Attendant is unable to resolve the legacy Exchange DN %1 to a unique recipient in the Active Directory. ...
  66. The resource(s) associated with these data classification identifier(s) are invalid: "{0}". Resource must have one and only ...
  67. The resource(s) associated with these data classification identifier(s) are invalid: "{0}". The default Name and Description ...
  68. The ResourceCustom, ResourcePropertiesDisplay, and ResourceSearchProperties parameters can't be specified at the same time. ...
  69. The response is in invalid format. Please rerun the cmdlet with the Verbose parameter to investigate the response details. ...
  70. The Restore-MailboxDatabaseCopy operation on %1 was successful, and production paths were updated. All logs were not successfully ...
  71. The Restore-MailboxDatabaseCopy operation on %1 was successful, and production paths were updated. All logs were successfully ...
  72. The Restore-MailboxDatabaseCopy operation on %1 was successful. All logs were not successfully copied. Time of the failure ...
  73. The restored logfile %4 does not have the correct log signature. For more information, click http://www.microsoft.com/contentredirect.asp. ...
  74. The result object has been corrupted and is in an inconsistent state. The following validation errors have been encountered: ...
  75. The results are sorted but inconsistent with reference item. MailboxGuid:'{0}', ReferenceItem:'{1}', Offending Item:'{2}'. ...