Exchange Server 2016

  1. PowerShell Runspaces - Average Active Time is the average time, in seconds, that a Windows PowerShell runspace stays active ...
  2. PowerShell Runspaces - Average Creation Time is the average time, in seconds, taken by the Exchange Administration Center ...
  3. PowerShell Runspaces - Average Creation Time is the average time, in seconds, taken by the Exchange Administration Center ...
  4. PowerShell Runspaces - Peak Active is the largest number of Windows PowerShell runspaces simultaneously active in the Exchange ...
  5. PowerShell Runspaces - Peak is the largest number of Windows PowerShell runspaces simultaneously loaded in the Exchange Control ...
  6. PowerShell Runspaces - Total is the total number of Windows PowerShell runspaces loaded in the Exchange Control Panel since ...
  7. PowerShell Runspaces/sec is the number of Windows PowerShell runspaces that are created per second in the Exchange Control ...
  8. Pre-read page checksum error %4 occurred. If this error persists, please restore the database from a previous backup. For ...
  9. predicate contains extension that start with '.': {1}. These parameters will not match any file extensions. Please don't ...
  10. Preferred bridgehead servers are selected for intersite replication, while none these servers can replicate the directory ...
  11. PrepareAD has either not been run or has not replicated to the domain controller used by Setup. Setup will attempt to use ...
  12. PrepareDomain for domain {0} has partially completed. Because of your Active Directory site configuration, you must wait ...
  13. PrepareDomain for domain {0} was unable to add the group {1} to the group {2} on domain controller {5}, because the current ...
  14. Previous log's accumulated segment checksum mismatch in logfile %4, Expected: %5, Actual: %6. For more information, click ...
  15. Primary and connection specific DNS suffixes are not appended on server {2}. Please select 'Append primary and connection ...
  16. Primary DNS ({1}) for server {2} responded successfully to both UDP and TCP connections but the returned responses are different. ...
  17. Primary DNS servers for server {2} responded successfully to the connection requests by the tool but events showing DNS connectivity ...
  18. Primary external DNS ({1}) for SMTP instance '{3}' on server {2} responded successfully to both UDP and TCP connections but ...
  19. Probe {0} failed on {Probe.MachineName} beginning at {Monitor.FirstAlertObservedTime} (UTC). Failing Reason: {Probe.Error} ...
  20. Probe {0} failed on {Probe.MachineName} beginning at {Monitor.FirstAlertObservedTime} (UTC). Failing Reason: {Probe.Error} ...
  21. Probe {0} failed on {Probe.MachineName} beginning at {Monitor.FirstAlertObservedTime} (UTC). Failing Reason: {Probe.Error} ...
  22. Probe {0} failed on {Probe.MachineName} beginning at {Monitor.FirstAlertObservedTime} (UTC). Failing Reason: {Probe.Error} ...
  23. Probe {0} failed on {Probe.MachineName} beginning at {Monitor.FirstAlertObservedTime} (UTC). Failing Reason: {Probe.Error} ...
  24. Probe.ResultName} Failed with Error message: {Probe.Error} beginning at {Monitor.FirstAlertObservedTime} (UTC). Details below: ...
  25. Probe: {Probe.ResultName} Error: {Probe.Error} Exception: {Probe.Exception} Details: {Probe.FailureContext} Log: {Probe.ExecutionContext} ...
  26. Probe: {Probe.ResultName}DL Expansion is failing for user {Probe.StateAttribute1}. User's org id is {Probe.StateAttribute2}. ...
  27. Probe: {Probe.ResultName}Journal Archiving is unable to resolve user for tenant {Probe.StateAttribute1}. Here is the detailed ...
  28. Probe: {Probe.ResultName}Journal filter agent is dropping valid incoming journal for following org: {Probe.StateAttribute1}. ...
  29. Probe: {Probe.ResultName}Journaling is failing on {Probe.MachineName} in function {Probe.StateAttribute1}MessageId {Probe.StateAttribute2}Org ...
  30. Probe: {Probe.ResultName}Latency: {Probe.SampleValue}msError: {Probe.Error}Details: {Probe.FailureContext}Log: {Probe.ExecutionContext} ...
  31. Probe: {Probe.ResultName}Mailbox guid: {Probe.StateAttribute2}In Org: {Probe.StateAttribute3}Is archive: {Probe.StateAttribute4}With ...
  32. Probe: {Probe.ResultName}Mailbox guid: {Probe.StateAttribute2}In Org: {Probe.StateAttribute3}Is archive: {Probe.StateAttribute4}With ...
  33. Probe: {Probe.ResultName}Mailbox guid: {Probe.StateAttribute2}In Org: {Probe.StateAttribute3}Is archive: {Probe.StateAttribute4}With ...
  34. Probe: {Probe.ResultName}Mailbox guid: {Probe.StateAttribute2}In Org: {Probe.StateAttribute3}Is archive: {Probe.StateAttribute4}With ...
  35. Probe: {Probe.ResultName}Mailbox guid: {Probe.StateAttribute2}In Org: {Probe.StateAttribute3}Message: {Probe.StateAttribute4}If ...
  36. Probe: {Probe.ResultName}Mailbox guid: {Probe.StateAttribute2}In Org: {Probe.StateAttribute3}With stack trace: {Probe.StateAttribute5} ...
  37. Probe: {Probe.ResultName}Mailbox guid: {Probe.StateAttribute2}Sid: {Probe.StateAttribute3}With stack trace: {Probe.StateAttribute4}Get ...
  38. Problems are preventing proper operation of database '%1' ('%2'). The failure may be corrected by remounting the database. ...
  39. Problems are preventing proper operation of database '%4' ('%5'). The failure may be corrected by remounting the database. ...
  40. Process %1 (PID=%2) Component %3. Encountered a timeout while trying to access remote performance counter '%4'. Remote server ...
  41. Process %1 (PID=%2) Component %3. Encountered an exception while trying to read remote performance counter '%4'. Exception: ...
  42. Process %1 (PID=%2) Forest %3. Exchange Active Directory Provider could not find minimal required number of suitable domain ...
  43. Process %1 (PID=%2) Forest %3. Exchange Active Directory Provider couldn't find minimal required number of suitable Global ...
  44. Process %1 (PID=%2) Forest %3. Exchange Active Directory Provider has discovered the following servers with the following ...
  45. Process %1 (PID=%2) Forest %3. Exchange Active Directory Provider will use the servers from the following list: Domain Controllers: ...
  46. Process %1 (PID=%2) Forest %3. No minimal required number of Domain Controller server is up in the local site '%4'. Exchange ...
  47. Process %1 (PID=%2) Forest %3. No minimal required number of Global Catalog server is up in the local site '%4'. Exchange ...
  48. Process %1 (PID=%2) Forest %3. No minimal required number of suitable Domain Controller servers were found in the local site ...
  49. Process %1 (PID=%2) Forest %3. No minimal required number of suitable Global Catalog servers were found in the local site ...
  50. Process %1 (PID=%2) Forest %3. The configuration domain controller specified in a call to SetConfigDCName (%4) is unreachable. ...
  51. Process %1 (PID=%2) Forest %3. The configuration domain controller specified in a call to SetConfigDCName (%4) was not found ...
  52. Process %1 (PID=%2). %3 Default Accepted Domains are found in current topology. Maybe it is caused by a configuration error. ...
  53. Process %1 (PID=%2). %3 is a read-only domain controller. Exchange Active Directory Provider requires that domain controllers ...
  54. Process %1 (PID=%2). A request to Directory Server %3 did not return a result within %4 seconds and is being abandoned. The ...
  55. Process %1 (PID=%2). Active Directory topology for %3 could not be discovered in %4 seconds. Review the Application log for ...
  56. Process %1 (PID=%2). AD Session operation failed on DC %3 because this server is not suitable at the moment. DomainController ...
  57. Process %1 (PID=%2). AD Session used by the process is marked as IsScopedToRetiredTenant. Tenant DN: %3, error details: %4. ...
  58. Process %1 (PID=%2). ADHealthCache successfully read AD health result which is due to replication on the DC %3. The value ...
  59. Process %1 (PID=%2). An error occurred while loading the registry configuration for the Microsoft Exchange Active Directory ...
  60. Process %1 (PID=%2). An error ocurred while creating Wcf client for %3 from configuration file, default settings will be ...
  61. Process %1 (PID=%2). An LDAP %3 operation succeeded but took %4 milliseconds - Server=%5. Base DN=%6, Filter=%7, Scope=%8. ...
  62. Process %1 (PID=%2). An LDAP search call to Directory Server %3 failed - Error code=%4 (%8). Base DN=%5, Filter=%6, Scope=%7. ...
  63. Process %1 (PID=%2). An LDAP search result to Directory Server %3 exceeded the administrative size limit.Only the first %4 ...
  64. Process %1 (PID=%2). Attempting %5: forest %3 secure channel domain controller is set to %4 which is in maintenacne mode. ...
  65. Process %1 (PID=%2). Attempting %5:, DCLocator cache DC for forest %3 is set to %4 which is in maintenacne mode. Will retry ...
  66. Process %1 (PID=%2). Configuration object %3 read from %4 failed validation and will be excluded from the result set. Set ...
  67. Process %1 (PID=%2). Configuration object %3 read from %4 failed validation. A partially valid object will be returned. Set ...
  68. Process %1 (PID=%2). Configuration object %3 read from %4 failed validation. DataValidationException will be thrown. Set ...
  69. Process %1 (PID=%2). Contacting server %3 for RUS RPC service returned RPCException '%4'. Server will not be used for RUS ...
  70. Process %1 (PID=%2). Deleted Notification request with RootId (%3) will be ignored. Maximum number of AD Notifications per ...
  71. Process %1 (PID=%2). Deleted object notification received. ChangeType=%3; Context=%4; Id=%5; LastknownParent=%6; Type=%7; ...
  72. Process %1 (PID=%2). Domain controller %3 was not found when DNS was queried for the service location(SRV) resource records ...
  73. Process %1 (PID=%2). DSAccess could not discover the Fully Qualified Domain Name (FQDN) of local server with Exception %3. ...
  74. Process %1 (PID=%2). Error %3 occurred when DNS was queried for the service location (SRV) resource record used to locate ...
  75. Process %1 (PID=%2). Error DNS_ERROR_RCODE_NAME_ERROR ( 3) occurred when DNS was queried for the servicelocation (SRV) resource ...