Exchange Server 2016

  1. /Hosting mode is not available with the current version of Exchange. Upgrading from Exchange Server 2010 /hosting to Exchange ...
  2. A 'CrossTenantObjectId' cannot be generated for the given object because it is unable to evaluate a valid value for '{0}'. ...
  3. A 'MSExchangeIS Mailbox Store' event was logged within the last 24 hours indicating a server performance issue due to excessive ...
  4. A archive mailbox will be created for '{0}'. Select between the "local archive" and "remote hosted archive" options below ...
  5. A bad page link (error %4) has been detected in a B-Tree (ObjectId: %5, PgnoRoot: %6) of database %7 (%8 => %9, %10). For ...
  6. A call for user %1 in dial plan %2 was rejected, because no legacy server could be found to handle a call for this user. ...
  7. A call for user %1 was received in dial plan %2. The user is on a legacy mailbox, and the dial plan doesn't have any legacy ...
  8. A call received with the following parameters: Calling party: "%1", Called party: "%2", Diversion information: "%3", Referred-By ...
  9. A call was received with the following parameters: Calling party: "%1", Called party: "%2", Diversion information: "%3", ...
  10. A categorizer forward loop was detected. The 'targetAddress' attribute is set on a mailbox-enabled user. This is a common ...
  11. A certificate '{0}' was found for thumbprint '{1}', but its Private Key was not present. This usually happens when certificate ...
  12. A certificate using the thumbprint '{0}' specified in the UMCertificateThumbprint property of the '{1}' object wasn't found. ...
  13. A change in network configuration was detected. The role for cluster network '%1' subnet '%2' was changed from '%3' to '%4'. ...
  14. A checked build of the operating system is installed on server {2}. This can cause system instability issues including crashes, ...
  15. A checked build of the operating system is installed. This can cause system instability issues including crashes, hangs, ...
  16. A Client Access array has been added or removed. The Client Access array registry setting has been modified. Old value: %1 ...
  17. A Client Access server array was found in site '{2}'. However, database '{3}' is configured to use Client Access server '{4}' ...
  18. A Client Access server array was found in site '{2}'. However, database '{3}' is configured to use Client Access server array ...
  19. A Client Access server has been added or removed. The Client Access server registry setting has been modified. Old value: ...
  20. A Client Access server has been added or removed. The Client Access server resource pool registry setting has been modified. ...
  21. A cluster named '{0}' already exists in Active Directory. Either disable the account or select a different name for the database ...
  22. A communication error has occurred and we can't access your account. The server returned the error response {1} for the command ...
  23. A communication error has occurred and we can't access your account. The server returned the unrecognized response {1} for ...
  24. A communication error has occurred and your account can't be accessed. The server returned the TLS failure response {0}. ...
  25. A compliance request requires a path to the store (-ComplianceStorePath) and appropriate credentials (-RemoteCredentials). ...
  26. A component has failed to retrieve updated configuration information. The component may still be running with old configuration ...
  27. A component with the name '{0}' does not exist. Available component names are {1}. Make sure the name is correct and the ...
  28. A computer account named '{0}' already exists and is enabled. The account must be disabled in order to be used by the database ...
  29. A configuration error is preventing proper operation of database '%1' ('%2'). The error may occur because of a database misconfiguration, ...
  30. A configuration error is preventing proper operation of database '%4' ('%5'). The error may occur because of a database misconfiguration, ...
  31. A configuration error occurred in item {1} of property {0}: '{2}'. Values for this field should be at least {3} characters ...
  32. A configuration management scope can't be enabled on the "{0}" role assignment. It can only be enabled on an on-premises ...
  33. A configuration update occurred but the internal %1 cache failed to load. Microsoft Exchange will retain the existing configuration. ...
  34. A connection could not be made to the remote directory service, possibly due to network failure. Be sure that both directory ...
  35. A connection couldn't be made to the Exchange server named {0}. Verify that the Microsoft Exchange Service Host service is ...
  36. A connection couldn't be made to the Exchange server named {0}. Verify that the Microsoft Exchange Transport service is started. ...
  37. A connection couldn't be made to the Microsoft Exchange Unified Messaging service on the server named {0}. Verify that the ...
  38. A corrupted Classification Definition has been found. Recreating the definition may solve the problem. This definition will ...
  39. A corrupted classification rule collection has been identified. This classification rule collection will not be used for ...
  40. A corrupted log file for copy '%1' was detected: %2 Recovery was attempted by marking this copy as Failed and failing over ...
  41. A corrupted Outlook protection rule has been found. Recreating the rule may solve the problem. This rule will not be returned ...
  42. A corrupted Policy Nudge rule has been found. Recreating the rule may solve the problem. This rule will not be returned to ...
  43. A credential for the alternate service account "{0}" that was added on {1} is incorrect or no longer valid. Failure reason ...
  44. A credential for the alternate service account "{0}" that was added on {1} is valid. Other credentials for this account are ...
  45. A data validation error occurred. This situation can happen when directory objects aren't formatted correctly. Check for ...
  46. A database backup is already in progress. Please verify that no other seeding or incremental reseeding operations are started ...
  47. A database location change was detected from '%4' to '%5'. For more information, click http://www.microsoft.com/contentredirect.asp. ...
  48. A database operation has encountered a fatal error. The Microsoft Exchange Transport service is shutting down. Exception ...
  49. A database operation has encountered an I/O error. The Microsoft Exchange Transport service is shutting down. Exception details: ...
  50. A database page failed verification due to a timestamp mismatch for {1}. The dbtime on a page is in advance of the dbtimeBefore ...
  51. A database page failed verification due to a timestamp mismatch for {1}. The dbtime on a page smaller than the dbtimeBefore ...
  52. A default role assignment policy wasn't found. New mailboxes won't have any role assigned unless a role assignment policy ...
  53. A discovery mailbox can't be created on server '{0}'. The database that contains the mailbox store must be located on a server ...
  54. A Distinguished Name DN cannot be generated for this object.The Directory prevents further objects of this type from being ...
  55. A Document failure resulting in the CTS node being restarted has occurred. MdbGuid: %1, DocId: %2, CorrelationId: %3 ErrorMessage: ...
  56. A dumpster redelivery request for database '{0}' could not be created because the request was invalid. Either the request ...
  57. A duplicate data classification identifier '%2' has been identified in objects with DN '%3' and '%4' under organization '%1'. ...
  58. A duplicate mailbox was found due to problems during a Move Request procedure. The duplicate mailbox has been deleted. Try ...
  59. A failure item with message id {0} occurred, but the message could not be formatted. There may be a problem with the set ...
  60. A failure occurred while opening a mailbox for user '%1'. ServerName = '%2'. Database = '%3'. More Information: '%4'. Please ...
  61. A failure occurred while trying to contact the Mailbox server '%1' for the '%2' operation. Please make sure that the Microsoft ...
  62. A fatal error occurred during generation of a UM report in the mailbox with user principal name %1. The system had to reinitialize ...
  63. A fatal error occurred in the %1. The Service Control Manager will restart the %1 automatically to recover from this error. ...
  64. A fax call to the user "%1" couldn't be received because no valid fax partner URI is specified for the UM mailbox policy ...
  65. A flight with the name '{0}' does not exist. Available flight names are {1}. Make sure the name is correct and the version ...
  66. A folder couldn't be created to cache the current Outlook Web App process. Other processes may be using the same directory. ...
  67. A forced configuration update for %1 has successfully completed. Object details from the last notification-based reload: ...
  68. A function call to '{6}' took longer than the threshold value of {5} seconds to complete. The call took {9} seconds. This ...
  69. A function call to '{6}' took longer than the threshold value of {5} seconds to complete. The call took {9} seconds. This ...
  70. A function call to {4} took longer than the threshold value of {5} seconds to complete. The call '{6}' took {9} seconds. ...
  71. A gap in the logfile sequence was detected. Logfile %1 is missing. Other logfiles past this one may also be required. This ...
  72. A gap in the logfile sequence was detected. Logfile %4 is missing. Other logfiles past this one may also be required. This ...
  73. A GetCopyStatus RPC hang has been detected on Server {0} for 15 mins. The MSExchangeDagMgmt and MSExchangeRepl services are ...
  74. A GetCopyStatus RPC hang was detected on Server {0} for 90 mins. The problem was not automatically resolved. The MSExchangeDagMgmt ...
  75. A Global Catalog (GC) server has been added or removed. The %3 registry setting has been modified. Old value: %1 New value: ...