Exchange Server 2010

  1. The user version for routing group '{3}' may be changing rapidly on server {2} ({9} version change(s) detected over {8} seconds). ...
  2. The user with extension '{0}' and dial plan '{1}' isn't UM-enabled, or is enabled for UM on a mailbox that isn't supported ...
  3. The user's Exchange Server version is '{0}'. An archive mailbox can be connected to a user with mailboxes on Exchange 2010 ...
  4. The user's external e-mail address isn't a valid SMTP address. Remote access to the mailbox or archive will be disabled. ...
  5. The user's external e-mail address isn't a valid SMTP address. Remote access to the mailbox or archive will be disabled. ...
  6. The user-specified domain controller {0} cannot be used because setup has determined that it must use the schema master domain ...
  7. The value "{0}" isn't a valid mailbox folder permission or role. The valid permissions include "ReadItems, CreateItems, EditOwnedItems, ...
  8. The value "{0}" of the IssuedTo parameter matches more than one certificate in the LocalMachine certificate store. You can ...
  9. The value "{0}" of the parameter SHA1Thumbprint isn't valid. No certificate could be found in the LocalMachine certificate ...
  10. The value "{0}" on the parameter SHA1Thumbprint is invalid. The expected format is 20 bytes in hexadecimal presentation optionally ...
  11. The value for '{4}' is set to {9} bytes on server {2}. This can cause errors for users of Outlook Web Access. A minimum value ...
  12. The value for '{4}' on server {2} is less than {8} and may cause performance degradation for the scanning result thread. ...
  13. The value for '{4}' on server {2} is too low and may cause performance degradation. The current registry value is {9}. Based ...
  14. The value for configuration setting '{4}' for database '{3}' on server {2} has changed (default value: {7}). Current '{4}' ...
  15. The value for configuration setting '{4}' for database '{3}' on server {2} has changed (default value: {7}). This configuration ...
  16. The value for configuration setting '{4}' for database '{3}' on server {2} has changed (default: {7}). This configuration ...
  17. The value for configuration setting '{4}' for database '{3}' on server {2} has changed. This configuration is recommended ...
  18. The value for configuration setting '{4}' for object '{3}' on server {2} has changed. Default value: {8}. Current value: ...
  19. The value for configuration setting '{4}' for public database '{3}' on server {2} has changed. Default: {8} seconds. Current ...
  20. The value for configuration setting '{4}' for public folder database '{3}' on server {2} has changed. Current value: {9}. ...
  21. The value for configuration setting '{4}' for public store '{3}' on server {2} has changed. Default: {8} seconds. Current ...
  22. The value for configuration setting '{4}' for SMTP instance '{3}' on server {2} has changed. Default value: {8}. Current ...
  23. The value for configuration setting '{4}' on server {2} has changed. This can cause mail flow problems. Current value: {9}. ...
  24. The value for parameter {0} can only be specified when moving mailboxes between Exchange organizations and must be in a different ...
  25. The value for setting '{4}' has changed for display specifier '{3}'. This will modify the default behavior for generating ...
  26. The value for the '{0}' counter on server {2} is greater than zero (average value is {3}) and it appears that '{4}' is failing ...
  27. The value for the '{4}' parameter on server {2} is low and could cause instability. Consider increasing the value to 31000 ...
  28. The value for the '{4}' registry entry is set to zero on server {2}. This can cause severe reliability issues and problems ...
  29. The value for the '{4}' registry entry is set to {9} on server {2}. This may cause excessive memory usage by MAPI clients ...
  30. The value for the '{4}' registry entry is set to {9} on server {2}. This may cause excessive memory usage on the server. ...
  31. The value for the '{4}' registry entry is set too high on server {2}. This can cause mail flow problems. Default value: {8} ...
  32. The value for the '{4}' registry entry is set too low on server {2}. This can cause degraded database performance and mail ...
  33. The value for the '{4}' registry entry on server {2} does not match the name of the local computer ({1}). This may cause ...
  34. The value for the '{4}' registry entry on server {2} has changed. Default value: {8} seconds. Current value: {9} seconds. ...
  35. The value for the '{4}' registry entry on server {2} has changed. Default value: {9} minutes. Current value: {8} seconds. ...
  36. The value for the '{4}' registry entry on server {2} has changed. This value should only be changed on the advice of Microsoft ...
  37. The value for the Exchange Installable File System (IFS) '{4}' registry entry on server {2} has changed. Current value: {9}. ...
  38. The value for the Extensible Storage Engine (ESE) transaction log file size for database '{3}' on server {2} changed. This ...
  39. The value for the Extensible Storage Engine (ESE) transaction log file size for storage group '{3}' on server {2} has changed. ...
  40. The value for the Extensible Storage Engine (ESE) transaction log file size for storage group '{3}' on server {2} has changed. ...
  41. The value for the Extensible Storage Engine (ESE) transaction log file size has changed on server {2}. This configuration ...
  42. The value for the IMAP4 '{4}' registry entry is set higher than {8} bytes on server {2}. Communication errors may occur. ...
  43. The value for the IMAP4 '{4}' registry entry is set lower than {8} bytes on server {2}. Communication errors may occur. Current ...
  44. The value for the IMAP4 '{4}' registry entry on server {2} has changed. In some scenarios, this can increase performance. ...
  45. The value for the maximum Extensible Storage Engine (ESE) cache on server {2} has changed. Current maximum cache size is ...
  46. The value for the maximum number of databases per storage group on server {2} has changed. This configuration is not supported. ...
  47. The value for the maximum number of storage groups on server {2} has changed. This configuration is not supported. This server ...
  48. The value for the Microsoft Exchange Information Store '{4}' registry entry on server {2} has changed. Current value: {9}. ...
  49. The value for the Microsoft Exchange Information Store '{4}' registry entry on server {2} is less than {8}. This configuration ...
  50. The value for the Microsoft Exchange Information Store RPC '{4}' registry entry on server {2} is not set to {8}. This will ...
  51. The value for the Microsoft Exchange Site Replication Service '{4}' registry entry on server {2} has changed. Port value: ...
  52. The value for the Microsoft Exchange Site Replication Service '{4}' registry entry on server {2} is less than {8}. This configuration ...
  53. The value for the Microsoft Exchange System Attendant '{4}' registry entry on server {2} is less than {8}. This configuration ...
  54. The value for the minimum Extensible Storage Engine (ESE) cache on server {2} has changed. This configuration is not generally ...
  55. The value for the POP3 '{4}' registry entry is set higher than {8} bytes on server {2}. Communication errors may occur. Current ...
  56. The value for the POP3 '{4}' registry entry is set lower than {8} bytes on server {2}. Communication errors may occur. Current ...
  57. The value for the POP3 '{4}' registry entry on server {2} has changed. In some scenarios, this can increase performance. ...
  58. The value for the transaction log file size for database {3} on server {2} changed. This configuration isn't supported. Current ...
  59. The value of an SMTP supervision list entry must consist of tags separated by commas, followed by the SMTP address. It must ...
  60. The value of the CustomRecipientWriteScope parameter must be the same as the implicit write scope of the associated management ...
  61. The value of the EnableAsSharedConfiguration parameter can't be true for an organization that has a SharedConfiguration value. ...
  62. The value of the Windows Management Instrumentation (WMI) setting '{4}' on cluster node {2} differs from that on node {1} ...
  63. The value provided for the ResultSize parameter must be an integer from {0} to {1}. Check the value you provided, and try ...
  64. The value provided in the {0} parameter contains leading or trailing spaces. Remove the leading or trailing spaces, and try ...
  65. The value specified for the age at which old message tracking log files will be removed is not valid. The default value %1 ...
  66. The value specified for the age at which old message tracking log files will be removed is not valid. The default value %1 ...
  67. The value you entered isn't a valid regular expression. A regular expression can contain plain text and placeholders to represent ...
  68. The value you specified for the "{0}" parameter exceeds the maximum allowable length, {1}. Provide a shorter value and try ...
  69. The value you specify with the WritableRecipient parameter must be a valid User, UserMailbox, Contact, MailContact or SystemMailbox ...
  70. The value {0} contains a number format specifier that's not valid. It should be in the form " ]". In this form, the prefix ...
  71. The value, '{0}', specified with the ConfigWriteScope parameter isn't valid. The configuration write scope must match the ...
  72. The values for the UseIncludedMailboxDatabases and the UseExcludedMailboxDatabases parameters can't be set to $true at the ...
  73. The values of property {0} are different and should match. The local organization relationship {1} has value {2}, and the ...
  74. The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector ...
  75. The VerifyGlobalRoutingEntry parameter will be ignored, either because the dial plan doesn't support global call routing ...