Exchange Server 2016

  1. A public folder database is present on Exchange Client Access server {0}. This configuration may cause data accessibility ...
  2. A public folder move is assumed to be complete if the target mailbox GUID for the moving folders are updated at the public ...
  3. A public folder store is present on Exchange front-end server {2}. This can cause data accessibility and system reliability ...
  4. A Publishing License couldn't be created. This failure may prevent features such as Transport Protection Rules, IRM in Outlook ...
  5. A read operation on the file "%1" at offset %2 for %3 bytes failed %4 times over an interval of %5 seconds before finally ...
  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 verification or I/O error is preventing proper operation of database '%1' ('%2'). Review the event logs and other ...
  8. A read verification or I/O error is preventing proper operation of database '%4' ('%5'). Review the event logs and other ...
  9. A receive connector can only be created on an Edge Transport or a Hub Transport server. Specify an Edge Transport or a Hub ...
  10. A recent change in the Microsoft Anti-spam Update service mode has been detected. The Content Filter agent is being reinitialized. ...
  11. A recommended value for the '{4}' registry entry on server '{2}' should be between 1 and {3}. As a best practice, create ...
  12. A recovery storage group exists on server {0}. This storage group should only exist during data recovery. Once recovery is ...
  13. A recovery storage group exists on server {2}. This should only exist during data recovery. Once recovery is complete, the ...
  14. A regular expression specified for a transport rule must contain at least one non-blank character. A regular expression that ...
  15. A remote (TCP/IP) based streaming backup was attempted. This functionality has been disabledby default settings. Client: ...
  16. A replica of the offline address book (OAB) '{3}' (folder: {1}) was not found on server {2}. This may result in OAB generation ...
  17. A request for a node on an empty page (Pgno: %4) has been made (error %1) for a B-Tree (ObjectId: %2, PgnoRoot: %3) of database ...
  18. A request for a node on an empty page (Pgno: %7) has been made (error %4) for a B-Tree (ObjectId: %5, PgnoRoot: %6) of database ...
  19. A request to read from the file "%1" at offset %2 for %3 bytes has not completed for %4 second(s). This problem is likely ...
  20. A request to read from the file "%1" at offset %2 for %3 bytes succeeded, but took an abnormally long time (%4 seconds) to ...
  21. A request to read from the file "%1" at offset %2 for %3 bytes succeeded, but took an abnormally long time (%4 seconds) to ...
  22. A request to read from the file "%4" at offset %5 for %6 bytes has not completed for %7 second(s). This problem is likely ...
  23. A request to read from the file "%4" at offset %5 for %6 bytes succeeded, but took an abnormally long time (%7 seconds) to ...
  24. A request to read from the file "%4" at offset %5 for %6 bytes succeeded, but took an abnormally long time (%7 seconds) to ...
  25. A request to stop e-mail address generation has been received. This process will be stopped after address generation for ...
  26. A request to track latency was made on an item that is no longer capable of tracking latency. Component latency info will ...
  27. A request to write to the file "%1" at offset %2 for %3 bytes has not completed for %4 second(s). This problem is likely ...
  28. A request to write to the file "%1" at offset %2 for %3 bytes succeeded, but took an abnormally long time (%4 seconds) to ...
  29. A request to write to the file "%1" at offset %2 for %3 bytes succeeded, but took an abnormally long time (%4 seconds) to ...
  30. 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 ...
  31. A request to write to the file "%4" at offset %5 for %6 bytes succeeded, but took an abnormally long time (%7 seconds) to ...
  32. A request to write to the file "%4" at offset %5 for %6 bytes succeeded, but took an abnormally long time (%7 seconds) to ...
  33. A required security operation could not be performed during delivery of this e-mail message. Either the credentials are incorrect, ...
  34. A required security operation couldn't be performed during delivery of this e-mail message. Either the credentials are incorrect, ...
  35. A resource is overloaded due to your Throttling Policy budgget. The operation will be delayed until your budget allows it ...
  36. A restore map already exists for the specified component. You can only specifya restore map when performing a full restore. ...
  37. A retention policy groups together a set of message retention settings, which are called retention tags, so that you can ...
  38. A Scan Process restarted because it exceeds the limit of Scan Process Recovery Heuristic Policy: %1. The Percentage value ...
  39. A Scan Process restarted because it exceeds the limit of Scan Process Recovery Life Time threshold. The policy configuration ...
  40. A secure connection from domain-secured domain '%1' on connector '%2' failed to authenticate because validation of the Transport ...
  41. A secure connection to domain secure domain '%1' on connector '%2' could not be established because TLS was not offered. ...
  42. A secure connection to domain-secured domain '%1' on connector '%2' could not be established because the DomainSecureEnabled ...
  43. A secure connection to domain-secured domain '%1' on connector '%2' could not be established because the validation of the ...
  44. A secure connection to the domain %1 could not be established because the Transport Layer Security (TLS) certificate for ...
  45. A secure connection with Exchange server %1 could not be established because the protocol negotiation did not find a mutually ...
  46. A Secure Mail Certificate with matching subject '{0}' and issuer '{1}' cannot be found on transport server {2}. All transport ...
  47. A security error occurred while trying to deliver your e-mail message. Security policies prohibit further explanation of ...
  48. A Security Token Service cannot be found for organization {0}. The security token service list is {1}. Failure: {2} SubFailure: ...
  49. A seed had begun for database copy '%1' but got interrupted probably because of a crash in the Microsoft Exchange Replication ...
  50. A serious error is preventing proper operation of database '%1' ('%2'). Review the application and system event logs for ...
  51. A serious error is preventing proper operation of database '%4' ('%5'). Review the application and system event logs for ...
  52. A server object for this server ("%s") already exists in the Administrative Group "%s". If you are attempting to recover ...
  53. A server object for this server ("%s") must exist in the Active Directory in order to recover this server. If you are attempting ...
  54. A server-side database availability group administrative operation failed with a transient error. Please try the operation ...
  55. A server-side operation for user {0} failed with error 0x{1:X}. For more information, please see the event logs on the server ...
  56. A server-side operation for user {0} has failed. You may be able to try the operation again. For more information, see the ...
  57. A service principal name, containing - "name/authority" where name specifies an application class value and authority contains ...
  58. A Setup failure previously occurred while installing the {0} role. Either run Setup again for just this role, or remove the ...
  59. A shared configuration Organization for the specified ProgramId/OfferId: '{0}'/'{1}' already exists. Skipping creating new ...
  60. A significant portion of the database buffer cache has been written out to the system paging file. This may result in severe ...
  61. A significant portion of the database buffer cache has been written out to the system paging file. This may result in severe ...
  62. A single in-place hold object only support {0} source mailboxes. Please make sure the number of source mailboxes is less ...
  63. A single replica of folder '{1}' for offline address book '{2}' exists in the organization. To increase performance and resilience, ...
  64. A single replica of the free/busy folder for administrative group '{3}' exists in the organization, and more than 10,000 ...
  65. A single replica of the free/busy folder for administrative group '{3}' exists in the organization. In some situations, multiple ...
  66. A single-labeled DNS domain prepared for Exchange was detected. This is not a recommended configuration, and will not be ...
  67. A single-labeled DNS domain prepared for Exchange was detected. This isn't a recommended configuration. You should plan to ...
  68. A SIP OPTIONS message was rejected with the following parameters: From: "%1", To: "%2", Response Code: "%3", Response Headers: ...
  69. A SIP service request was rejected with the following parameters: From: "%1", To: "%2", Response Code: "%3", Response Headers: ...
  70. A situation where the server is configured to loop back on itself was detected. If you have multiple SMTP virtual servers ...
  71. A slow file IO operation was encountered on file '%1' for copy '%2'. The observed latency was %3 ms while performing a '%4'. ...
  72. A specified provisioning attribute '{0}' is invalid. Please ensure that each attribute name and value is non-empty and contains ...
  73. A strong authentication rule. It consists of a set of SelectionConditions. All the SelectionConditions must be evaluated ...
  74. A tag can be created based on the settings of an existing managed folder. Only one tag is created per selected managed folder. ...
  75. A target checkpoint file '{0}' already exists. You must remove this file before database seeding or reseeding can be performed. ...