Exchange Server 2010

  1. The sign-in to Outlook Web App failed. User %1 has a mailbox on %2 server version. However, no Client Access server or front-end ...
  2. The sign-in to Outlook Web App failed. User %1 has a mailbox on %2 server version. However, no Client Access server or front-end ...
  3. The signature of log file %1 doesn't match other log files. Recovery won't succeed unless all signatures match. Log files ...
  4. The signature of log file %1 doesn't match other log files. Recovery won't succeed unless all signatures match. Log files ...
  5. The signature of logfile %4 does not match other logfiles. Recovery cannot succeed unless all signatures match. Logfiles ...
  6. The signature of logfile %4 does not match other logfiles. Recovery cannot succeed unless all signatures match. Logfiles ...
  7. The signing certificate with thumbprint "{0}" in the Windows Live metadata document is expired. Ignoring this certificate. ...
  8. The Simple Mail Transfer Protocol (SMTP) service is installed on this computer. This must be removed before Setup can continue. ...
  9. The SIP session border controller that's used by the Microsoft Exchange Unified Messaging service hasn't been specified. ...
  10. The site name '{0}' must have fewer than 41 characters when automatic send connector creation is selected. Please shorten ...
  11. The site {1}, which has an Exchange 2010 Mailbox server, also has at least one Exchange 2007 Client Access server with the ...
  12. The site-wide public folder database for administrative group '{1}' wasn't detected within this administrative group. The ...
  13. The site-wide public folder database for administrative group '{2}' has been deleted. Current public folder store: '{1}'. ...
  14. The size for the log directory specified in Microsoft.Exchange.Monitoring.CorrelationEngine.exe.config wasn't valid. Setting ...
  15. The size of the Application log on server {2} is larger than 64 MB. This may cause high usage of Page Table Entries (PTE). ...
  16. The size of the log files in '{4}' folder for storage group '{3}' on server {2} is bigger than 1GB. Over time the amount ...
  17. The size of the Security log on server {2} is larger than 64 MB. This may cause high usage of Page Table Entries (PTE). Maximum ...
  18. The sliding time window (in seconds) during which the 'Repeat Threshold' number of events must occur in order for the state ...
  19. The smarthost name '{3}' configured in Send Connector is not an IP address or fully qualified domain name (FQDN), and this ...
  20. The SMTP address template '{0}' is invalid because it references a domain that isn't configured as an accepted domain for ...
  21. The SMTP configuration parameter '{4}' is set to {9} on server {2}. This may cause problems with mail flow and should be ...
  22. The SMTP IgnorePFTimeLimit value on server {2} has been manually set and it is less than the default value of 2. Current ...
  23. The SMTP MaxDSNSize value on server {2} has been manually set (default: unlimited). This can improve processing time and ...
  24. The SMTP MsgHandleAsyncThreshold value on server {2} has been manually set. This parameter can cause service availability ...
  25. The SMTP queue folder for instance '{3}' on server {2} is identical to the pickup folder. This will cause duplicate message ...
  26. The SMTP queue folder for instance '{3}' on server {2} is located on the same drive as the system partition. This may cause ...
  27. The sort order format "{0}" is invalid. The format is: +/-]PropertyName, where '+' indicates ascending sort; '-' indicates ...
  28. The source copy {0}/{1} for Update-MailboxDatabaseCopy must have a status of Mounted or Healthy, but its current state is ...
  29. The source copy {0}/{1} has a failed content index. You may use the -DatabaseOnly parameter to update the database without ...
  30. The source forest cleanup has been cancelled because the policies couldn't be applied to the target mailbox. SourceForestCleanupOptions: ...
  31. The source forest policy name '{0}' is set on more than one policy. The source forest policy name must be unique for all ...
  32. The source installation package for the product 2 is out of sync with the client package. Try the installation again using ...
  33. The source mailbox '{0}' will not be searched because it is the target mailbox. The source mailbox cannot be used as the ...
  34. The source mailbox appears to have an archive mailbox but resides on a database with a version of Exchange that doesn't support ...
  35. The source mailbox has a managed folder mailbox policy that only works with Exchange 2007 or later. To explicitly remove ...
  36. The source mailbox has a Unified Messaging mailbox policy that can only be applied to mailboxes on computers running Exchange ...
  37. The source server '{0}' isn't a Hub Transport server. You can't use the Edge Transport server role as a source server for ...
  38. The source servers contain both Hub Transport servers and Edge Transport servers. Source servers either should be all Hub ...
  39. The source {0} is mail-enabled in the source forest. Identity: '{1}'. Alias: '{2}'. ExternalEmailAddress: '{3}'. LegacyExchangeDN: ...
  40. The SourceIPAddress that you typed isn't valid. Specify a local IP address of the source server for this Send connector, ...
  41. The specified .edb file path ('{0}') is already in use by another database on the server. Please specify a different .edb ...
  42. The specified access rights "{0}" are invalid. Valid access rights include AllStoreRights, AllExtendedRights, or the combination ...
  43. The specified address space '{0}' isn't an SMTP address space. Non-SMTP address spaces aren't allowed on Edge Transport servers. ...
  44. The specified Application URI for the domain is already assigned to a different Application ID in Windows Live. Detailed ...
  45. The specified correlation interval value '{0}' is less than the minimum allowed value. The default value '{1}' will be used ...
  46. The specified correlation time window value '{0}' is less than the minimum allowed value. The default value '{1}' will be ...
  47. The specified database file path cannot be found on the specified server. Specified EdbFilePath: {0}. Specified server: {1}. ...
  48. The specified database has been removed. You must remove the database file located in {1} from your computer manually if ...
  49. The specified DTMF fallback auto attendant "{0}" is not valid. It should be associated with the same dial plan as the current ...
  50. The specified DTMF fallback auto attendant "{0}" isn't valid. A DTMF fallback auto attendant shouldn't be speech-enabled. ...
  51. The specified e-mail address policy couldn't be edited. E-mail address policies created with legacy versions of Exchange ...
  52. The specified Edge Transport server '{0}' is subscribed to an Active Directory site. Exchange doesn't support running this ...
  53. The specified enhanced status code is invalid. Valid values are 5.7.1, or a value in the range between 5.7.10 and 5.7.999. ...
  54. The specified Exchange server ({2}) for processing Recipient Update Service '{3}' is running Exchange Server 2007. The service ...
  55. The specified file name is not a valid database file path. You cannot use a UNC path as part of the database file name. Specified ...
  56. The specified folder can't be displayed. This may be because the folder type isn't one that's supported for Web Part URL ...
  57. The specified installation directory must be located on a fixed drive, but {0} is located on a CD-ROM drive, RAM disk, network ...
  58. The specified installation directory must be located on an NTFS drive, but {0} is located on a drive that is not formatted ...
  59. The specified log file path ('{0}') is in use by another database on server "{1}". Please specify a different log folder ...
  60. The specified log folder path ('{0}') is already in use by another database on the server. Please specify a different log ...
  61. The specified merged free/busy interval is not valid. Specify an interval that is less than the free/busy time window and ...
  62. The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and ...
  63. The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters. Directory ...
  64. The specified priority "{0}" isn't valid. The priority should be equivalent to or immediately higher or lower than the priority ...
  65. The specified public folder store couldn't be removed from the replica lists of its public folders because no other public ...
  66. The specified public folder user "{0}" is not unique. A valid public folder user should be a mail-enabled user, mailbox or ...
  67. The specified recipient '{1}' was found to be global distribution group '{3}', while the topology appears to be a multi-domain ...
  68. The specified rule-based monitor time window value '{0}' is less than the minimum allowed value. The default value '{1}' ...
  69. The specified server "{0}" isn't an Exchange 2010 server. This task is only supported on servers running Exchange 2010 or ...
  70. The specified user or group "{0}" is a local user or group and isn't supported on a computer that doesn't have AD LDS installed. ...
  71. The specified Web Part URL contains an invalid value for the {0} parameter. The value may be invalid only for the folder ...
  72. The specified working directory for the store on server {2} does not appear to exist. This may cause messages with attachments ...
  73. The speech recognition phrases associated with menu option {0} have exceeded the maximum allowed length of 256 characters. ...
  74. The SSL certificate for '{1}' is self-signed. It does not provide any of the security guarantees provided by authority-signed ...
  75. The SSL certificate for '{1}' will expire {9}. Users may be unable to connect with the server once the certificate expires. ...