Exchange Server 2016

  1. The Exchange Server User Monitor (ExMon) RPC data indicates that client restrictions are causing high load on this server. ...
  2. The Exchange Server User Monitor (ExMon) RPC data indicates that clients are building new views, which is causing high load ...
  3. The Exchange Server User Monitor (ExMon) RPC data indicates that clients are performing bulk operations. Bulk operations ...
  4. The Exchange Server User Monitor (ExMon) RPC data indicates that clients are performing costly bulk operations. These operations ...
  5. The Exchange Server User Monitor (ExMon) RPC data indicates that clients are performing online operations. Online operations ...
  6. The Exchange Server User Monitor (ExMon) RPC data indicates that clients are performing online operations. Online operations ...
  7. The Exchange Server User Monitor (ExMon) RPC data indicates that clients are performing synchronization operations. Synchronization ...
  8. The Exchange Server User Monitor (ExMon) RPC data indicates that the user '{3}' had a long-running MAPI bulk operation of ...
  9. The Exchange Server User Monitor (ExMon) RPC data indicates that the user '{3}' had a long-running MAPI operation of type ...
  10. The Exchange Server User Monitor (ExMon) RPC data indicates that the user '{3}' had a long-running MAPI operation of type ...
  11. The Exchange Server User Monitor (ExMon) RPC data indicates that the user '{3}' had a long-running MAPI operation of type ...
  12. The Exchange Server User Monitor (ExMon) RPC data indicates that the user '{3}' had a long-running MAPI operation of type ...
  13. The Exchange Server User Monitor (ExMon) RPC data indicates that the user '{3}' had a long-running MAPI operation of type ...
  14. The Exchange Server User Monitor (ExMon) RPC data indicates that the user '{3}' had a long-running MAPI operation of type ...
  15. The Exchange Server User Monitor (ExMon) RPC data indicates that the user '{3}' had a long-running MAPI synchronization operation ...
  16. The Exchange Server User Monitor (ExMon) RPC data indicates that the user '{3}' is causing high load on this server. FindRow ...
  17. The Exchange Server User Monitor (ExMon) RPC data indicates that the user '{3}' is causing high load on this server. Restrictions ...
  18. The Exchange Server User Monitor (ExMon) RPC data indicates that the user '{3}' is performing a costly MAPI operation "{4}". ...
  19. The Exchange Server User Monitor (ExMon) RPC data indicates that the user '{3}' is performing a costly MAPI operation "{4}". ...
  20. The Exchange Server User Monitor (ExMon) RPC data indicates that the user '{3}' is performing bulk operations of type MAPI ...
  21. The Exchange Server User Monitor (ExMon) RPC data indicates that the user '{3}' is performing normal bulk operations of type ...
  22. The Exchange Server User Monitor (ExMon) RPC data indicates that the user '{3}' is performing normal synchronization operations ...
  23. The Exchange Server User Monitor (ExMon) RPC data indicates that the user '{3}' is performing online operations of type MAPI ...
  24. The Exchange Server User Monitor (ExMon) RPC data indicates that the user '{3}' is performing online operations of type MAPI ...
  25. The Exchange Server User Monitor (ExMon) RPC data indicates that the user '{3}' is performing synchronization operations ...
  26. The Exchange Server User Monitor (ExMon) RPC data indicates that the user '{3}' may be building new views, which is causing ...
  27. The Exchange server {2} wasn't found in Active Directory on server {1}. Please provide the CMS name for the Exchange server. ...
  28. The Exchange settings size of {0} is approaching the maximum size {1}. Please run with -ClearHistory or remove unnecessary ...
  29. The Exchange store database '{0}' has had an RPC average latency > {1} msec for last {2}. Database Name: {Monitor.StateAttribute2} ...
  30. The Exchange store database '{0}' has had an RPC average latency > {1} msec for last {2}. Database Name: {Monitor.StateAttribute2} ...
  31. The Exchange store database '{0}' has had at least {1} active background tasks executing for the last {2}. Error: {Probe.Error} ...
  32. The Exchange store database '{0}' has had at least {1} active background tasks executing for the last {2}. Error: {Probe.Error} ...
  33. The Exchange transport on server {2} will not expand membership of distribution groups when checking restrictions. This configuration ...
  34. The Exchange Trusted Subsystem is not a member of the local Administrators group on specified witness server {0}. Error: ...
  35. The Exchange UMIPGateway objects weren't created. Please verify that you're a member of the Organization Management role ...
  36. The Exchange version you're using isn't high enough to view '{0}' sensitive information types. View from a newer server instead. ...
  37. The Exchange Virtual Server can not be upgraded by the Cluster Administrator tool on this computer. To upgrade this Exchange ...
  38. The Exchange Virtual Server can not be upgraded on this cluster node. To upgrade this Exchange Virtual Server, take the System ...
  39. The ExcludeHttpRedirect value was found in the registry. This value is used by Autodiscover, but it can cause problems if ...
  40. The ExcludeHttpsAutodiscoverDomain value was found in the registry. This value is used by Autodiscover, but it can cause ...
  41. The ExcludeHttpsRootDomain value was found in the registry. This value is used by Autodiscover, but it can cause problems ...
  42. The ExcludeScpLookup value was found in the registry. This value is used by Autodiscover, but it can cause problems if your ...
  43. The ExcludeSrvLookup value was found in the registry. This value is used by Autodiscover, but it can cause problems if your ...
  44. The ExcludeSrvRecord value was found in the registry. This value is used by Autodiscover, but it can cause problems if your ...
  45. The executable file "{0}" for the UM worker process doesn't exist. To resolve this issue, copy the executable file located ...
  46. The executable files for all the transport event sinks found in the metabase of server {2} are identified and found on disk. ...
  47. The executing user is not in the current organization. You can specify "BypassSecurityGroupManagerCheck" to "{0}" in Exchange ...
  48. The execution time for the rule has exceeded the monitoring threshold configured in the 'TransportRuleExecutionTimeAlertingThresholdInMilliseconds' ...
  49. The existence of the junk email rule for mailbox %1 can't be confirmed. If the junk email rule doesn't exist, unsafe messages ...
  50. The existing classification rule collection will not be updated because the version of existing rule collection ({1}) is ...
  51. The existing cmdlet extension agent's configuration is invalid. There are two cmdlet extension agents that share the same ...
  52. The existing cmdlet extension agents configuration is invalid because cmdlet extension agents "{1}" and "{2}" share the same ...
  53. The existing trusted publishing domain (TPD) named "{0}" came from a different source than the TPD you are trying to import. ...
  54. The ExistingResponse property was not stamped on virtual directory '{1}' on '{0}'. The return code is {2}. The error message ...
  55. The ExMon trace was captured for {1} seconds. Since it is normal for some users to use large amounts of CPU for periods of ...
  56. The expiration date for the rule has to be later than or the same as the current date. Please update the date and try again. ...
  57. The export for compliance search "{0}" completed with error. Please rerun/retry the export to make sure it finishes successfully. ...
  58. The export for compliance search "{0}" has not finished yet. Please rerun New-ComplianceSearchPackage after it's completed. ...
  59. The export is still in progress. To avoid data loss, please stop the export and wait until the process stopped before close. ...
  60. The export location is not a valid folder path. The export location is a local file system folder or UNC folder and it is ...
  61. The extension is invalid or not supported. LDAP_MATCHING_RULE_BIT_AND(1.2.840.113556.1.4.803) and LDAP_MATCHING_RULE_BIT_OR(1.2.840.113556.1.4.804) ...
  62. The Extensions folder in the ILM installation directory can't be found. Verify that the folder wasn't renamed after the ILM ...
  63. The external e-mail address can't be changed because it's the primary SMTP address. Promote another SMTP address to primary ...
  64. The external IP addresses on the HybridConfiguration Active Directory object were not properly cleared during the upgrade ...
  65. The ExternalDirectoryObjectID of this inactive mailbox still exists and this command can only be executed when inactive mailbox ...
  66. The ExternalLicensingEnabled parameter can't be set to true because the organization isn't federated with the Microsoft Federation ...
  67. The ExternalSenderAdminAddress value is not set. External Sender Admin Notifications cannot be enabled without a valid ExternalSenderAdminAddress. ...
  68. The failover operation on database '{0}' from server '{1}' was canceled because the database is already mounted. The previous ...
  69. The federated domain '{0}' of the user is in the local organizational relationship which normally only contains the domains ...
  70. The Federation certificate with thumbprint "{0}" must have a unique Subject Key Identifier. The Subject Key Identifier "{2}" ...
  71. The federation information returned from remote organization is different from local organization relationship configuration. ...
  72. The Federation mailbox is misconfigured for this organization. Office 365 mailbox access will be disabled until this is resolved. ...
  73. The Federation Metadata URL must specify an absolute path to the federation metadata document. No relative URL is allowed. ...
  74. The Federation or Auth certificate %1 has expired. Renew the certificate to ensure proper functionality of Federation Trust ...
  75. The Federation or Auth certificate %1 will expire in less than 15 days. Renew the certificate soon to ensure proper functionality ...