Exchange Server 2010

  1. The default scope restriction for the "{0}" role assignment can't be calculated because the current user has delegating role ...
  2. The default sharing policy can't be removed. First choose another policy to be the default sharing policy, and then remove ...
  3. The DefaultAuthenticationMethod parameter can't be specified with the ClientAuthentication parameter or the IISAuthenticationMethods ...
  4. The delivery receipt for the test message from {0} to {1} wasn't received within the error latency timeout of {2:#,#} seconds. ...
  5. The delivery receipt for the test message from {0} to {1} wasn't received within the execution timeout of {2:#,#} seconds. ...
  6. The Depth parameter will filter for entries of the specified Depth. This can be used to only get the high level entries to ...
  7. The designated journaling recipient for database '{3}' on server {2} is a disabled account ({1}). This can cause messages ...
  8. The designated journaling recipient for database '{3}' on server {2} is located on the local server. As a best practice, ...
  9. The designated journaling recipient for database '{3}' on server {2} isn't hidden from the address lists. To avoid having ...
  10. The designated journaling recipient for database '{3}' on server {2} points to a deleted object ({1}). This can cause messages ...
  11. The designated journaling recipient for database '{3}' on server {2} points to a deleted object ({1}). This can cause messages ...
  12. The designated journaling recipient for database '{3}' on server {2} points to a disabled account ({1}). This can cause messages ...
  13. The designated journaling recipient for database '{3}' on server {2} points to an object that does not have a valid '{4}' ...
  14. The designated journaling recipient for database '{3}' on server {2} points to an object that does not have a valid mailNickname. ...
  15. The desired checkpoint depth for database '%1' was modified from %2 bytes to %3 bytes to ensure that it is greater than the ...
  16. The desired checkpoint depth for database '%1' was modified from %2 bytes to %3 bytes to ensure that it is greater than the ...
  17. The destination Active Directory forest isn't up to date, which prevents the move from proceeding. Verify that Active Directory ...
  18. The destination server for this recipient could not be found in the Domain Name System (DNS). Please verify the e-mail address ...
  19. The destination server for this recipient could not be found in the Domain Name System (DNS). Please verify the e-mail address ...
  20. The destination system is currently not accepting any messages. Please retry at a later time. If that fails, contact your ...
  21. The destination system is currently not accepting any messages. Please retry at a later time. If that fails, contact your ...
  22. The DHCP Client service is not running on server {2}. This may cause dynamic DNS update failures, even when static IP addresses ...
  23. The dial plan '{0}' contains servers that are incompatible with this task. The incompatible servers won't be queried for ...
  24. The differential update file for address list '%1' cannot be generated due to invalid SMTP domain names or invalid Legacy ...
  25. The differential update file for address list '%1' cannot be generated due to invalid SMTP domain names or invalid Legacy ...
  26. The digital ID used to sign this message has been revoked. This can indicate that the issuer of the digital ID no longer ...
  27. The digital signature of this message couldn't be validated because an error occurred while the message was being loaded. ...
  28. The digital signature on this message can't be verified. The sender didn't include the digital ID used to sign the message. ...
  29. The digital signature on this message isn't valid. The message contents may have been altered after the message was signed. ...
  30. The direct trust certificate of the subscribed Edge Transport server with thumbprint {0} is a duplicate of the certificate ...
  31. The directory database has reported an error. Use the Services icon in the Control Panel to stop and then start the Microsoft ...
  32. The directory location to store the routing table log files for server {0} isn't configured. Specify a directory location ...
  33. The Directory name value is too long. A Distinguished Name DN could not be generated for this object. Please enter a different ...
  34. The Directory name value is too long. A Distinguished Name DN could not be generated for this object. Please enter a different ...
  35. The directory object for this computer has the serverRole attribute set to 1 (indicating a Front End server). This will be ...
  36. The directory object for this computer has the serverRole attribute set to 1 (indicating a Front End server). This will be ...
  37. The directory replica you are trying to delete is the source of a subsequent replica and cannot be deleted. On the DSA General ...
  38. The Directory Service Access (DSAccess) configuration cache on server {2} is full. Consider using the '{4}' registry entry ...
  39. The Directory Service Access (DSAccess) process on server {2} is hard-coded to use Active Directory server {1}. This configuration ...
  40. The Directory Service Access (DSAccess) process on server {2} reports that Active Directory server {1} is not functional. ...
  41. The Directory Service Access (DSAccess) process on server {2} reports that Active Directory server {1} is not synchronized ...
  42. The Directory Service Access (DSAccess) process on server {2} reports that Active Directory server {1} is taking longer than ...
  43. The Directory Service Access (DSAccess) process on server {2} reports that it is not using port 3268 for LDAP global catalog ...
  44. The Directory Service Access (DSAccess) process on server {2} reports that it is not using port 389 for LDAP domain controller ...
  45. The Directory Service Access (DSAccess) user cache on server {2} is full. Consider using the '{4}' registry entry to increase ...
  46. The directory service is not the expected type (Windows Active Directory vs. Exchange Directory). Make sure that Windows ...
  47. The directory service is unable to create the universal security group {0} in the domain {1}. Please verify that the domain ...
  48. The DirSync cookie for this domain has expired. Domain: %1 Last updated: %2 Time since last update: %3 Maximum allowed: %4 ...
  49. The DirSync cookie for this domain has expired. Domain: %1 Last updated: %2 Time since last update: %3 Maximum allowed: %4 ...
  50. The discovery mailbox, a hidden default mailbox that is required to search mailboxes, can't be found. It may have been inadvertently ...
  51. The Discovery Management role group wasn't found. The service plan for your organization doesn't support discovery management. ...
  52. The disk containing the log files is full. Deleting log files to recover disk space may make your database unstartable if ...
  53. The disk containing the log files is full. Deleting log files to recover disk space may make your database unstartable if ...
  54. The disk or volume mount point where the target database will be seeded is either dismounted or not responding to I/O requests. ...
  55. The Display Name of the recipient should be {0}. Run the Set-OrganizationConfig command without any parameters to correct ...
  56. The distinguished name already exists. Try the operation again. If the error recurs, try stopping the directory service and ...
  57. The Distributed Transaction Coordinator resource is not present or running on any node in this cluster. You must have the ...
  58. The distribution group "{0}" is configured to require approval for membership, but no arbitration mailbox is specified. You ...
  59. The distribution point for template "{0}" is "{1}". It doesn't match the URIs passed to the Import-RMSTrustedPublishingDomain ...
  60. The distribution points for the tenant licenses acquired for {0} do not match the configured service location {1} or publish ...
  61. The DNS search order for network interface '{1}' on server {2} is blank. Exchange relies on domain name system lookups to ...
  62. The document cannot be converted by the WebReady Document Viewing service because it is larger than the maximum size limit ...
  63. The document grew beyond a specified limit during format conversion. The output is at least {0} times larger than the input. ...
  64. The document or folder that you attempted to access is not stored on a Microsoft Windows SharePoint Services server or a ...
  65. The document you tried to open is protected with Information Rights Management and can only be opened using a desktop computer ...
  66. The document you tried to open is protected with Information Rights Management but it can't be viewed because it's corrupted. ...
  67. The document you tried to open is protected with Information Rights Management. Pre-licensing failed. Try opening the message ...
  68. The document you tried to open is protected with Information Rights Management. The Rights Management server isn't available ...
  69. The document you tried to open is protected with Information Rights Management. The RMS server isn't set up correctly. To ...
  70. The document you tried to open is protected with Information Rights Management. The sender didn't give you the rights necessary ...
  71. The document you're trying to view can't be converted because it doesn't have the right kind of file extension or content. ...
  72. The domain "%s" has been identified as an insecure domain for mail-enabled groups with hidden distribution list membership. ...
  73. The domain "{0}" isn't an Accepted Domain, therefore, it can't be federated. Check to make sure you typed the domain name ...
  74. The domain controller the script should run against. The default is to run against a well-connected domain controller in ...
  75. The domain name part of the sender's SMTP e-mail address is invalid. The domain part, which is the part of the e-mail address ...