Exchange Server 2016

  1. The value for the Microsoft Exchange Site Replication Service '{4}' registry entry on server {2} is less than {8}. This configuration ...
  2. The value for the Microsoft Exchange System Attendant '{4}' registry entry on server {2} is less than {8}. This configuration ...
  3. The value for the minimum Extensible Storage Engine (ESE) cache on server {2} has changed. This configuration is not generally ...
  4. The value for the OrganizationConfigHash parameter is null or empty. This likely means that your Office 365 tenant organization ...
  5. The value for the POP3 '{4}' registry entry is set higher than {8} bytes on server {2}. Communication errors may occur. Current ...
  6. The value for the POP3 '{4}' registry entry is set lower than {8} bytes on server {2}. Communication errors may occur. Current ...
  7. The value for the POP3 '{4}' registry entry on server {2} has changed. In some scenarios, this can increase performance. ...
  8. The value for the transaction log file size for database {3} on server {2} changed. This configuration isn't supported. Current ...
  9. The value of an SMTP supervision list entry must consist of tags separated by commas, followed by the SMTP address. It must ...
  10. The value of the CustomRecipientWriteScope parameter must be the same as the implicit write scope of the associated management ...
  11. The value of the EnableAsSharedConfiguration parameter can't be true for an organization that has a SharedConfiguration value. ...
  12. The value of the Windows Management Instrumentation (WMI) setting '{4}' on cluster node {2} differs from that on node {1} ...
  13. The value provided for the ResultSize parameter must be an integer from {0} to {1}. Check the value you provided, and try ...
  14. The value provided in the {0} parameter contains leading or trailing spaces. Remove the leading or trailing spaces, and try ...
  15. The value specified for the age at which old message tracking log files will be removed is not valid. The default value %1 ...
  16. The value specified for variant '{2}' does not match its type. Only values of type '{3}' in format '{4}' are allowed for ...
  17. The value that you've set for {0} won't work. When you customize a field here, the value must be a whole number greater than ...
  18. The value you entered isn't a valid regular expression. A regular expression can contain plain text and placeholders to represent ...
  19. The value you specified for the "{0}" parameter exceeds the maximum allowable length, {1}. Provide a shorter value and try ...
  20. The value you specify with the WritableRecipient parameter must be a valid User, UserMailbox, Contact, MailContact or SystemMailbox ...
  21. The value {0} contains a number format specifier that's not valid. It should be in the form " ]". In this form, the prefix ...
  22. The value, '{0}', specified with the ConfigWriteScope parameter isn't valid. The configuration write scope must match the ...
  23. The values for the UseIncludedMailboxDatabases and the UseExcludedMailboxDatabases parameters can't be set to $true at the ...
  24. The values of property {0} are different and should match. The local organization relationship {1} has value {2}, and the ...
  25. The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector ...
  26. The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector ...
  27. The VerifyGlobalRoutingEntry parameter will be ignored, either because the dial plan doesn't support global call routing ...
  28. The version data on the Exchange server '{0}' is invalid. Setup will treat the server as a pre-Exchange 2016 server. Message: ...
  29. The version of '{5}' installed on cluster node {2} may cause failures if mount points are created. If you intend to use mount ...
  30. The version of '{5}' installed on cluster node {2} may cause volume mount point failures. Review Microsoft Knowledge Base ...
  31. The version of '{5}' installed on server {2} can cause Active Directory replication issues. Refer to Microsoft Knowledge ...
  32. The version of '{5}' installed on server {2} can cause kernel memory allocation errors. An update is available from the vendor. ...
  33. The version of '{5}' installed on server {2} can cause working sets to be improperly trimmed when Terminal Services is used. ...
  34. The version of '{5}' installed on server {2} is incompatible with {0} and can cause disk errors. If you are experiencing ...
  35. The version of '{5}' installed on server {2} may cause connectivity issues in some networking configurations. Download and ...
  36. The version of '{5}' installed on server {2} may cause connectivity issues in some networking configurations. If you are ...
  37. The version of '{5}' installed on server {2} may cause connectivity issues in some networking configurations. If you are ...
  38. The version of '{5}' installed on server {2} may cause mail flow issues with X.400 connectors resident on this server. If ...
  39. The version of '{5}' installed on server {2} may cause performance issues. Please install Windows Server 2003 Service Pack ...
  40. The version of ClientAccessArray to be set to is {0}. However, the minimum version of ClientAccessArray that the Set-ClientAccessServer ...
  41. The version of Internet Information Services (IIS) that is running on server '{0}' can't be determined. This error can occur ...
  42. The version of offline address book "{0}" is older than Exchange 2007. Run the following command to upgrade this offline ...
  43. The version of PowerPath on cluster node {2} (version {9}) is different than on node {1} (version {8}). This is not recommended ...
  44. The version of the Active Directory Connector (ADC) on server {2} is not compatible with the current Active Directory forest ...
  45. The version of the Edge Subscription matches with only some of the Mailbox servers in the subscribed site. EdgeSync will ...
  46. The version of the free/busy security descriptor obtained from mailbox {0} is not supported. The expected version is {1}. ...
  47. The version of the Microsoft Exchange Information Store service is incompatible with the version of the Exchange System Manager. ...
  48. The version of the operating system on the server '{0}' is later than that on the local computer. Data collection and analysis ...
  49. The version of the Recipient Update Service on Exchange server {2} is not compatible with the current Active Directory forest ...
  50. The version of this organization doesn't match the exchange upgrade bucket source version. Organization version: "{0}". Bucket ...
  51. The version of {5} installed on server {2} may cause high CPU utilization for the Inetinfo process when message tracking ...
  52. The version of {5} installed on server {2} may cause messages to public folders to queue before the hierarchy can replicate. ...
  53. The version of {5} installed on server {2} may cause the Inetinfo process to use 100% of CPU when Active Directory queries ...
  54. The version store for this instance (%1) cannot grow because it is receiving Out-Of-Memory errors from the OS. It is likely ...
  55. The version store for this instance (%1) has a long-running transaction that exceeds the maximum transaction size. Current ...
  56. The version store for this instance (%1) has reached its maximum size of %2Mb. It is likely that a long-running transaction ...
  57. The version store for this instance (%4) cannot grow because it is receiving Out-Of-Memory errors from the OS. It is likely ...
  58. The version store for this instance (%4) has a long-running transaction that exceeds the maximum transaction size. Current ...
  59. The version store for this instance (%4) has reached its maximum size of %5Mb. It is likely that a long-running transaction ...
  60. The virtual directory "{0}" allows Basic authentication but doesn't require an SSL-encrypted connection. This means that ...
  61. The virtual directory "{0}" isn't configured correctly. This server has the Mailbox server role installed, so HTTP compression ...
  62. The virtual directory '{0}' on Client Access server '{1}' isn't enabled for anonymous calendar sharing, although the sharing ...
  63. The voice message that you tried to listen to is protected with Information Rights Management. You can only listen to this ...
  64. The VoIP platform encountered a TLS exception during the call with ID "%1". Details: "%2". This exception occurred at the ...
  65. The VoIP platform encountered an exception %1 during the call with ID "%2". This exception occurred at the Microsoft Exchange ...
  66. The VoIPSecurity parameter on the dial plan can't be set to SIPSecured. The address field "{0}" on IP gateway "{1}" isn't ...
  67. The volume '{0}' mounted at '{1}' will not be formatted because it falls within the initial safe holding period of '{2}'. ...
  68. The volume '{0}' mounted at '{1}' will not be formatted because it is either not an Exchange volume, or has database mount ...
  69. The Volume Manager could not fix up the mount point for database '{0}' to point to volume '{1}' because the volume already ...
  70. The Volume Manager failed to create the required EDB and LOG folder directories for database '{0}' on spare volume '{1}'. ...
  71. The volume with GUID path '{0}' has more than {3} database mount points under root path '{1}'. Database Mount Points: {2}. ...
  72. The Web management interface couldn't redirect user '%1' from site '%2' to site '%3' and will let the user continue to the ...
  73. The web request '{0}' hits timeout ({1}). This indicates the IIS service is in bad state that we need to terminate w3wp processes ...
  74. The WebReady Document Viewing cache has reached its size limit. It may take several minutes for the temporary files to be ...
  75. The WebReady Document Viewing manager didn't initialize. It will try again. If the problem continues, restart Outlook Web ...