Exchange Server 2007

  1. MSExchangeTransport found invalid smart hosts string %1 on SMTP connector %2 in routing tables with timestamp %3. MSExchangeTransport ...
  2. MTLS requires that both the SIP endpoint and Windows server be issued an X.509 certificate signed by a trusted certification ...
  3. Multiple edits have been made to the same message. Please use an alternate client to view this message in order to get more ...
  4. Multiple matches were found for the OWA forms authentication Web Service Extension, using the following: module {1} GroupID ...
  5. Multiple matching users were found for the mailbox that you specified. Please use the -User parameter to specify the user ...
  6. Multiple modifications have been made to the same folder. Please use an alternate client to view this message in order to ...
  7. Multiple users are complaining of delays while using Outlook, or are seeing the Outlook cancellable RPC dialog frequently ...
  8. Network interface card (NIC) teaming is enabled on server {2}. Ensure that the latest drivers are installed. Current driver: ...
  9. Network interface driver file '{5}' for '{1}' on server {2} is more than two years old. Check with your vendor to find out ...
  10. Network interface teaming is enabled on server {2}. Ensure that the latest drivers are installed. Current driver: {0} - {6} ...
  11. Network problems are preventing connection to the Microsoft Exchange Server computer. Contact your system administrator if ...
  12. Newly copied log file %2 for %1 is corrupt. Re-seeding the passive node is now required. Use the Update-StorageGroupCopy ...
  13. No Accepted Domain objects found in Active Directory on server {2}. This may cause issues with the ability for the organization ...
  14. No Client Access server has been specified or found. You must either run this on a Client Access server, or use the ClientAccessServer ...
  15. No computer account in Active Directory has '{5}' set to '{3}'. This will result in Kerberos authentication failures when ...
  16. No connector for routing group '{3}' was found in the link state information maintained by server {2}. This may cause mail ...
  17. No conversion was possible, this is a type converter for simple generic class and the generic can only take one parameter. ...
  18. No customized DSN text is configured for the enhanced status code '{0}'. You can use New-SystemMessage cmdlet to configure ...
  19. No database session was available to satisfy a request on the mailbox database '%2'. The number of sessions configured via ...
  20. No database session was available to satisfy a request on the public folder database '%2'. The number of sessions configured ...
  21. No default clustered mailbox server could be determined for node {0}. This task requires that a clustered mailbox server ...
  22. No DNS servers could be retrieved from network adapter %1. Check if the computer is connected to a network and Get-NetworkConnectionInfo ...
  23. No EdgeSync Configuration or Accepted Domain issues were identified in any of the Active Directory Application Mode (ADAM) ...
  24. No EdgeSync credential found in Active Directory Application Mode (ADAM) instance on server {2} for Edge Transport server ...
  25. No EdgeSync credentials were found for Edge transport server {0} on the local Hub Transport server. Remove the Edge subscription ...
  26. No EdgeSync credentials were found in Active Directory for Edge Transport server role computer {2}. This occurs when the ...
  27. No EdgeSync credentials were found in Active Directory for Hub Transport server role computer {2}. This occurs when the EdgeSync ...
  28. No Exchange Server User Monitor (ExMon) data was analyzed. You must provide the name of a file containing the ExMon ETL trace ...
  29. No form of authentication has been specified for the '{0}' virtual directory. Use the Set-OwaVirtualDirectory cmdlet to specify ...
  30. No Host (A) records of SMTP instance '{3}' (fully-qualified domain name: {1}) can be obtained from any DNS servers server ...
  31. No issues were found when validating critical configuration objects in the Active Directory Application Mode (ADAM) instance ...
  32. No issues were found with the location of the Exchange data files, page file, TEMP directory or TMP directory, or with the ...
  33. No known issues were found with CPU load. Even though some RPC operations may be consuming significant CPU resources, this ...
  34. No known issues were found with RPC load. Even though some RPC operations may be consuming significant CPU resources, this ...
  35. No legacy DN could be returned for the object with sid %1. The object may not have a legacyDN, or other temporary errors ...
  36. No mailbox databases were found on {0} to perform the operation. Check if the user has permissions to read the Exchange configuration ...
  37. No mailbox was found to perform the transaction. You may need to wait for the Active Directory replication. The target database ...
  38. No matching users were found. Please use the -User parameter to specify the user to which this mailbox should be connected. ...
  39. No member for routing group '{3}' was found in the link state information maintained by server {2}. This may cause mail flow ...
  40. No operation is required because the Exchange 2007 default administrative group "{0}" does not exist. Setup may be installing ...
  41. No operator extension number has been configured for the UM auto attendant named "%1", or for the Dial Plan to which it belongs. ...
  42. No Pointer (PTR) record for IP address {4} can be obtained from any DNS servers server {2} uses. This may cause routing problems ...
  43. No previous version of an offline address list for '%1' can be found. No differential update file will be produced. This ...
  44. No process other than the {0} process was consuming more than 10% of the server CPU. This indicates the {0} process is most ...
  45. No providers are found in the folder "%1". The Autodiscover service is unable to process any valid requests. Check Autodiscover ...
  46. No replacements were specified for recipient '{0}' in the speech grammar filter list. The entry will be discarded from grammar. ...
  47. No route has been created for public folder hierarchy %1 in routing tables with timestamp %2. Recipients will not be routed ...
  48. No route to message, next hop not found. You have set up a Routing Group topology but there is no Routing Group Connector ...
  49. No routing group master has been specified for routing group '{3}'. This routing group may be isolated from other routing ...
  50. No SMTP connector was found for non-authoritative SMTP address space '{1}'. Exchange cannot forward messages to an external ...
  51. No SMTP connectors with Exchange gateway server {2} as the local bridgehead appear to have non-Exchange gateway server {1} ...
  52. No SMTP instances on server {2} are set to accept and forward messages addressed to non-authoritative SMTP address space ...
  53. No source transport servers or home MTA server have been set for connector %1 in routing tables with timestamp %2. Ignoring ...
  54. No target bridgehead servers were found for routing group connector %1 in routing tables with timestamp %2. Ignoring the ...
  55. No user data was found in Exchange Server User Monitor (ExMon) ETL trace file '{0}'. This may be because you are not running ...
  56. No valid agents.config file was found in '{0}', so a new one was created. You can recover the default configuration for Transport ...
  57. No valid agents.config file was found in '{0}'. The default configuration for transport agents can be recovered by running ...
  58. No valid Transport Layer Security (TLS) certificate was found. Microsoft Exchange can't update the Active Directory Application ...
  59. No Windows domains found. You will only be able to select Windows accounts defined on this computer. This means that future ...
  60. Non Smtp Gateway Connection Failure on Connector %1. The drop directory filename %2 exceeds the system-defined maximum length. ...
  61. Non-delivery reports will be sent for all messages in the selected {0} queues, and then the messages will be deleted. Do ...
  62. Non-delivery reports will be sent for the {0} selected messages, and then all selected messages will be deleted. Do you want ...
  63. Non-SMTP address space '%1' was detected on the DNS SMTP connector '%2' in routing tables with timestamp %3. The address ...
  64. Non-SMTP connector %1 failed because the Drop directory %2 does not have the correct access permissions. Change the access ...
  65. Nonpaged pool memory on server {2} is over the critical threshold of {8} MB. System instability may occur. Current value: ...
  66. Nonpaged pool memory on server {2} is over the warning threshold of {8} MB. This may cause system instability. Current value: ...
  67. Not Found DN Entries (Configuration Data) is the total number of configuration data "Not Found DN" type entries in the cache. ...
  68. Not Found DN Entries Memory (Configuration Data) is the memory occupied by all configuration data "Not Found DN" Entries ...
  69. Not Found DN Entries Memory (User Data) is the memory occupied by all user data "Not Found DN" Entries in the cache (in bytes) ...
  70. Not Found GUID Entries (Configuration Data) is the total number of configuration data "Not Found GUID" type entries in the ...
  71. Not Found GUID Entries Memory (Configuration Data) is the memory occupied by all configuration data "Not Found GUID" Entries ...
  72. Not Found GUID Entries Memory (User Data) is the memory occupied by all user data "Not Found GUID" Entries in the cache (in ...
  73. Not including the {0} process, the process using the most processor time is {1}, which is consuming {2}% of the CPU time. ...
  74. Not including the {0} process, the process using the most processor time is {1}, which is consuming {2}% of the CPU time. ...
  75. Not including the {0} process, the process using the most processor time is {1}, which is consuming {2}% of the CPU time. ...