Exchange Server 2016

  1. The goal for Time-Based Assistants is to run on all active databases, unless processing is disabled via configuration. Diagnostic ...
  2. The goal for Time-Based Assistants is to run on all active databases, unless processing is disabled via configuration. Diagnostic ...
  3. The goal for Time-Based Assistants is to schedule workcycle time intervals and complete scheduled work, where every mailbox ...
  4. The goal for Time-Based Assistants is to schedule workcycle time intervals and complete scheduled work, where every mailbox ...
  5. The grammar file named "{0}" with rule "{1}" does not have a valid RecoEvent declaration. Make sure the first node after ...
  6. The group "{0}" can't be managed by recipient "{1}". The owner of the group should have the following recipient type details: ...
  7. The group "{0}" is not managed by any recipient but "{1}" is true. Please set "{1}" to false or choose a recipient to manage ...
  8. The group couldn't be created because the limit for the number of groups has been reached. This could be the limit for the ...
  9. The group couldn't be created because the specified owner SMTP address is invalid. Please try again with another address. ...
  10. The group couldn't be created because this group ID is already being used. Please try a different group ID for this group. ...
  11. The group metrics cookie for this domain has expired.%1 Domain: %2 Last updated: %3 Time since last update: %4 Maximum allowed: ...
  12. The group name contains the word "{0}", which isn't allowed in group names in your organization. Please rename your group. ...
  13. The group name you specified isn't valid. Please make sure the length of the name is under 256 characters and that it doesn't ...
  14. The group's alias must be included in the request. It can contain at most 64 alphanumeric characters, underscores, and periods. ...
  15. The HandleADDriverTimeoutInPowershell.ps1 script attempted to restart the following application pools:%1. During execution ...
  16. The HandleADDriverTimeoutInPowershell.ps1 script has executed successfully without errors. The following application pools ...
  17. The header of the free/busy security descriptor obtained from mailbox {0} is not supported. The header length should be at ...
  18. The health alert value of '{1}' on exchange server '{0}' is '{2}', that may cause some special unhealthy state of the server. ...
  19. The health manager is reporting that recycling the {0} app pool has failed to restore health and attempts to mark the protocol ...
  20. The health manager is reporting that recycling the {0} app pool has failed to restore health and it has requested the protocol ...
  21. The health manager is reporting that recycling the {0} app pool has failed to restore health and it has tried to fail over ...
  22. The health test of the Monitoring WCF Service on server '{0}' failed. Verify that the DAG Management service (MSExchangeDagMgmt) ...
  23. The health test of the Monitoring WCF Service on server '{0}' timed out after '{1}'. Verify that the DAG Management service ...
  24. The health test of the TCP listener for the Microsoft Exchange Replication service on server '{0}' failed. This server cannot ...
  25. The heartbeat connection for server {2} appears to have a DNS search order. Heartbeat connections should not have the DNS ...
  26. The heartbeat connection for server {2} appears to have the default gateway address set. Heartbeat connections should not ...
  27. The heartbeat connection for server {2} appears to have the primary WINS address set. Heartbeat connections should not have ...
  28. The heartbeat connection for server {2} is first in the TCP/IP binding order and not the public connection. This may cause ...
  29. The home server of the specified sender '{3}' (mail address: {4}) is {2} whereas the entered Exchange server was {1}. The ...
  30. The Host Controller service is not running. Service restart was tried already but did not solve the problem. The service ...
  31. The host is not responding. This code may be caused by transient network conditions. Exchange will automatically try again ...
  32. The HostServer attribute of a database copy cannot be empty. It must be set to a valid server. This may be due to a corrupted ...
  33. The HTML report is written as a set of tables. The first summarises all of the moves, mounts, and failovers by grouping them ...
  34. The HTTPS protocol binding does not exist in default web site in '{0}'. Please make sure install-ExchangeCertificate for ...
  35. The Hub Transport server role and the IIS Simple Mail Transfer Protocol (SMTP) service are both installed on server {0}. ...
  36. The Hub Transport server role and the IIS Simple Mail Transfer Protocol (SMTP) service are both installed on server {2}. ...
  37. The hybrid configuration object has been upgraded to Exchange 2013. You must run the Update-HybridConfiguration from an Exchange ...
  38. The hybrid detection engine will try to connect to Office 365 using the provided tenant credentials to run the Get-OrganizationConfig ...
  39. The Identity and OrganizationalUnit parameters shouldn't be used at the same time when the IgnoreDefaultScope parameter is ...
  40. The identity of the Database Availability Group (aka DAG) for which to generate the report. The value can be any object that ...
  41. The identity of the database availability probe. Use Get-MonitoringItemIdentity -Identity Outlook or Outlook.Protocol to ...
  42. The Identity parameter must be filled in with a target computer which can be either local or remote. The optional EngineUpdatePath ...
  43. The Identity parameter must contain a distinguished name when the IgnoreDefaultScope switch is used. Specify a valid DN with ...
  44. The identity {0} is incomplete. For this operation, you must specify the full identity. Only the server name may be left ...
  45. The idle time between replication cycles for directory replication connector '{3}' is longer than {8} hours. If cross-site ...
  46. The IgnoreCase attribute can only be used with a regular expression in the ItemHasKnownEntity rules. Remove the IgnoreCase ...
  47. The IIS FileCacheMaxHandles value on server {2} has been set manually. The default value is 800 handles for each 32 MB of ...
  48. The IIS path {0} couldn't be found to modify the forms-based authentication setting. It may have been removed recently. Verify ...
  49. The IIS path {0} couldn't be found while attempting to query its forms-based authentication setting (metabase property ID ...
  50. The IIS virtual directory "{0}" for the management Web service is missing. The task is trying to create it and apply the ...
  51. The IIS virtual directory "{0}" is not hosted on the local server (FQDN: "{1}"). The task can't create a virtual directory ...
  52. The IIS Web Services root (metabase path "/LM/W3SVC") can't be accessed. Make sure IIS is running and is configured correctly. ...
  53. The IMAP4 '{4}' setting is enabled in the registry on server {2}. This setting can increase performance for message enumeration. ...
  54. The IMAP4 service failed to connect using SSL or TLS encryption. No valid certificate is configured to respond to SSL/TLS ...
  55. The Import-UMPrompt cmdlet couldn't be run to upload the specified audio file because the Windows Desktop Experience role ...
  56. The In-Place Hold search failed because the mailbox database isn't being indexed by Exchange Search. Search criteria = '{0}'; ...
  57. The inactive mailbox "{0}" doesn't have needed properties: ExchangeGuid, DistinguishedName, LegacyExchangeDN or OrganizationalUnit. ...
  58. The inactive mailbox has been recovered. To preserve data until you obtain a valid license, we have enabled Single Item Recovery ...
  59. The incoming server name can't be longer than 126 characters. Please verify the incoming server name is within that limit, ...
  60. The index entry for the specifed request is missing information that's used to locate the request. Deleting the index entry. ...
  61. The index entry refers to a different source user than the job. Job SourceUser value: '{0}'. Index Entry SourceUser value: ...
  62. The index entry refers to a different target user than the job. Job TargetUser value: '{0}'. Index Entry TargetUser value: ...
  63. The index entry was for a different organization than the job. Job OrganizationId value: '{0}'. Index Entry OrganizationId ...
  64. The inference training feeder for mailbox %1 picked messages in the following proportions. Inbox: %2. Deleted Items: %3. ...
  65. The inference training feeder for mailbox %1 picked the following number of messages. MaxTotalItemCount : %2. TotalItemCount: ...
  66. The input string "{0}" isn't formatted correctly. An example of an IP range is "192.168.1.1-192.168.255.255" where "192.168.1.1" ...
  67. The input string "{1}" isn't a valid recipient filter for e-mail address policy "{0}" with lowest priority. To upgrade the ...
  68. The input value '{2}' is outside the valid range of values that can be represented by ByteQuantifiedSize. The valid range ...
  69. The input XML provided is empty. If you continue, all existing mail public folders in Active Directory will be deleted. Do ...
  70. The installed version of Exchange 2010 cannot be upgraded. You must remove the existing Edge Transport server role using ...
  71. The instant messaging notifications payload size has grown too large for user "%1". The notifications infrastructure is either ...
  72. The Instant Search test transaction failed. A zero hit count was returned by querying the keyword '{0}' in the inbox of user ...
  73. The Instant Search test transaction for the database '{0}' has failed {1} times running every {2} seconds. The last probe ...
  74. The Instant Search test transaction querying the keyword '{0}' in the inbox of user '{1}' failed with an exception.Exception ...
  75. The insufficient redundancy monitor has not been running for {0} minutes. It was last run at {Probe.StateAttribute3}; The ...