Exchange Server 2010

  1. The SSL certificate for the {4} service on server {2} is self-signed. It does not provide any of the security guarantees ...
  2. The SSL certificate for the {4} service on server {2} will expire {9}. Users may be unable to connect with the server once ...
  3. The SSL certificate from the remote party at '{0}' doesn't match the intended host name '{1}'. Instead, the host names presented ...
  4. The SSL certificate was issued by {0} and isn't trusted by Windows. If this is an internal certification authority and isn't ...
  5. The start and end times for your work week use the {0} time zone instead of the {1} time zone. The {0} time zone is used ...
  6. The Start-EdgeSynchronization cmdlet can only be run against a Hub Transport server. Make sure you either run this command ...
  7. The starting restored logfile %4 is too high. It should start from logfile %5. For more information, click http://www.mi ...
  8. The starting restored logfile %4 is too high. It should start from logfile %5. For more information, click http://www.mi ...
  9. The STARTTLS certificate will expire soon: subject: %1, thumbprint: %2, hours remaining: %3. Run the New-ExchangeCertificate ...
  10. The STARTTLS certificate will expire soon: subject: %1, thumbprint: %2, hours remaining: %3. Run the New-ExchangeCertificate ...
  11. The state of the reconciler for this database. A value of one indicates it is currently reconciling, zero means it is not. ...
  12. The STM file for mailbox database '{3}' on server {2} is being written to an encrypted folder. Severe performance degradation ...
  13. The STM file for mailbox store '{3}' on server {2} is being written to a compressed folder. Severe performance degradation ...
  14. The STM file for mailbox store '{3}' on server {2} is being written to a non-NTFS partition. This configuration does not ...
  15. The Stop-DatabaseAvailabilityGroup cmdlet failed to stop servers {0} in database availability group '{1}'. If the servers ...
  16. The store driver encountered a poison message during message submission. The submission will be stopped for event %1 on mailbox ...
  17. The store driver encountered a poison message during message submission. The submission will be stopped for event %1 on mailbox ...
  18. The store driver encountered a poison message during message submission. The submission will be stopped for event %1 on mailbox ...
  19. The store driver encountered a poison message during message submission. The submission will be stopped for event %1 on mailbox ...
  20. The store driver encountered a poison message during shadow message submission. The shadow submission will be stopped for ...
  21. The store driver encountered a poison message during shadow message submission. The shadow submission will be stopped for ...
  22. The store driver encountered a poison message during shadow message submission. The shadow submission will be stopped for ...
  23. The store driver encountered a poison message during shadow message submission. The shadow submission will be stopped for ...
  24. The store driver failed to deliver a message to %1: legacyExchangeDN attribute value of the mailbox Active Directory object ...
  25. The store driver failed to deliver a message to %1: legacyExchangeDN attribute value of the mailbox Active Directory object ...
  26. The store service on server {2} is not running. This can cause messages to queue when they are destined to databases with ...
  27. The streaming page read from the file "%1" at offset %2 for %3 bytes failed verification due to a page checksum mismatch. ...
  28. The streaming page read from the file "%1" at offset %2 for %3 bytes failed verification due to a page checksum mismatch. ...
  29. The streaming page read from the file "%4" at offset %5 for %6 bytes failed verification due to a page checksum mismatch. ...
  30. The streaming page read from the file "%4" at offset %5 for %6 bytes failed verification due to a page checksum mismatch. ...
  31. The string '{0}' isn't correctly formatted. It can contain a number with an optional unit specifier or the long ByteQuantifiedSize ...
  32. The subject alternative name (SAN) of SSL certificate for the {4} service on server {2} does not appear to match the host ...
  33. The subject alternative name (SAN) of SSL certificate for {1} does not appear to match the host address. Host address: {8}. ...
  34. The subscription failed because of a failure to save corrupted server object {0} to Active Directory with error {1}. You ...
  35. The sum of the '{0}' and '{1}' settings exceeds 80 percent of the CLR thread pool size on server {2}. This could degrade ...
  36. The supplied credential is used to connect automatically in a non-interactive way For Basic authentication, the credential ...
  37. The supplied credential is used to connect automatically in a non-interactive way For Basic authentication, the credential ...
  38. The SuppressXAnonymousTls parameter can't be set to $true on a Receive connector unless UseDowngradedExchangeServerAuth is ...
  39. The suspend operation can't proceed because database '{0}' on Exchange Mailbox server '{1}' is the active mailbox database ...
  40. The sync state loaded from the mailbox has a newer version than the Exchange ActiveSync application. More information: %1 ...
  41. The sync state loaded from the mailbox has a newer version than the Exchange ActiveSync application. More information: %1 ...
  42. The synchronization process has started, but the task is unable to read performance counters from the server. This may indicate ...
  43. The syntax for a protocol command was either invalid or it wasn't recognized. You can try sending the e-mail message again ...
  44. The syntax for a protocol command was either invalid or not recognized. The sender can try sending the e-mail message again ...
  45. The System Attendant isn't responding. It may be paused, or the version of the Administrator program may not match the version ...
  46. The system has detected a change in the available networks. The system is now using network '%1' instead of network '%2' ...
  47. The system has detected a change in the available networks. The system is now using network '%1' instead of network '%2' ...
  48. The system has serviced a %1 task but it took an abnormally long time (%2 seconds to be dispatched, %3 seconds to be executed). ...
  49. The system has serviced a %1 task but it took an abnormally long time (%2 seconds to be dispatched, %3 seconds to be executed). ...
  50. The system has serviced a %1 task but it took an abnormally long time (%2 seconds to be dispatched, %3 seconds to be executed). ...
  51. The system has serviced a %1 task but it took an abnormally long time (%2 seconds to be dispatched, %3 seconds to be executed). ...
  52. The system has serviced a %4 task but it took an abnormally long time (%5 seconds to be dispatched, %6 seconds to be executed). ...
  53. The system has serviced a %4 task but it took an abnormally long time (%5 seconds to be dispatched, %6 seconds to be executed). ...
  54. The system has serviced a %4 task but it took an abnormally long time (%5 seconds to be dispatched, %6 seconds to be executed). ...
  55. The system has serviced a %4 task but it took an abnormally long time (%5 seconds to be dispatched, %6 seconds to be executed). ...
  56. The system is experiencing memory allocation failures that are preventing proper operation of database '%1' ('%2'). This ...
  57. The system is experiencing memory allocation failures that are preventing proper operation of database '%1' ('%2'). This ...
  58. The system is experiencing memory allocation failures that are preventing proper operation of database '%4' ('%5'). The error ...
  59. The system is experiencing memory allocation failures that are preventing proper operation of database '%4' ('%5'). The error ...
  60. The tag type cannot be modified. Please create a new Retention Policy Tag with the desired tag type, or delete this tag and ...
  61. The target Client Access server version {1} is different from the version of the {0} cmdlet that was specified. The {0} cmdlet ...
  62. The target database '{0}' isn't an Exchange database. Neither MailEnableSourceAccount nor CreateSourceContact can be specified ...
  63. The target mailbox doesn't have an SMTP proxy matching '{0}'. The primary SMTP address '{1}' will be used as the external ...
  64. The target server cannot support OAB "{0}" since Version 4 is enabled. Either disable Version 4 generation or install KB ...
  65. The TargetApplicationUri of the remote organization doesn't match the local ApplicationUri of the Federation Trust object. ...
  66. The task and public folder database {0} connect to different domain controllers. Offline address book public folder distribution ...
  67. The task cannot locate the certificate to produce the subscription file. Check the local machine certificate store to ensure ...
  68. The task cannot locate the local server's configuration object. Check Active Directory to ensure the server object for {0} ...
  69. The task couldn't find the user {0}\{1} in Active Directory. This task needs to be able to look up the user to obtain the ...
  70. The task couldn't find the user {0}\{1} in Active Directory. This task needs to be able to look up the user to obtain the ...
  71. The task couldn't sign in with user {0}. Run {2} to verify that the user exists on the Mailbox server {1} To run this task ...
  72. The task couldn't sign in with user {0}. Run {2} to verify that the user exists on the Mailbox server {1} To run this task ...
  73. The task failed to correctly generate RUS information Proxies, Addresslists, Policies included for this object, error '%1'. ...
  74. The task failed to correctly generate RUS information Proxies, Addresslists, Policies included for this object, error '%1'. ...
  75. The task is attempting to communicate with the Microsoft Exchange Replication service on server "{0}" to obtain updated configuration ...