Exchange Server 2010

  1. The routing group member (GUID: {1}) found in the link state information maintained by server {2} was successfully resolved ...
  2. The routing table lookup for the UM IP gateway failed after the UM IP gateway was created, leaving the UM IP gateway in an ...
  3. The Rpc Client Access server specified {0}, which is not the same value returned via the Address Book server, {1}. Outlook ...
  4. The RPC over HTTP Proxy component is currently disabled. This prevents Outlook Anywhere from being configured correctly. ...
  5. The RPC over HTTP Proxy component is currently disabled. This prevents Outlook Anywhere from being configured correctly. ...
  6. The RPC over HTTP Proxy component is not installed or is not properly configured. Use the Windows Component Wizard to add ...
  7. The RPC over HTTP Proxy component is not installed or is not properly configured. Use the Windows Component Wizard to add ...
  8. 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. ...
  9. The RPC proxy server extension installed on server {2} points to a non-standard path ({5}). Please verify that this file ...
  10. The RPC query to retrieve the copy status for databases on server '{0}' failed. The Microsoft Exchange Replication service ...
  11. The RPCs for user '{1}' had a large number of failures. {2} out of {3} operations failed. This accounts for {0}% of this ...
  12. The RpcTcpPort value configured for the Exchange Address Book service on server {0} is invalid. It's currently set to {1}. ...
  13. The RpcTcpPort value configured for the Exchange Address Book Service on server {0} is not within the recommended range. ...
  14. The rule "%1" with the sequence number %2 was disabled due to the error %5 that was encountered while applying the rule. ...
  15. The rule "%1" with the sequence number %2 was disabled due to the error %5 that was encountered while applying the rule. ...
  16. The rule "%1" with the sequence number %2 was disabled due to the error %5 that was encountered while applying the rule. ...
  17. The rule "%1" with the sequence number %2 was disabled due to the error %5 that was encountered while applying the rule. ...
  18. The rule (%1) with sequence number %2 is being ignored because it is already in the rule trigger history. The distinguished ...
  19. The rule (%1) with sequence number %2 is being ignored because it is already in the rule trigger history. The distinguished ...
  20. The rule (%1) with sequence number %2 is being ignored because it is already in the rule trigger history. The public folder ...
  21. The rule (%1) with sequence number %2 is being ignored because it is already in the rule trigger history. The public folder ...
  22. The rule (%1) with sequence number %2 is being ignored because it is disabled. The distinguished name of the owning mailbox ...
  23. The rule (%1) with sequence number %2 is being ignored because it is disabled. The distinguished name of the owning mailbox ...
  24. The rule (%1) with sequence number %2 is being ignored because it is disabled. The public folder is %3 on database "%4". ...
  25. The rule (%1) with sequence number %2 is being ignored because it is disabled. The public folder is %3 on database "%4". ...
  26. The rule (%1) with sequence number %2 is being ignored because it is in an error state. The distinguished name of the owning ...
  27. The rule (%1) with sequence number %2 is being ignored because it is in an error state. The distinguished name of the owning ...
  28. The rule (%1) with sequence number %2 is being ignored because it is in an error state. The public folder is %3 on database ...
  29. The rule (%1) with sequence number %2 is being ignored because it is in an error state. The public folder is %3 on database ...
  30. The rule can't be created because it is too large. It has {0} characters, and the maximum number of characters is {1}. Reduce ...
  31. The rule can't be saved. Either the rule is larger than the size limit for individual rules, or all your rules together, ...
  32. The rule collection file name that you just specified already exists. Do you want to continue and overwrite the existing ...
  33. The rule collection you are trying to import contains older rule actions that are not compatible with the new rule actions ...
  34. The rule collection you are trying to import contains the LogEvent action that is no longer supported. The LogEvent action ...
  35. The rules on a folder are too big for the destination server. To allow the operation to complete, all the user's rules on ...
  36. The rules on a folder are too big for the destination server. To allow the operation to complete, all the user's rules on ...
  37. The Rules quota of mailbox %1 has been reached and the automatic reply rules can't be enabled or updated. Delete some existing ...
  38. The Rules quota of mailbox %1 has been reached and the automatic reply rules can't be enabled or updated. Delete some existing ...
  39. The SACL Watcher servicelet encountered an error while monitoring SACL change. Returned error %2 enumerating group policies ...
  40. The SACL Watcher servicelet encountered an error while monitoring SACL change. Returned error %2 enumerating group policies ...
  41. The SACL Watcher servicelet encountered an error while monitoring SACL change. The domain controller name is null or empty. ...
  42. The SACL Watcher servicelet encountered an error while monitoring SACL change. The domain controller name is null or empty. ...
  43. The Scalable Networking Pack is installed on server '{2}' and its network offloading features are enabled. Make sure the ...
  44. The scan you have requested is being prepared. Depending on the amount of data in the scan, this may take several minutes ...
  45. The Schema Master role '{2}' is not running Windows Server 2003 Service Pack 1 or later. Exchange Server 2007 requires this ...
  46. The SCL threshold value is outside of the allowed range. The threshold value must be from 0 though 9. Provide a value that ...
  47. The scope of the management role assignments "{0}" and "{1}" couldn't be compared because the associated management scopes ...
  48. The script can also email reports of the database status. To configure this, admins should edit the Send-HANotificationMailCorpHub ...
  49. The script starts PowerShell jobs to collect the data from each server. These jobs run for the full duration that data is ...
  50. The search catalog could not be dismounted for the database '{0}' on server '{1}'. The files may be locked while the Microsoft ...
  51. The search catalog didn't become healthy after seeding. Use the CatalogOnly parameter to reseed the search catalog if required. ...
  52. The search exceeded the maximum number of mailboxes that can be searched at a time. Please try searching less than {0} mailboxes. ...
  53. The search index files for Mailbox Database %1 (GUID = %2) are invalid. They will be deleted and recreated in %3 minutes ...
  54. The search index files for Mailbox Database %1 (GUID = %2) are invalid. They will be deleted and recreated in %3 minutes ...
  55. The search name can't contain the asterisk (*) or question mark (?) characters, or any leading or trailing spaces. Please ...
  56. The search operation could not be completed within the allotted time limit. Please try to narrow down your scope to reduce ...
  57. The SearchFolder is already visible to Outlook. There is already an associated message with the information of this SearchFolder. ...
  58. The second highest source of RPC load is in the category '{1}'. This category accounts for {2} RPC operations/second, out ...
  59. The secondary address {0} is in an invalid format. The secondary address must be a valid extension or in the form @contoso.com. ...
  60. The secondary WINS server address for network interface '{1}' on server {2} is blank. If primary WINS resolution fails this ...
  61. The security context could not be established due to a failure in the requested quality of service (e.g. mutual authentication ...
  62. The security context couldn't be established due to a failure in the requested quality of service (for example, mutual authentication ...
  63. The security features that are required for delivery of this e-mail message are not supported by the recipient e-mail system. ...
  64. The security features that are required for delivery of this e-mail message aren't supported by the recipient's e-mail system. ...
  65. The Security Preference change for UM server {0} won't take effect until the Microsoft Exchange Unified Messaging service ...
  66. The seeding was cancelled for database '{0}' because the copy configuration changed on the seeding source '{1}' ( a failover ...
  67. The seeding was cancelled for database '{0}' from '{1}' because the database copy on server '{1}' has transitioned to failed ...
  68. The selected items will be permanently deleted from this folder. If you continue, you won't be able to recover these items. ...
  69. The selected mailbox will be enabled for Unified Messaging. Upon completion, an e-mail message will be sent to the mailbox ...
  70. The send or update operation could not be performed because the change key passed in the request does not match the current ...
  71. The sender e-mail address is invalid. There may be an error in the e-mail account configuration. Check for configuration ...
  72. The sender has a malformed or missing mail attribute in the directory structure. The Transport categorizer cannot deliver ...
  73. The sender has requested to share their calendar with a group you're a member of. However, calendars can't be shared with ...
  74. The sender is not authorized to send e-mail messages to this e-mail address. Possible causes: 1)The session is not authenticated ...
  75. The sender isn't authorized to send e-mail messages to this e-mail address. The possible reasons for this are: 1)The session ...