Exchange Server 2010

  1. Client Access server "%1" tried to proxy Outlook Web App traffic to Client Access server "%2". This failed because "%2" didn't ...
  2. Client Access server "%1" tried to proxy Outlook Web App traffic to Client Access server "%2". This failed because one of ...
  3. Client Access server "%1" tried to proxy Outlook Web App traffic to Client Access server "%2". This failed because one of ...
  4. Client Access server "%1" tried to proxy Outlook Web App traffic to Client Access server "%2". This failed because the Outlook ...
  5. Client Access server "%1" tried to proxy Outlook Web App traffic to Client Access server "%2". This failed because the Outlook ...
  6. Client Access server "%1" tried to proxy Outlook Web App traffic to Client Access server "%2". This failed for user "%3" ...
  7. Client Access server "%1" tried to proxy Outlook Web App traffic to Client Access server "%2". This failed for user "%3" ...
  8. Client Access server "%1", running Exchange version "%2", is proxying Outlook Web App traffic to Client Access server "%3", ...
  9. Client Access server "%1", running Exchange version "%2", is proxying Outlook Web App traffic to Client Access server "%3", ...
  10. Client Access server %1 failed to obtain site information for %2 because Client Access server %2 isn't contained within an ...
  11. Client Access server %1 failed to obtain site information for %2 because Client Access server %2 isn't contained within an ...
  12. Client Access server %1 failed to proxy Exchange Web Services to Active Directory site %2 because none of the Client Access ...
  13. Client Access server %1 failed to proxy Exchange Web Services to Active Directory site %2 because none of the Client Access ...
  14. Client Access server %1 failed to proxy Exchange Web Services to Active Directory site %2 because there are no applicable ...
  15. Client Access server %1 failed to proxy Exchange Web Services to Active Directory site %2 because there are no applicable ...
  16. Client Access server %1 failed to proxy the request because there are no applicable Client Access servers in any potential ...
  17. Client Access server %1 failed to proxy the request because there are no applicable Client Access servers in any potential ...
  18. Client Access server %1 running Exchange version %2 tried to find a Client Access server in Active Directory site %3. Service ...
  19. Client Access server %1 running Exchange version %2 tried to find a Client Access server in Active Directory site %3. Service ...
  20. Client Access server %1 tried to proxy Exchange Web Services traffic to %2. This failed because the calling Active Directory ...
  21. Client Access server %1 tried to proxy Exchange Web Services traffic to %2. This failed because the calling Active Directory ...
  22. Client Access server %1 tried to proxy Exchange Web Services traffic to Client Access server %2. This failed because the ...
  23. Client Access server %1 tried to proxy Exchange Web Services traffic to Client Access server %2. This failed because the ...
  24. Client Access server %1 tried to proxy Exchange Web Services traffic to Client Access server %2. This failed because the ...
  25. Client Access server %1 tried to proxy Exchange Web Services traffic to Client Access server %2. This failed because the ...
  26. Client Access server %1 tried to proxy Exchange Web Services traffic to Client Access server %2. This failed because the ...
  27. Client Access server %1 tried to proxy Exchange Web Services traffic to Client Access server %2. This failed because the ...
  28. Client Access server %1 tried to proxy Exchange Web Services traffic. This failed for user %2 because this user is a member ...
  29. Client Access server %1 tried to proxy Exchange Web Services traffic. This failed for user %2 because this user is a member ...
  30. Client Access server %1 tried to proxy Outlook Web App traffic to Client Access server %2. This failed because one of these ...
  31. Client Access server %1 tried to proxy Outlook Web App traffic to Client Access server %2. This failed because one of these ...
  32. Client Access server %1, running Exchange version %2, is proxying Exchange Web Services traffic to Client Access server %3, ...
  33. Client Access server %1, running Exchange version %2, is proxying Exchange Web Services traffic to Client Access server %3, ...
  34. Client Access server {0} in domain {1} encountered an error while connecting to domain {2} to retrieve delivery report data. ...
  35. Client Access server: {0} Mailbox server: {1} Mailbox database: {2} Mailbox: {3} Port: {4} Connection type: {5} TrustAnySSLCertificate: ...
  36. Client Access server: {0} Mailbox server: {1} Mailbox database: {2} Mailbox: {3} Port: {4} Connection type: {5} TrustAnySSLCertificate: ...
  37. Client certificate authentication couldn't be determined because an unexpected failure occurred. {0} failed with error {1}. ...
  38. Client requests that take less than 2 seconds round trip are considered successful and a positive experience for the end ...
  39. Client-Reported Failures - Autodiscover Failures is the number of client-reported free/busy requests that failed due to Autodiscover ...
  40. Client-Reported Failures - Connection Failures is the number of client-reported free/busy requests that failed because the ...
  41. Client-Reported Failures - Partial or Other Failures is the number of client-reported free/busy requests that failed due ...
  42. Client-Reported Failures - Total is the total number of client-reported free/busy requests that failed since the service ...
  43. Client-side Cache Hits is the total number of calls made to GetServerForDatabase that do not have to make an RPC to the server ...
  44. Client-side Cache Misses is the total number of calls made to GetServerForDatabase that have made an RPC to the server because ...
  45. Client-side Calls ReadThrough is the number of times GetServerForDatabase is called with the ReadThrough flag. The ReadThrough ...
  46. Client-side Calls/Sec is the rate at which remote clients are querying for the current server hosting a particular mailbox ...
  47. Client-side RPC Calls is the total number of calls made to GetServerForDatabase that have to make an RPC to the server. It ...
  48. Closed campus exceptions The mailbox can send e-mail to or receive e-mail from anyone in this list, even if the closed campus ...
  49. Closed campus exceptions To turn on the closed campus policy, which blocks external e-mail traffic, go to Manage My Organization ...
  50. Cluster node {2} will require the software update as described in Microsoft Knowledge Base article 898790 if it is upgraded ...
  51. Cluster {1} path on server {2} is set to the default location. For optimum performance, this path should point to a fast ...
  52. Cluster {2} is a two node cluster with a node majority set but no witness has been configured. A node majority set with file ...
  53. cluster.exe did not succeed, but {0} was not a {2} error code. Not attempting any other servers. This may be an expected ...
  54. cluster.exe failed to contact the cluster. RPC_S_SERVER_UNAVAILABLE. The cluster network name resource may be offline or ...
  55. Coexistence between Exchange Server 2010 and Exchange Server versions older than Exchange Server 2007 SP2 in the same Active ...
  56. Collect: Domain Controllers: LDAP Searches time limit exceeded per minute (Interval=1 min, Tolerance=5, MaxSampleSeparation=120). ...
  57. Collect: Edge Transport: MSExchange Connection Filtering Agent: Connections on IP Allow List Providers (Report Collection). ...
  58. Collect: Edge Transport: MSExchange Connection Filtering Agent: Connections on IP Block List Providers (Report Collection). ...
  59. Collect: Edge Transport: MSExchange Protocol Analysis Agent: Senders Blocked Because of Local Open Proxy (Report Collection). ...
  60. Collect: Edge Transport: MSExchange Protocol Analysis Agent: Senders Blocked Because of Remote Open Proxy (Report Collection). ...
  61. Collect: Edge Transport: MSExchange Recipient Filter Agent: Recipients Rejected by Recipient Validation (Report Collection). ...
  62. Collect: Edge Transport: MSExchange Sender ID: Messages Validated with a Fail - Malformed Domain Result (Report Collection). ...
  63. Collect: Edge Transport: MSExchange Sender ID: Messages Validated with a Fail - Non-existent Domain Result (Report Collection). ...
  64. Collect: Edge Transport: MSExchange Sender ID: Messages Validated with a Fail - Not Permitted Result (Report Collection). ...
  65. Collect: Hub Transport: MSExchange Connection Filtering Agent: Connections on IP Allow List Providers (Report Collection). ...
  66. Collect: Hub Transport: MSExchange Connection Filtering Agent: Connections on IP Block List Providers (Report Collection). ...
  67. Collect: Hub Transport: MSExchange Protocol Analysis Agent: Senders Blocked Because of Local Open Proxy (Report Collection). ...
  68. Collect: Hub Transport: MSExchange Protocol Analysis Agent: Senders Blocked Because of Remote Open Proxy (Report Collection). ...
  69. Collect: Hub Transport: MSExchange Recipient Filter Agent: Recipients Rejected by Recipient Validation (Report Collection). ...
  70. Collect: Hub Transport: MSExchange Sender ID Agent: Messages Validated with a Fail - Malformed Domain Result (Report Collection). ...
  71. Collect: Hub Transport: MSExchange Sender ID Agent: Messages Validated with a Fail - Non-existent Domain Result (Report Collection). ...
  72. Collect: Hub Transport: MSExchange Sender ID Agent: Messages Validated with a Fail - Not Permitted Result (Report Collection). ...
  73. CollectAndReport" means that the script should both collect the data from the servers and then process them to produce the ...
  74. CollectOverMetrics reads from the event logs of servers in a DatabaseAvailabilityGroup to gather information on database ...
  75. CollectReplicationMetrics collects data from performance counters related to database replication. The script gathers counter ...