Exchange Server 2010

  1. The following custom prompt files were not found for UM dial plan "%1": "%2". If new custom prompt files have been published ...
  2. The following error occurred while processing %1. %2. The meeting request couldn't be processed. Correct the problem and ...
  3. The following error occurred while processing %1. %2. The meeting request couldn't be processed. Correct the problem and ...
  4. The following error occurred while reporting client data. The root cause may be that the server has not been upgraded to ...
  5. The following error occurred while reporting client data. The root cause may be that the server has not been upgraded to ...
  6. The following error was received while removing the Organization Management role group : {0}. You need to remove the group ...
  7. The following files weren't attached because each of them exceeds the maximum size limit for a single attachment ({1} MB): ...
  8. The following files weren't inserted because they aren't supported image file types: {0}. The supported image file types ...
  9. The following folder failed to be opened during move mailbox for %1. Folder: %2; Error code: %3. Run ISINTEG to check for ...
  10. The following folder failed to be opened during move mailbox for %1. Folder: %2; Error code: %3. Run ISINTEG to check for ...
  11. The following folders in mailbox '%1' have items that exceed the message size limit in the archive. The oversized items will ...
  12. The following folders in mailbox '%1' have items that exceed the message size limit in the archive. The oversized items will ...
  13. The following items couldn't be sent to your mobile phone. They haven't been deleted. You should be able to access them using ...
  14. The following list shows the retention policies and archive policies that are currently available to you. To use additional ...
  15. The following message failed to be opened during move mailbox for %1. Parent folder: %2; Message subject/ID: %3; Error code: ...
  16. The following message failed to be opened during move mailbox for %1. Parent folder: %2; Message subject/ID: %3; Error code: ...
  17. The following message is successfully opened during move mailbox for %1. Parent folder: %2; Message subject/ID: %3; Database: ...
  18. The following message is successfully opened during move mailbox for %1. Parent folder: %2; Message subject/ID: %3; Database: ...
  19. The following message tracking log file is corrupted: '%1'. The corrupted record won't be included in the search results. ...
  20. The following message tracking log file is corrupted: '%1'. The corrupted record won't be included in the search results. ...
  21. The following Microsoft Exchange 2003 back-end servers aren't enabled for Outlook Anywhere. If you want to enable them, use ...
  22. The following options control whether this tool will automatically check the Web for a newer version of the configuration ...
  23. The following parameters on the "{1}" management role entry of the "{0}" management role can't be removed because they don't ...
  24. The following parameters that you tried to add to the "{1}" management role entry on the "{0}" management role can't be added ...
  25. The following properties cannot change on a Provisioned server: StaticDomainControllers, StaticGlobalCatalogs, StaticConfigDomainController, ...
  26. The following recipients are outside your organization. The calendar sharing settings you selected aren't available to them. ...
  27. The following recipients are outside your organization. The calendar sharing settings you selected aren't available to them. ...
  28. The following retention policies already exist and are different than those in the file:{0} These policies will be updated ...
  29. The following retention tags already exist and are different than those in the file:{0} These tags will be updated with the ...
  30. The following servers have been added to the database availability group but not to the cluster: {0}. This is usually the ...
  31. The following servers in the Windows Failover Cluster are not in Active Directory: {0}. This is usually the result of an ...
  32. The forest functional level of the current Active Directory forest is not Windows Server 2003 native or later. To install ...
  33. The forest functional level of the current Active Directory forest isn't Windows Server 2008 native or later. To install ...
  34. The format "{0}" is incorrect. Use the format "Prefix Suffix", where Prefix and Suffix can contain text strings or any of ...
  35. The format of '{0}' is invalid. ConfiguredAttributes properties must be specified as "name, type", where "name" is the name ...
  36. The format of the e-mail address is incorrect. Check the address, look up the recipient in the Address Book, or contact the ...
  37. The format of the e-mail address is incorrect. Check the address, look up the recipient in the Address Book, or contact the ...
  38. The format of the e-mail address isn't correct. A correct address looks like this: [email protected]. Please check the ...
  39. The format of the recipient e-mail address is not valid. Valid SMTP e-mail addresses can contain only letters, numbers, hyphens, ...
  40. The format of the recipient e-mail address isn't valid. Valid SMTP e-mail addresses can contain only letters, numbers, hyphens, ...
  41. The format of the secondary address {0} isn't valid. The secondary address must be a valid extension or an E164 number (for ...
  42. The format of the SIP resource identifier that you specified isn't valid. Use the format in the following example: [email protected]. ...
  43. The format you provided, "{0}", is unknown. The correct format is "X509: CN=Issuer CN=Subject". Note that the issuer part ...
  44. The forms-based authentication public time-out value is currently {0} and the private time-out value is {1}. The public time-out ...
  45. The forms-based authentication setting of path {0} (metabase property id {1}) couldn't be modified. Are you sure you have ...
  46. The frequency at which each sample is taken. Typical values would be 30 seconds, one minute, or five minutes; under normal ...
  47. The fully qualified domain name (FQDN) of the local computer matches the SMTP address of recipient policy '{3}'. Setup cannot ...
  48. The fully qualified domain name (FQDN) value on the default receive connector named '{3}' on server {2} has been changed. ...
  49. The fully qualified name of this computer ("%s") matches the SMTP domain in the recipient policy "%s". You must rename this ...
  50. The fully-qualified domain name of SMTP virtual server '{3}' on server {2} does not match the DNS resolved server name. This ...
  51. The fully-qualified domain name of SMTP virtual server '{3}' on server {2} does not match the fully-qualified domain name ...
  52. The Function Call log (FCL) shows that the {0} process experienced long wait times in calls to the directory. Please check ...
  53. The Function Call log (FCL) shows {1} in progress calls to Virus Scanner, and there are only {2} threads available for virus ...
  54. The gateways in the list above also relay Internet mail to the cloud-based service without filtering messages for junk e-mail. ...
  55. The generation number ({1}) in the check point file is higher than the minimum required log file number ({2}) in the database ...
  56. The generation number ({1}) inside the check point file is greater than the minimum required transaction log file number ...
  57. The generation number ({1}) inside the check point file is greater than the minimum required transaction log file number ...
  58. The generation number inside the check point file ({1}) is greater than the minimum required transaction log file number ...
  59. The generation number inside the check point file ({1}) is greater than the minimum required transaction log file number ...
  60. The generation of the quarantine message may fail because of an error reading the spam quarantine mailbox configuration from ...
  61. The generation of the quarantine message may fail because of an error reading the spam quarantine mailbox configuration from ...
  62. The global '{3}' limit used by Exchange Server 2003 and Exchange 2000 Server conflicts with the corresponding organization ...
  63. The grammar file named "{0}" with rule "{1}" does not have a valid RecoEvent declaration. Make sure the first node after ...
  64. The group "{0}" can't be managed by recipient "{1}". The owner of the group should have the following recipient type details: ...
  65. The group "{0}" is not managed by any recipient but "{1}" is true. Please set "{1}" to false or choose a recipient to manage ...
  66. The group name contains the word "{0}", which isn't allowed in group names in your organization. Please rename your group. ...
  67. The header of the free/busy security descriptor obtained from mailbox {0} is not supported. The header length should be at ...
  68. The health test of the TCP listener for the Microsoft Exchange Replication service on server '{0}' failed. This server cannot ...
  69. The heartbeat connection for server {2} appears to have a DNS search order. Heartbeat connections should not have the DNS ...
  70. The heartbeat connection for server {2} appears to have the default gateway address set. Heartbeat connections should not ...
  71. The heartbeat connection for server {2} appears to have the primary WINS address set. Heartbeat connections should not have ...
  72. The heartbeat connection for server {2} is first in the TCP/IP binding order and not the public connection. This may cause ...
  73. The highlighted volumes do not have enough available disk space for the currently selected features. To fix this, you can ...
  74. The home server of the specified sender '{3}' (mail address: {4}) is {2} whereas the entered Exchange server was {1}. The ...
  75. The host is not responding. This code may be caused by transient network conditions. Exchange will automatically try again ...