Exchange Server 2010

  1. The task was successful, but Active Directory may not reflect the current results until replication occurs. Error: "{0}". ...
  2. The task was unable to find any Hub Transport servers without the Mailbox server role in the local Active Directory site. ...
  3. 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 ...
  4. The TCP/IP Port value configured for the Microsoft Exchange RPC Client Access service on server {0} is invalid. It's currently ...
  5. The TCP/IP Port value configured for the Microsoft Exchange RPC Client Access service on server {0} is outside of recommended ...
  6. The TCP/IP Port value for the Microsoft Exchange RPC Client Access service and the RpcTcpPort value for the Exchange Address ...
  7. The temporary folder couldn't be deleted because the WebReady Document Viewing Manager doesn't have the permissions to delete ...
  8. The temporary folder couldn't be deleted because the WebReady Document Viewing Manager doesn't have the permissions to delete ...
  9. The temporary recovery folder must be empty at this point. There should be no database or transaction log files from other ...
  10. The tenant organization isn't in an Active state. Complete the administrative tasks that are active for this organization, ...
  11. The term '{0}' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling ...
  12. The test can't proceed because the test URL isn't secure, and the authentication method supported by the virtual directory ...
  13. The test couldn't sign in to Outlook Web App because an SSL certificate couldn't be validated. You can force the cmdlet to ...
  14. The test couldn't sign in to Outlook Web App because an SSL certificate couldn't be validated. You can force the cmdlet to ...
  15. The test doesn't support any authentication methods presented by the virtual directory. Authentication modes supported by ...
  16. The test doesn't support any authentication methods presented by the virtual directory. Authentication modes supported by ...
  17. The test mailbox doesn't reside in the correct site. This may have occurred because the test user's mailbox was moved. User ...
  18. The test mailbox doesn't reside in the correct site. This may have occurred because the test user's mailbox was moved. User ...
  19. The test mailbox doesn't reside on the correct server. This may have occurred because the test user's mailbox was moved. ...
  20. The test mailbox doesn't reside on the correct server. This may have occurred because the test user's mailbox was moved. ...
  21. The test mailbox was not initialized. Run new-TestCasConnectivityUser.ps1 to ensure that the test mailbox is created. Detailed ...
  22. The test mailbox was not initialized. Run new-TestCasConnectivityUser.ps1 to ensure that the test mailbox is created. Detailed ...
  23. The test step {1} running over protocol '{0}' issued from test user '{2}' failed with error: '{3}'. The detailed information ...
  24. The Test-PowershellConnectivity cmdlet on the %1 virtual directory failed because the %2 service isn't running on the server. ...
  25. The Test-PowershellConnectivity cmdlet on the %1 virtual directory failed because the %2 service isn't running on the server. ...
  26. The Test-PowershellConnectivity cmdlet on the '{0}' virtual directory failed because the service '{1}' isn't running on the ...
  27. The Test-ReplicationHealth cmdlet will query the Microsoft Exchange Replication service via RPC to retrieve copy status information. ...
  28. The Test-UMConnectivity cmdlet successfully reset the PINs for the UM test mailboxes on the following Mailbox servers: {0}. ...
  29. The Test-UMConnectivity task couldn't find a valid TLS certificate to use for the connectivity check to Unified Messaging. ...
  30. The Test-UMConnectivity task encountered an error while initializing the VoIP platform for diagnostic tests. Details follow: ...
  31. The Test-UMConnectivity task encountered an error while trying to send a diagnostic message to the Unified Messaging server. ...
  32. The Test-UMConnectivity task is trying the Voice-over-IP connectivity and telephone user interface logon to the local Unified ...
  33. The Test-UMConnectivity task tried to sign in to the UM server through the telephone user interface, but failed to retrieve ...
  34. The third highest source of RPC load is in the category '{1}'. This category accounts for {2} RPC operations/second, out ...
  35. The Third Party Replication listener is not yet running because Active Manager has not yet triggered initialization. If this ...
  36. The Third Party Replication listener provided by the vendor didn't respond because {0}. Check the third-party product to ...
  37. The Third Party Replication Manager could not access Active Directory. Error: %1. Initialization will be retried automatically. ...
  38. The Third Party Replication Manager could not access Active Directory. Error: %1. Initialization will be retried automatically. ...
  39. The time difference between the operating system of the Active Directory Connector server and the local Active Directory ...
  40. The timestamp for restored logfile %4 does not match the timestamp recorded in the logfile previous to it. For more information, ...
  41. The timestamp for restored logfile %4 does not match the timestamp recorded in the logfile previous to it. For more information, ...
  42. The timestamp indicating the age of the last log generated on the active database copy is '{0}', which is stale or missing. ...
  43. The TLSAuthLevel parameter can't be set to DomainValidation on a smarthost Send connector without specifying a valid TLS ...
  44. The token received by the federation partner does not contain a proof key. Check the application event log for more information. ...
  45. The tool has determined that distribution group expansion problems may be causing the 'Messages awaiting directory lookup' ...
  46. The tool has determined that journaling recipient problems are probably causing the 'Messages awaiting directory lookup' ...
  47. The tool has determined that journaling recipient problems may be causing the 'Messages awaiting directory lookup' queue ...
  48. The tool has determined that message journaling problems may be causing the 'Messages awaiting directory lookup' queue issue ...
  49. The tool has determined that permissions problems on one or more objects used by Exchange is probably causing the 'Messages ...
  50. The tool has determined that permissions problems on one or more objects used by Exchange may be causing the 'Messages awaiting ...
  51. The tool is starting an ETW trace session. If this is a timed trace, the trace session will run for {1} seconds and then ...
  52. The tool was not able to identify the fully-qualified domain name of all the remote servers. SMTP instance name checks cannot ...
  53. The tool was not able to identify the fully-qualified domain name or IP address of all the remote servers. Connectivity tests ...
  54. The Toolbox Work Center was unable to read the values under the {0} registry key because the current user does not have permission ...
  55. The topology does not contain any route to server %1 in Active Directory site %2 in routing tables with timestamp %3. Recipients ...
  56. The topology does not contain any route to server %1 in Active Directory site %2 in routing tables with timestamp %3. Recipients ...
  57. The topology doesn't contain a route to Active Directory site %1 in routing tables with the timestamp %2. Recipients will ...
  58. The topology doesn't contain a route to Active Directory site %1 in routing tables with the timestamp %2. Recipients will ...
  59. The topology doesn't contain a route to Exchange 2000 Server or Exchange Server 2003 %1 in Routing Group %2 in routing tables ...
  60. The topology doesn't contain a route to Exchange 2000 Server or Exchange Server 2003 %1 in Routing Group %2 in routing tables ...
  61. The total external RMS Messages Prelicensed is the total number of messages IRM-protected by external RMS servers that are ...
  62. The total number of Exchange Virtual Servers on this cluster has exceeded the allowable limit for active/passive to operate. ...
  63. The total number of recipient updates where only a portion of safe or block lists was propagated to Active Directory due ...
  64. The total number of repeated queries performed to retrieve data for the same recipient across all instances of Active Directory ...
  65. The total number of search requests rejected by the Log search service. Rejection can occur because the service is too busy, ...
  66. The total number of searches that are performed to look for the corresponding initiation message based on the OOFs and NDRs ...
  67. The total number of threads configured for the message store (%1) appears to be too small for the current store configuration. ...
  68. The total number of threads configured for the message store (%1) appears to be too small for the current store configuration. ...
  69. The total size of the files needed to perform an incremental reseed exceeds {0}% of the total size needed for a full reseed. ...
  70. The total time a Windows PowerShell Runspace was kept active during the request. This includes the time necessary to activate ...
  71. The total time spent on the request, as measured by the client. This value ultimately measures the user perceived performance ...
  72. The total time spent processing the request on the server. However, this does not include the network time to send or receive ...
  73. The total time to spend collecting data. Typical values would be one to three hours; longer durations should only be used ...
  74. The transaction log files required to successfully recover this database to the point at which it was last running are available, ...
  75. The transport process couldn't load poison message information from the registry. Access to the registry failed with the ...