Exchange Server 2016

  1. The syntax for a protocol command was either invalid or not recognized. The sender can try sending the e-mail message again ...
  2. The System Attendant isn't responding. It may be paused, or the version of the Administrator program may not match the version ...
  3. The system has detected a change in the available networks. The system is now using network '%1' instead of network '%2' ...
  4. The system has serviced a %1 task but it took an abnormally long time (%2 seconds to be dispatched, %3 seconds to be executed). ...
  5. The system has serviced a %1 task but it took an abnormally long time (%2 seconds to be dispatched, %3 seconds to be executed). ...
  6. The system has serviced a %4 task but it took an abnormally long time (%5 seconds to be dispatched, %6 seconds to be executed). ...
  7. The system has serviced a %4 task but it took an abnormally long time (%5 seconds to be dispatched, %6 seconds to be executed). ...
  8. The system is experiencing memory allocation failures that are preventing proper operation of database '%1' ('%2'). The error ...
  9. The system is experiencing memory allocation failures that are preventing proper operation of database '%4' ('%5'). The error ...
  10. The system setting indicates that it supports only {1} source mailboxes in a mailbox search. You have specified {0} source ...
  11. The tag type cannot be modified. Please create a new Retention Policy Tag with the desired tag type, or delete this tag and ...
  12. The target Client Access server version {1} is different from the version of the {0} cmdlet that was specified. The {0} cmdlet ...
  13. The target database '{0}' isn't an Exchange database. Neither MailEnableSourceAccount nor CreateSourceContact can be specified ...
  14. The target mailbox doesn't have an SMTP proxy matching '{0}'. The primary SMTP address '{1}' will be used as the external ...
  15. The target server cannot support OAB "{0}" since Version 4 is enabled. Either disable Version 4 generation or install KB ...
  16. The TargetApplicationUri of the remote organization doesn't match the local ApplicationUri of the Federation Trust object. ...
  17. The task and public folder database {0} connect to different domain controllers. Offline address book public folder distribution ...
  18. The task cannot locate the certificate to produce the subscription file. Check the local machine certificate store to ensure ...
  19. The task cannot locate the local server's configuration object. Check Active Directory to ensure the server object for {0} ...
  20. The task couldn't find the user {0}\{1} in Active Directory.This task needs to be able to look up the user to obtain the ...
  21. The task couldn't sign in with user {0}. Run {2} to verify that the user exists on the Mailbox server {1} To run this task ...
  22. The task failed to correctly generate RUS information Proxies, Addresslists, Policies included for this object, error '%1'. ...
  23. The task is attempting to communicate with the Microsoft Exchange Replication service on server "{0}" to obtain updated configuration ...
  24. The task is cancelled because the request operation on the mailbox search object '{0}' requires upgrading it to current version. ...
  25. The task was successful, but Active Directory may not reflect the current results until replication occurs. Error: "{0}". ...
  26. The task was unable to find any servers with the Client Access role but not the Mailbox role in the local Active Directory ...
  27. The task wasn't able to connect to IIS on the server '{0}'. Make sure that the server exists and can be reached from this ...
  28. The TCP/IP Port value configured for the Microsoft Exchange RPC Client Access service on server {0} is invalid. It's currently ...
  29. The TCP/IP Port value configured for the Microsoft Exchange RPC Client Access service on server {0} is outside of recommended ...
  30. The TCP/IP port value configured for the Microsoft Exchange RPC Client Access service on server {0} isn't valid. The current ...
  31. The TCP/IP Port value for the Microsoft Exchange RPC Client Access service and the RpcTcpPort value for the Exchange Address ...
  32. The temporary folder couldn't be deleted because the WebReady Document Viewing Manager doesn't have the permissions to delete ...
  33. The tenant organization isn't in an Active state. Complete the administrative tasks that are active for this organization, ...
  34. The term '{0}' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling ...
  35. The test can't proceed because the test URL isn't secure, and the authentication method supported by the virtual directory ...
  36. The test couldn't sign in to Outlook Web App because an SSL certificate couldn't be validated. You can force the cmdlet to ...
  37. The test doesn't support any authentication methods presented by the virtual directory.Authentication modes supported by ...
  38. The test mailbox doesn't reside in the correct site. This may have occurred because the test user's mailbox was moved.User ...
  39. The test mailbox doesn't reside on the correct server. This may have occurred because the test user's mailbox was moved.User ...
  40. The test mailbox was not initialized. Run new-TestCasConnectivityUser.ps1 to ensure that the test mailbox is created. Detailed ...
  41. The Test-CasConnectivity cmdlet failed at the first time. Insert an entry to TransientErrorCache. BaseUrl: %1. MbxServre: ...
  42. The Test-CasConnectivity cmdlet failed. Find the entry in TransientErrorCache. BaseUrl: %1. MbxServre: %2. Error: %3. Warning: ...
  43. The Test-PowershellConnectivity cmdlet on the %1 virtual directory failed because the %2 service isn't running on the server. ...
  44. The Test-PowershellConnectivity cmdlet on the '{0}' virtual directory failed because the service '{1}' isn't running on the ...
  45. The Test-ReplicationHealth cmdlet will query the Microsoft Exchange Replication service via RPC to retrieve copy status information. ...
  46. The Test-UMConnectivity cmdlet detected that the Microsoft Exchange Unified Messaging service on the Mailbox server is at ...
  47. The Test-UMConnectivity cmdlet successfully reset the PINs for the UM test mailboxes on the following Mailbox servers: {0}. ...
  48. The Test-UMConnectivity task couldn't find a valid TLS certificate to use for the connectivity check to Unified Messaging. ...
  49. The Test-UMConnectivity task encountered an error while initializing the VoIP platform for diagnostic tests. Details follow: ...
  50. The Test-UMConnectivity task encountered an error while trying to send a diagnostic message to the Mailbox server. Details ...
  51. The Test-UMConnectivity task is trying the Voice-over-IP connectivity and telephone user interface logon to the local Unified ...
  52. The Test-UMConnectivity task tried to sign in to the Mailbox server through the telephone user interface, but failed to retrieve ...
  53. The third highest source of RPC load is in the category '{1}'. This category accounts for {2} RPC operations/second, out ...
  54. The Third Party Replication listener is not yet running because Active Manager has not yet triggered initialization. If this ...
  55. The Third Party Replication listener provided by the vendor didn't respond because {0}. Check the third-party product to ...
  56. The Third Party Replication Manager could not access Active Directory. Error: %1. Initialization will be retried automatically. ...
  57. The time difference between the operating system of the Active Directory Connector server and the local Active Directory ...
  58. The timestamp for restored logfile %4 does not match the timestamp recorded in the logfile previous to it. For more information, ...
  59. The timestamp indicating the age of the last log generated on the active database copy is '{0}', which is stale or missing. ...
  60. The TLSAuthLevel parameter can't be set to DomainValidation on a smarthost Send connector without specifying a valid TLS ...
  61. The TMP/TEMP path on server {0} is located on the same drive as the system partition. This may cause performance problems. ...
  62. The TMP/TEMP path on server {0} isn't located on the same drive as the system partition. This may cause performance issues. ...
  63. The TO header of an incoming call with ID "{0}" didn't match the value specified in the UM IP Gateway property GatewayForwardingAddress. ...
  64. The token received by the federation partner does not contain a proof key. Check the application event log for more information. ...
  65. The tool has determined that distribution group expansion problems may be causing the 'Messages awaiting directory lookup' ...
  66. The tool has determined that journaling recipient problems are probably causing the 'Messages awaiting directory lookup' ...
  67. The tool has determined that journaling recipient problems may be causing the 'Messages awaiting directory lookup' queue ...
  68. The tool has determined that message journaling problems may be causing the 'Messages awaiting directory lookup' queue issue ...
  69. The tool has determined that permissions problems on one or more objects used by Exchange is probably causing the 'Messages ...
  70. The tool has determined that permissions problems on one or more objects used by Exchange may be causing the 'Messages awaiting ...
  71. The tool is starting an ETW trace session. If this is a timed trace, the trace session will run for {1} seconds and then ...
  72. The tool was not able to identify the fully-qualified domain name of all the remote servers. SMTP instance name checks cannot ...
  73. The tool was not able to identify the fully-qualified domain name or IP address of all the remote servers. Connectivity tests ...
  74. The Toolbox Work Center was unable to read the values under the {0} registry key because the current user does not have permission ...
  75. The topology does not contain any route to owning Mailbox Server %1 for database %2 in routing tables with timestamp %3. ...