Exchange Server 2016

  1. The specified classification rule collection has some invalid content(s) which cannot be consumed successfully by the classification ...
  2. The specified classification rule collection resolved to an existing custom rule collection. The out-of-box argument specification ...
  3. The specified data classification identity '{0}' has resolved to a data classification in classification rule collection ...
  4. The specified database file path cannot be found on the specified server. Specified EdbFilePath: {0}. Specified server: {1}. ...
  5. The specified database has been removed. You must remove the database file located in {1} from your computer manually if ...
  6. The specified DTMF fallback auto attendant "{0}" is not valid. It should be associated with the same dial plan as the current ...
  7. The specified DTMF fallback auto attendant "{0}" isn't valid. A DTMF fallback auto attendant shouldn't be speech-enabled. ...
  8. The specified e-mail address policy couldn't be edited. E-mail address policies created with legacy versions of Exchange ...
  9. The specified Edge Transport server '{0}' is subscribed to an Active Directory site. Exchange doesn't support running this ...
  10. The specified enhanced status code '{0}' is invalid or isn't compatible with Transport Rules policy requirement. Valid values ...
  11. The specified Enum type has a type name and value(s) that are identical with that of an already registered type but with ...
  12. The specified Exchange server ({2}) for processing Recipient Update Service '{3}' is running Exchange Server 2007. The service ...
  13. 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 ...
  14. The specified groups will be expanded so that an In-Place Hold can be put on the mailboxes in these groups. Only the mailboxes ...
  15. The specified Identity does not represent a device conditional access rule, but this cmdlet can only manipulate device conditional ...
  16. The specified Identity does not represent a device configuration rule, but this cmdlet can only manipulate device configuration ...
  17. The specified Identity does not represent an audit configuration policy, but this cmdlet can only manipulate audit configuration ...
  18. The specified Identity does not represent an audit configuration rule, but this cmdlet can only manipulate audit configuration ...
  19. The specified Identity represents a device configuration rule, but this cmdlet cannot manipulate device configuration rule. ...
  20. The specified Identity represents an audit configuration policy, but this cmdlet cannot manipulate audit configuration policy. ...
  21. The specified Identity represents an audit configuration rule, but this cmdlet cannot manipulate audit configuration rule. ...
  22. The specified installation directory must be located on a fixed drive, but {0} is located on a CD-ROM drive, RAM disk, network ...
  23. The specified installation directory must be located on an NTFS drive, but {0} is located on a drive that is not formatted ...
  24. The specified log file path ('{0}') is in use by another database on server "{1}". Please specify a different log folder ...
  25. The specified log folder path ('{0}') is already in use by another database on the server. Please specify a different log ...
  26. The specified MailboxContainerGuid '{0}' does not match the MailboxContainerGuid of the Unified Mailbox it is being linked ...
  27. The specified merged free/busy interval is not valid. Specify an interval that is less than the free/busy time window and ...
  28. The specified out-of-box classification rule collection update cannot be applied because it is missing data classification(s) ...
  29. The specified parameters are invalid. To view Help, run the following command: Get-Help Update-MalwareFilteringServer.ps1. ...
  30. The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and ...
  31. The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters. Directory ...
  32. The specified priority "{0}" isn't valid. The priority should be equivalent to or immediately higher or lower than the priority ...
  33. The specified public folder store couldn't be removed from the replica lists of its public folders because no other public ...
  34. The specified public folder user "{0}" is not unique. A valid public folder user should be a mail-enabled user, mailbox or ...
  35. The specified recipient '{1}' was found to be global distribution group '{3}', while the topology appears to be a multi-domain ...
  36. The specified server {0} isn't an Exchange 2010 server. This task is only supported on servers running Exchange 2010 or later ...
  37. 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. ...
  38. The specified working directory for the store on server {2} does not appear to exist. This may cause messages with attachments ...
  39. The speech recognition phrases associated with menu option {0} have exceeded the maximum allowed length of 256 characters. ...
  40. The SSL certificate for '{1}' is self-signed. It does not provide any of the security guarantees provided by authority-signed ...
  41. The SSL certificate for '{1}' will expire {9}. Users may be unable to connect with the server once the certificate expires. ...
  42. The SSL certificate for the {4} service on server {2} is self-signed. It does not provide any of the security guarantees ...
  43. The SSL certificate for the {4} service on server {2} will expire {9}. Users may be unable to connect with the server once ...
  44. The SSL certificate from the remote party at '{0}' doesn't match the intended host name '{1}'. Instead, the host names presented ...
  45. The Start-EdgeSynchronization cmdlet can only be run against a Mailbox server. Make sure you either run this command on a ...
  46. The starting restored logfile %4 is too high. It should start from logfile %5. For more information, click http://www.mi ...
  47. The STARTTLS certificate will expire soon: subject: %1, thumbprint: %2, hours remaining: %3. Run the New-ExchangeCertificate ...
  48. The status of Exchange Certificate '{1}' for services '{2}' on server '{0}' is expired or couldn't be determined: status ...
  49. The status of Exchange Certificate '{1}' for services '{2}' on server '{0}' is valid or couldn't be determined: status - ...
  50. The STM file for mailbox database '{3}' on server {2} is being written to an encrypted folder. Severe performance degradation ...
  51. The STM file for mailbox store '{3}' on server {2} is being written to a compressed folder. Severe performance degradation ...
  52. The STM file for mailbox store '{3}' on server {2} is being written to a non-NTFS partition. This configuration does not ...
  53. The Stop-DatabaseAvailabilityGroup cmdlet failed to stop servers {0} in database availability group '{1}'. If the servers ...
  54. The storage driver file for '{0}' on server is more than two years old. Check with your vendor to see if a newer version ...
  55. The store driver Submission encountered a poison message during message submission. The submission will be stopped for event ...
  56. The store driver Submission encountered a potential poison message during message submission. The submission will be stopped ...
  57. The store service on server {2} is not running. This can cause messages to queue when they are destined to databases with ...
  58. The streaming page read from the file "%1" at offset %2 for %3 bytes failed verification due to a page checksum mismatch. ...
  59. The streaming page read from the file "%4" at offset %5 for %6 bytes failed verification due to a page checksum mismatch. ...
  60. The string '{0}' isn't correctly formatted. It can contain a number with an optional unit specifier or the long ByteQuantifiedSize ...
  61. The string you provided for the disclaimer is larger than the allowed maximum of {0} characters. Please provide a string ...
  62. The string you provided for the email is larger than the allowed maximum of {0} characters. Please provide a string that ...
  63. The string you provided for the web portal text is larger than the allowed maximum of {0} characters. Please provide a string ...
  64. The subject alternative name (SAN) of SSL certificate for the {4} service on server {2} does not appear to match the host ...
  65. The subject alternative name (SAN) of SSL certificate for {1} does not appear to match the host address. Host address: {8}. ...
  66. The subnets configured for the database availability group are not properly assigned to networks. Use the Get-DatabaseAvailabilityGroupNetwork ...
  67. The subscription failed because of a failure to save corrupted server object {0} to Active Directory with error {1}. You ...
  68. The suggested setting is PowerShellMaxCmdlets >= ExchangeMaxCmdlets 1.2. Currently PowerShellMaxCmdlets = {0}, ExchangeMaxCmdlets ...
  69. The sum of the '{0}' and '{1}' settings exceeds 80 percent of the CLR thread pool size on server {2}. This could degrade ...
  70. The supplied credential is used to connect automatically in a non-interactive way For Basic authentication, the credential ...
  71. The SuppressXAnonymousTls parameter can't be set to $true on a Receive connector unless UseDowngradedExchangeServerAuth is ...
  72. The suspend operation can't proceed because database '{0}' on Exchange Mailbox server '{1}' is the active mailbox database ...
  73. The sync state loaded from the mailbox has a newer version than the Exchange ActiveSync application. More information: %1 ...
  74. The synchronization process has started, but the task is unable to read performance counters from the server. This may indicate ...
  75. The syntax for a protocol command was either invalid or it wasn't recognized. You can try sending the e-mail message again ...