Exchange Server 2010

  1. The Parameters parameter is required. If you want to remove all the existing parameters for the specified management role ...
  2. The parameters passed to the cmdlet represent a federated account, which doesn't match the namespace state, which is managed. ...
  3. The parameters passed to the cmdlet represent a federated account, which doesn't match the tenant's service plan to support ...
  4. The parameters passed to the cmdlet represent a managed account, which doesn't match the namespace state, which is federated. ...
  5. The parameters passed to the cmdlet represent a managed account, which doesn't match the tenant's service plan to support ...
  6. The parameters specified are either missing additional required parameters or are not valid together. To list the available ...
  7. The parameters specified are either missing additional required parameters or are not valid together. To list the available ...
  8. The parent Legacy Exchange DN container value '%1' was not found during generation of the differential update file for offline ...
  9. The parent Legacy Exchange DN container value '%1' was not found during generation of the differential update file for offline ...
  10. The partner fax server URI must be in the following formats: sip:FQDN:port;transport=TCP | UDP or sips:FQDN:port;transport=TLS. ...
  11. The password for Windows LiveID is invalid. Try again using a password which has the same length as the original password. ...
  12. The password for Windows LiveID is invalid. Try again using a password which has the same length as the original password. ...
  13. The patch page read from the file "%1" at offset %2 for %3 bytes failed verification due to a page checksum mismatch. The ...
  14. The patch page read from the file "%1" at offset %2 for %3 bytes failed verification due to a page checksum mismatch. The ...
  15. The patch page read from the file "%1" at offset %2 for %3 bytes failed verification due to a page number mismatch. The expected ...
  16. The patch page read from the file "%1" at offset %2 for %3 bytes failed verification due to a page number mismatch. The expected ...
  17. The patch page read from the file "%4" at offset %5 for %6 bytes failed verification due to a page checksum mismatch. The ...
  18. The patch page read from the file "%4" at offset %5 for %6 bytes failed verification due to a page checksum mismatch. The ...
  19. The patch page read from the file "%4" at offset %5 for %6 bytes failed verification due to a page number mismatch. The expected ...
  20. The patch page read from the file "%4" at offset %5 for %6 bytes failed verification due to a page number mismatch. The expected ...
  21. The path "{0}" doesn't exist on the remote server "{1}". The Microsoft Exchange File Distribution service will create it ...
  22. The path for the PowerShell virtual directory '{1}' has been changed to '{2}'. This can cause the Exchange Management Tools ...
  23. The path must reside on a local fixed disk. If operating on a cluster, it must reside on a disk shared by all physical nodes. ...
  24. The path of virtual directory '{3}' on server {2} doesn't match the 'folderPathName' or 'msExchDefaultDomain' attributes ...
  25. The path specified with the LanguagePack parameter appears to be invalid. The required file, 'ClientLanguagePack.msi', wasn't ...
  26. The path specified with the LanguagePack parameter appears to be invalid. The required file, 'ClientLanguagePack.msi', wasn't ...
  27. The path specified with the LanguagePack parameter appears to be invalid. The required file, 'ServerLanguagePack.msi', wasn't ...
  28. The path specified with the LanguagePack parameter appears to be invalid. The required file, 'ServerLanguagePack.msi', wasn't ...
  29. The path specified with the LanguagePack parameter appears to be invalid. The required files, 'ClientLanguagePack.msi' and ...
  30. The path specified with the LanguagePack parameter appears to be invalid. The required files, 'ClientLanguagePack.msi' and ...
  31. The path to the language pack bundle wasn't found or reachable. Setup can't continue. See the Setup log for for more details. ...
  32. The path to the protocol logging location for Receive connectors has not been set. No protocol log for Receive connectors ...
  33. The path to the protocol logging location for Receive connectors has not been set. No protocol log for Receive connectors ...
  34. The performance data log file has been divided into 20-minute increments. Please select the time range in which the performance ...
  35. The personal greeting is played to callers who request to leave a message when your extension is either busy or there is ...
  36. The personal greeting is played to callers who request to leave a message when your phone number is either busy or there ...
  37. The phone number for "{0}" is not in a standard international format. The following number is an example of the correct format: ...
  38. The phone number isn't in a standard international format. The following number is an example of the correct format: +1 (425) ...
  39. The phone number you entered isn't valid. A valid phone number includes only digits, hyphens, and parentheses. Please enter ...
  40. The phone number {0} hasn't been set as your notification phone number. If you want to receive text messages on {0}, please ...
  41. The Pickup directory doesn't have permissions to write the pickup location to registry (%1). Please make sure Network Service ...
  42. The Pickup directory doesn't have permissions to write the pickup location to registry (%1). Please make sure Network Service ...
  43. The Pickup directory doesn't have the necessary Read permissions and Delete Subfolders and Files permissions for Pickup directory ...
  44. The Pickup directory doesn't have the necessary Read permissions and Delete Subfolders and Files permissions for Pickup directory ...
  45. The pilot identifer "{0}" isn't a valid SIP address. The following is an example of a valid address: sip:[email protected]. ...
  46. The PIN you entered is not valid. Your PIN must contain only numbers, and must be at least {0} digits long. It cannot be ...
  47. The PIN you entered isn't valid. Your PIN must contain only numbers, and must be at least {0} digits long. It can't be the ...
  48. The Pointer (PTR) record {1} does not match any fully-qualified domain name of the SMTP instances on server {2}. This may ...
  49. The poison message component couldn't access the registry information. Locate the registry location and verify that the Network ...
  50. The Polling Interval specifies the frequency that this distribution point checks for updated OAB files. An interval of 0 ...
  51. The POP3 service failed to connect using SSL or TLS encryption. No valid certificate is configured to respond to SSL/TLS ...
  52. The POP3 service failed to connect using SSL or TLS encryption. No valid certificate is configured to respond to SSL/TLS ...
  53. The port number specified for {0} does not match the port number specified for UnEncryptedOrTLSBindings/SSLBindings. {1} ...
  54. The PowerShell virtual directory '{1}' has been configured to require SSL. This can cause the Exchange Management Tools to ...
  55. The previous archive '{1}' of user '{0}' can't be found in the database. The recovery of the archive failed. This can occur ...
  56. The previous archive '{1}' of user '{0}' can't be found in the database. The recovery of the archive failed. This can occur ...
  57. The previous archive '{1}' of user '{0}' is in use by the following user in Active Directory: "{2}". The recovery of archive ...
  58. The Primary Active Manager server name is not valid. If this condition persists, you may be able to correct the situation ...
  59. The primary DNS suffix for server {2} does not match the fully-qualified domain name (FQDN) of the Active Directory domain ...
  60. The primary header page of file %4 was damaged. The shadow header page was used instead. For more information, click htt ...
  61. The primary header page of file %4 was damaged. The shadow header page was used instead. For more information, click htt ...
  62. The primary SMTP address template on the recipient policy '{3}' should be the default accepted domain. Default: '{8}'. Current: ...
  63. The primary SMTP address, external e-mail address, or proxy address for the mailbox being searched isn't specified or is ...
  64. The primary SMTP address, the external e-mail address, or the proxy address for the recipient '{0}' either isn't set or is ...
  65. The primary WINS server address for network interface '{1}' on server {2} is blank. Exchange relies on short server name ...
  66. The process using the most processor time is '{1}', which is consuming {2}% of the CPU time. The ID of this process is {3}. ...
  67. The process using the second-most processor time is '{1}', which is consuming {2}% of the CPU time. The ID of this process ...
  68. The process using the third-most processor time is '{1}', which is consuming {2}% of the CPU time. The ID of this process ...
  69. The process with process ID %1 is holding the performance counter %2 from instance %3 and category %4 while running processes ...
  70. The process with process ID %1 is holding the performance counter %2 from instance %3 and category %4 while running processes ...
  71. The product key has been validated and the product ID has been successfully created. This change won't take effect until ...
  72. The program collects information about computer hardware and how you use Exchange, without interrupting you. This helps Microsoft ...
  73. The progress of the task can't be displayed because the task has failed to read the server's performance counters {0} times. ...
  74. The Properties parameter should only be specified when you specify ReadProperty, WriteProperty, or Self with the AccessRights ...
  75. The property "{0}" couldn't be resolved as a well-known property name, Active Directory schema or LDAP attribute name, or ...