Exchange Server 2010

  1. A proxy generator DLL on server {0} could not be found or failed to initialize. Proxy addresses for the current recipient ...
  2. A public folder store is present on Exchange front-end server {2}. This can cause data accessibility and system reliability ...
  3. A public group is a collection of two or more people in an organization's shared address book. You can create groups, which ...
  4. A read operation on file "%1" at offset %2 for %3 bytes failed %4 times over an interval of %5 seconds before finally succeeding. ...
  5. A read operation on file "%1" at offset %2 for %3 bytes failed %4 times over an interval of %5 seconds before finally succeeding. ...
  6. A read operation on the file "%4" at offset %5 for %6 bytes failed %7 times over an interval of %8 seconds before finally ...
  7. A read operation on the file "%4" at offset %5 for %6 bytes failed %7 times over an interval of %8 seconds before finally ...
  8. A read verification or I/O error is preventing proper operation of database '%1' ('%2'). Review the Event logs and other ...
  9. A read verification or I/O error is preventing proper operation of database '%1' ('%2'). Review the Event logs and other ...
  10. A read verification or I/O error is preventing proper operation of database '%4' ('%5'). Review the event logs and other ...
  11. A read verification or I/O error is preventing proper operation of database '%4' ('%5'). Review the event logs and other ...
  12. A Receive connector "{0}" wasn't found. You must specify one of the configured receive connectors. Make sure you typed the ...
  13. A receive connector can only be created on an Edge Transport or a Hub Transport server. Specify an Edge Transport or a Hub ...
  14. A recent change in the Microsoft Anti-spam Update service mode has been detected. The Content Filter agent is being reinitialized. ...
  15. A recent change in the Microsoft Anti-spam Update service mode has been detected. The Content Filter agent is being reinitialized. ...
  16. A recommended value for the '{4}' registry entry on server '{2}' should be between 1 and {3}. As a best practice, create ...
  17. A recovery storage group exists on server {2}. This should only exist during data recovery. Once recovery is complete, the ...
  18. A redirect response was received, but only HTTPS redirect URLs are supported in response to a POST request. The URL that ...
  19. A reminder can't be set for a single occurrence of a series of meetings when no reminder is set for the series. To set a ...
  20. A remote (TCP/IP) based streaming backup was attempted. This functionality has been disabled by default settings. Client: ...
  21. A remote (TCP/IP) based streaming backup was attempted. This functionality has been disabled by default settings. Client: ...
  22. A replica of public folder %1 was added. Expiration interval: %2 Database "%8". Folder-wide expiration interval: %3 Schedule: ...
  23. A replica of public folder %1 was added. Expiration interval: %2 Database "%8". Folder-wide expiration interval: %3 Schedule: ...
  24. A replica of public folder %1 was modified. Expiration interval: %2 (%3) Database "%14". Folder-wide expiration interval: ...
  25. A replica of public folder %1 was modified. Expiration interval: %2 (%3) Database "%14". Folder-wide expiration interval: ...
  26. A replica of the offline address book (OAB) '{3}' (folder: {1}) was not found on server {2}. This may result in OAB generation ...
  27. A request to import users is already in progress. To submit a new request, wait until the current one is done, or cancel ...
  28. A request to read from file "%1" at offset %2 for %3 bytes succeeded, but it took an unusually long time (%4 seconds) to ...
  29. A request to read from file "%1" at offset %2 for %3 bytes succeeded, but it took an unusually long time (%4 seconds) to ...
  30. A request to read from the file "%1" at offset %2 for %3 bytes succeeded, but took an abnormally long time (%4 seconds) to ...
  31. A request to read from the file "%1" at offset %2 for %3 bytes succeeded, but took an abnormally long time (%4 seconds) to ...
  32. A request to read from the file "%4" at offset %5 for %6 bytes succeeded, but took an abnormally long time (%7 seconds) to ...
  33. A request to read from the file "%4" at offset %5 for %6 bytes succeeded, but took an abnormally long time (%7 seconds) to ...
  34. A request to read from the file "%4" at offset %5 for %6 bytes succeeded, but took an abnormally long time (%7 seconds) to ...
  35. A request to read from the file "%4" at offset %5 for %6 bytes succeeded, but took an abnormally long time (%7 seconds) to ...
  36. A request to read to the file "%4" at offset %5 for %6 bytes has not completed for %7 second(s). This problem is likely due ...
  37. A request to read to the file "%4" at offset %5 for %6 bytes has not completed for %7 second(s). This problem is likely due ...
  38. A request to read to the file "%4" at offset %5 for %6 bytes has not completed for %7 second(s). This problem is likely due ...
  39. A request to read to the file "%4" at offset %5 for %6 bytes has not completed for %7 second(s). This problem is likely due ...
  40. A request to stop e-mail address generation has been received. This process will be stopped after address generation for ...
  41. A request to write to file "%1" at offset %2 for %3 bytes succeeded, but it took an unusually long time (%4 seconds) to be ...
  42. A request to write to file "%1" at offset %2 for %3 bytes succeeded, but it took an unusually long time (%4 seconds) to be ...
  43. A request to write to file "%1" at offset %2 for %3 bytes succeeded, but it took an unusually long time (%4 seconds) to be ...
  44. A request to write to file "%1" at offset %2 for %3 bytes succeeded, but it took an unusually long time (%4 seconds) to be ...
  45. A request to write to the file "%4" at offset %5 for %6 bytes has not completed for %7 second(s). This problem is likely ...
  46. A request to write to the file "%4" at offset %5 for %6 bytes has not completed for %7 second(s). This problem is likely ...
  47. A request to write to the file "%4" at offset %5 for %6 bytes has not completed for %7 second(s). This problem is likely ...
  48. A request to write to the file "%4" at offset %5 for %6 bytes has not completed for %7 second(s). This problem is likely ...
  49. A request to write to the file "%4" at offset %5 for %6 bytes succeeded, but took an abnormally long time (%7 seconds) to ...
  50. A request to write to the file "%4" at offset %5 for %6 bytes succeeded, but took an abnormally long time (%7 seconds) to ...
  51. A request to write to the file "%4" at offset %5 for %6 bytes succeeded, but took an abnormally long time (%7 seconds) to ...
  52. A request to write to the file "%4" at offset %5 for %6 bytes succeeded, but took an abnormally long time (%7 seconds) to ...
  53. A required column is missing from the CSV file. If you fre creating Windows Live IDs, the Password column is required. If ...
  54. A required column is missing from the CSV file. If you're creating Windows Live IDs, the Password column is required. If ...
  55. A required file cannot be installed because cabinet file 2 has an invalid digital signature. This may indicate that the cabinet ...
  56. A required file cannot be installed because cabinet file 2 is not digitally signed. This may indicate that the cabinet file ...
  57. A required security operation could not be performed during delivery of this e-mail message. Either the credentials are incorrect, ...
  58. A required security operation couldn't be performed during delivery of this e-mail message. Either the credentials are incorrect, ...
  59. A restore map already exists for the specified component. You can only specify a restore map when performing a full restore. ...
  60. A restore map already exists for the specified component. You can only specify a restore map when performing a full restore. ...
  61. A retention policy groups together a set of message retention settings, which are called retention tags, so that you can ...
  62. A rule synchronization error (%1) has occurred on mailbox database "%6". The mailbox folder is %2. The distinguished name ...
  63. A rule synchronization error (%1) has occurred on mailbox database "%6". The mailbox folder is %2. The distinguished name ...
  64. A rule synchronization error (%1) has occurred on Public Folder Store "%5". The public folder is %2. There are %3 of %4 retries ...
  65. A rule synchronization error (%1) has occurred on Public Folder Store "%5". The public folder is %2. There are %3 of %4 retries ...
  66. A secure connection couldn't be established to the Exchange server. Signatures won't be validated, and some message content ...
  67. A secure connection couldn't be established with the server. Encrypted messages won't be shown. For assistance, please contact ...
  68. A secure connection from domain-secured domain '%1' on connector '%2' failed to authenticate because validation of the Transport ...
  69. A secure connection from domain-secured domain '%1' on connector '%2' failed to authenticate because validation of the Transport ...
  70. A secure connection to domain secure domain '%1' on connector '%2' could not be established because TLS was not offered. ...
  71. A secure connection to domain secure domain '%1' on connector '%2' could not be established because TLS was not offered. ...
  72. A secure connection to domain-secured domain '%1' on connector '%2' could not be established because the DomainSecureEnabled ...
  73. A secure connection to domain-secured domain '%1' on connector '%2' could not be established because the DomainSecureEnabled ...
  74. A secure connection to domain-secured domain '%1' on connector '%2' could not be established because the validation of the ...
  75. A secure connection to domain-secured domain '%1' on connector '%2' could not be established because the validation of the ...