Exchange Server 2016

  1. There are mailboxes or connectors with delivery restrictions set based on the membership of distribution group '{3}' and ...
  2. There are mailboxes or connectors with delivery restrictions set based on the membership of distribution group '{3}' and ...
  3. There are messages that completed categorizations on server {2} but the queue length appears to be high. This may indicate ...
  4. There are messages waiting in the following queues: "{0}". If you proceed with the removal of Exchange Server, data loss ...
  5. There are more results available than are currently displayed. To view them, increase the value for the ResultSize parameter. ...
  6. There are more results available than are currently displayed. To view them, increase the value of the ResultSize parameter. ...
  7. There are more than ten administrators delegated at the organization level. This may pose a security issue. Number of administrators ...
  8. There are more than ten full administrators delegated at the organization level. This may pose a security issue. Number of ...
  9. There are multiple data classification identity specifications which resolve to a single data classification '{0}' ({1}) ...
  10. There are multiple sensitive information types with the unique identifier '{0}' that are contained in multiple rule packages. ...
  11. There are multiple transient exceptions from the Exchange Store that can negatively impact the user experience. Exception ...
  12. There are no mailbox servers in the database availability group '{0}' that are started. Run Start-DatabaseAvailabilityGroup ...
  13. There are no remote servers that have passed the connectivity tests over port {9}. SMTP command tests cannot be performed. ...
  14. There are no resource custom properties defined that can be applied to this resource mailbox.Resource custom properties can ...
  15. There are no source files under the path:{0}. Use the command Move-DatabasePath -ConfigurationOnly in the Exchange Management ...
  16. There are problems with the Business Productivity Online Suite (BPOS) Header configuration. Outlook Web App is unable to ...
  17. There are problems with the Live Header configuration. Verify the content of the LiveHeaderConfig.xml file. Error message: ...
  18. There are problems with the Live Header configuration. Verify the content of the LiveHeaderConfig.xml file. Error message: ...
  19. There are problems with the O365 Suite SetUserTheme. User.Puid: %1 User.PrincipalName: %2 TrackingGuid: %3 BOX Shell Service ...
  20. There are several possible causes for this code. 1)There is no route for the specified address space. For example, an SMTP ...
  21. There are several possible causes for this code. One of the most common ones is that the mail account does not exist at the ...
  22. There are too many contacts for external automatic reply messages for user %1, so they are being truncated to %2. Automatic ...
  23. There are too many Outlook Web App re-initialization requests. This can cause performance issues. This may be an indicator ...
  24. There aren't any custom organization throttling policies that exist in the current organization. The throttling policy returned ...
  25. There have been too many retries finding paths in the metabase. This is likely a temporary condition, caused by too many ...
  26. There is a case discrepancy with the Exchange server name {2} between the registry and Active Directory. The computer may ...
  27. There is a discrepancy in the Exchange server name {1} between the registry and Active Directory. The computer may have been ...
  28. There is a discrepancy with the Exchange server name {2} between the registry and Active Directory. The computer may have ...
  29. There is a discrepancy with the fully-qualified domain name setting between Active Directory and the metabase for SMTP instance ...
  30. There is a discrepancy with the maximum hop count setting between Active Directory and the metabase for SMTP instance '{3}' ...
  31. There is a discrepancy with the maximum message size setting between Active Directory and the metabase for SMTP instance ...
  32. There is a discrepancy with the maximum session size setting between Active Directory and the metabase for SMTP instance ...
  33. There is a gap in log sequence numbers, last used log file has generation %1. Logfile %2 (generation %3) have been deleted ...
  34. There is a gap in log sequence numbers, last used log file has generation %1. Logfiles %2 to %3 have been deleted so that ...
  35. There is a gap in log sequence numbers, last used log file has generation %4. Logfile %5 (generation %6) have been deleted ...
  36. There is a gap in log sequence numbers, last used log file has generation %4. Logfiles %5 to %6 have been deleted so that ...
  37. There is a gap in sequence number between logfile %1 and the logfiles previous to it. Logfiles %2 to 3 have been deleted ...
  38. There is a gap in sequence number between logfile %4 and the logfiles previous to it. Logfiles %5 to 6 have been deleted ...
  39. There is a pending reboot from a previous installation of a Windows Server role or feature. Please restart the computer and ...
  40. There is a problem communicating with this account. Have the settings changed recently? If you update your settings, click ...
  41. There is a problem logging on to this account. Please confirm that you've entered the correct user name and password, and ...
  42. There is a problem with the asynchronous audit log search servicelet. The servicelet has restarted multiple times in the ...
  43. There is a problem with your text message. This problem is usually caused by different software versions on the origin and ...
  44. There is a processor bottleneck, and less than {8}% of the processor time is in the Exchange process store.exe. It is recommended ...
  45. There is already a backup context open, and only one may be open at a time. It was opened by server %3 at time %4 on %5. ...
  46. There is already a backup context open, but the previous backup context could not be located. Only one backup context may ...
  47. There is already a Key Management Server installed in the Exchange 5.5 site on server "%s". You must remove the existing ...
  48. There is already a Key Management Server installed in this admin group. There can be one KM Server per admin group. You must ...
  49. There is an error in the recipient's mailbox configuration. This code may occur if the categorizer finds a bad or missing ...
  50. There is an error in the recipient's mailbox configuration. This code may occur if the categorizer finds a bad or missing ...
  51. There is an existing server in your Exchange organization that has the same name as the subscribing Edge Transport server. ...
  52. There is at least one occurrence of Event ID {9} in the application log of server {2} within the last 24 hours. Last occurrence ...
  53. There is at least one occurrence of Event ID {9} in the application log of server {2} within the last 24 hours. Last occurrence ...
  54. There is at least one occurrence of Event ID {9} in the Application log of server {2} within the last 24 hours. The last ...
  55. There is at least one occurrence of Event ID {9} in the system log of server {2} within the last 24 hours. This may indicate ...
  56. There is at least one occurrence of Event ID {9} in the system log of server {2} within the last 24 hours. Verify that the ...
  57. There is at least one transport rule(e.g. '{8}') configured to quarantine messages, but there is no quarantine mailbox configured. ...
  58. There is currently no consistency between directories. On the DSA General property page, choose Check Knowledge Consistency. ...
  59. There is currently no remote domain configured as the target delivery domain of your remote tenant. Either add a new remote ...
  60. There is less than five minutes time difference between the timestamp retrieved from the Active Directory ({1}) and Exchange ...
  61. There is more than five minutes time difference between the timestamp retrieved from the Active Directory ({1}) and Exchange ...
  62. There is more than five minutes time difference between the timestamp retrieved from the Active Directory ({9}) and Exchange ...
  63. There is more than five minutes time difference between the timestamp retrieved from the Active Directory service ({9}) and ...
  64. There is more than one MAPI public folder tree in administrative group '{3}'. This may cause access denied errors when accessing ...
  65. There is more than one network router between Exchange server {2} and Active Directory server {1}. This may cause Exchange ...
  66. There is no available domain controller to complete full import. Make sure there is at least one reliable domain controller ...
  67. There is no outbound connector to deliver mail for this domain. Make sure that there's an Outbound Connector of the type ...
  68. There is no valid SMTP Transport Layer Security (TLS) certificate for the FQDN of %1. The existing certificate for that FQDN ...
  69. There is no X.400 address defined in recipient policy '{0}' which does not have a semicolon as the terminating character. ...
  70. There is only one copy of database "{0}", which is hosted on server "{1}". You can use the Remove-MailboxDatabase cmdlet ...
  71. There is only one global catalog server in the Directory Service Access (DSAccess) topology on server {2}. This configuration ...
  72. There may be more results available than are currently displayed because the task couldn't get the proxy addresses of address ...
  73. There was a '{9}' event with Internal Message ID of '{1}' in the application log of server {2} from the source component ...
  74. There was a failure connecting to or otherwise retrieving Data from the Wac Discovery Service. We will fall back to stellent. ...
  75. There was a problem accessing the mailbox. Please contact your email admin. The failure occurred while importing contact ...