A non-delivery report with a status code of number was generated for recipient recipient (Message-ID id). Cause: This indicates a permanent failure. Possible causes : 1)No route is defined for a given address space. For example, an SMTP connector is configured, but this recipient address does not match the address spaces for which it routes mail. 2)Domain Name Server (DNS) returned an authoritative host not found for the domain. 3)The routing group does not have a connector defined ???? mail from one server in the routing group has no way to get to another routing group. Solution: Verify that this error is not caused by a DNS lookup problem, and then check the address spaces configured on your STMP connectors. If you are delivering Internet mail through an SMTP connector, consider adding an address space of type SMTP with value ????*???? (an asterisk) to one of the SMTP connectors to make routing possible. Verify all routing groups are connected to each other through a routing group connector or another connector.

Details
Product: Exchange
Event ID: 3008
Source: MSExchangeTransport
Version: 6.5.6940.0
Component: Microsoft Exchange Transport
Message: A non-delivery report with a status code of number was generated for recipient recipient (Message-ID id). Cause: This indicates a permanent failure. Possible causes : 1)No route is defined for a given address space. For example, an SMTP connector is configured, but this recipient address does not match the address spaces for which it routes mail. 2)Domain Name Server (DNS) returned an authoritative host not found for the domain. 3)The routing group does not have a connector defined ???? mail from one server in the routing group has no way to get to another routing group. Solution: Verify that this error is not caused by a DNS lookup problem, and then check the address spaces configured on your STMP connectors. If you are delivering Internet mail through an SMTP connector, consider adding an address space of type SMTP with value ????*???? (an asterisk) to one of the SMTP connectors to make routing possible. Verify all routing groups are connected to each other through a routing group connector or another connector.
   
Explanation

This event is logged when a non-delivery report is generated because Exchange cannot deliver a message. Possible causes for this event include the following:

  • No route is defined for a specific address space.
  • DNS returned an authoritative host not found response.
  • The routing group does not have a connector defined which prevents mail from servers in the routing group from being delivered to servers outside the routing group.
   
User Action

Verify that this error is not caused by a DNS lookup problem, a non-existent connector, or an incorrect address space. If you are delivering Internet mail through an SMTP connector, consider adding an address space with the value of * to the SMTP connector to make routing possible.

Related:

Process (PID=). DSAccess is unable to connect to the Domain Controller althoughits service location (SRV) resource record was found in the DNS The query was for the SRV record for The following domain controllers were identified by the query:Common causes of this error include:- Host (A) records that map the name of the domain controller to its IP addresses are missing or contain incorrect addresses.- Domain controllers registered in DNS are not connected to the network or are not running.For information about correcting this problem,

Details
Product: Exchange
Event ID: 2123
Source: MSExchangeDSAccess
Version: 6.5.6940.0
Component: Microsoft Exchange Directory Access Cache
Message: Process <process name> (PID=<process id>). DSAccess is unable to connect to the Domain Controller <name> althoughits service location (SRV) resource record was found in the DNS The query was for the SRV record for <distinguished name>The following domain controllers were identified by the query:<name>Common causes of this error include:- Host (A) records that map the name of the domain controller to its IP addresses are missing or contain incorrect addresses.- Domain controllers registered in DNS are not connected to the network or are not running.For information about correcting this problem, <text><text>
   
Explanation

This event will be seen if Diagnostics Logging on the Topology category of DSAccess is set to Minimum for the server. This event means that the domain controllers from the specified domain will not be used by DSAccess. As long as there is sufficient capacity in suitable domain controllers in other domains, it will not cause mail flow interruption. However, it is recommended that this event be investigated and fixed as soon as possible. If the event contains the name of the local domain, topology discovery cannot be completed, and this will cause mail flow interruption. This event may be logged if the required A (Address) resource records that map the names of the domain controllers to their respective IP addresses do not exist in DNS.

   
User Action

Verify that the required A resource records exist in DNS by using the Nslookup command-line tool.

Related:

Process (PID=). Error 0x occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain The query was for the SRV record for For information about correcting this problem,

Details
Product: Exchange
Event ID: 2122
Source: MSExchangeDSAccess
Version: 6.5.6940.0
Component: Microsoft Exchange Directory Access Cache
Message: Process <process name> (PID=<process id>). Error 0x<error code> occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain <name>The query was for the SRV record for <distinguished name>For information about correcting this problem, <text><text>
   
Explanation

This event occurs if Diagnostics Logging on the Topology category of DSAccess is set to Minimum for the server. It means that a non-specific error occurred when DNS was queried for SRV records for the specified domain. This event means that the domain controllers from the specified domain will not be used by DSAccess. As long as there is sufficient capacity in suitable domain controllers in other domains, mail flow will not be interrupted. However, it is recommended that this event be investigated and fixed as soon as possible. If the event contains the name of the local domain, topology discovery cannot be completed, and this will cause mail flow interruption. This can be caused if the required resource records on the DNS server are missing or are incorrect.

   
User Action

Verify that the required SRV and the A resource records exist in DNS by using the Nslookup command-line tool.

Related:

A non-delivery report with a status code of was generated for recipient (Message-ID ). Cause: This indicates a permanent failure. Possible causes : 1)No route is defined for a given address space. For example, an SMTP connector is configured, but this recipient address does not match the address spaces for which it routes mail. 2)Domain Name Server (DNS) returned an authoritative host not found for the domain. 3)The routing group does not have a connector defined û mail from one server in the routing group has no way to get to another routing group. Solution: Verify that this error is not caused by a DNS lookup problem, and then check the address spaces configured on your STMP connectors. If you are delivering Internet mail through an SMTP connector, consider adding an address space of type SMTP with value ô*ö (an asterisk) to one of the SMTP connectors to make routing possible.Verify all routing groups are connected to each other through a routing group connector or another connector.

Details
Product: Exchange
Event ID: 3008
Source: MSExchangeTransport
Version: 6.5.7638.0
Component: Microsoft Exchange Transport
Message: A non-delivery report with a status code of <number> was generated for recipient <recipient> (Message-ID <id>). Cause: This indicates a permanent failure. Possible causes : 1)No route is defined for a given address space. For example, an SMTP connector is configured, but this recipient address does not match the address spaces for which it routes mail. 2)Domain Name Server (DNS) returned an authoritative host not found for the domain. 3)The routing group does not have a connector defined û mail from one server in the routing group has no way to get to another routing group. Solution: Verify that this error is not caused by a DNS lookup problem, and then check the address spaces configured on your STMP connectors. If you are delivering Internet mail through an SMTP connector, consider adding an address space of type SMTP with value ô*ö (an asterisk) to one of the SMTP connectors to make routing possible.Verify all routing groups are connected to each other through a routing group connector or another connector.
   
Explanation

This event is logged when a non-delivery report is generated because Exchange cannot deliver a message. Possible causes for this event include the following:

  • No route is defined for a specific address space.
  • DNS returned an authoritative host not found response.
  • The routing group does not have a connector defined which prevents mail from servers in the routing group from being delivered to servers outside the routing group.
   
User Action

Verify that this error is not caused by a DNS lookup problem, a non-existent connector, or an incorrect address space. If you are delivering Internet mail through an SMTP connector, consider adding an address space with the value of * to the SMTP connector to make routing possible.

Related:

An unexpected error is forcing EXPS to close the SMTP connection to “%1”. “%2” called “%3” which failed with error code %4 ( %5@%6 ).

Details
Product: Exchange
Event ID: 1705
Source: MSExchangeTransport
Version: 6.5.7596.0
Message: An unexpected error is forcing EXPS to close the SMTP connection to “%1”. “%2” called “%3” which failed with error code %4 ( %5@%6 ).
   
Explanation

This Error event indicates that Microsoft® Exchange Server is closing an X-EXPS connection to another server in the Exchange Server organization. The X-EXPS command is a command that Exchange uses to implements SMTP server-to-server authentication.

The following are some common causes of this event:

  • Exchange is trying to connect to a remote server that advertises X-EXPS. However, the connection cannot be made because a valid FQDN is not provided. A valid FQDN may be required if you are using a third-party application that must use a Host file. See User Action.

  • An Exchange server is trying to connect to another Exchange server in the same organization that is not configured to enable relay between servers. See User Action.

   
User Action

To resolve this event, do one or more of the following:

  • If the remote server requires a valid FQDN, check to see whether the Host file is configured to resolve the NetBIOS name of the server to an IP address. If that is the way the Host file is configured, configure the Host file to resolve the FQDN to an IP address.

  • If Exchange is trying to connect to another Exchange server in the same organization that is not configured to enable relay between servers, do the following:

    1. Click Start, point to Programs, point to Microsoft Exchange, and then click System Manager.

    2. In System Manager, click Servers, click <Exchange server name>, click Protocols, and then click SMTP.

    3. Right-click Default Virtual SMTP Server, and then click Properties.

    4. On the Access tab, click Relay.

    5. Make sure that the Allow all computers which successfully authenticate to relay, regardless of the list above check box is selected.

  • In Event Viewer, examine the Application log for related events that are logged before of after this event message to determine. These related events may provide additional information about the cause for why the server to server communication link was closed.

For more information about the communication verb X-EXPS, see Microsoft Knowledge Base article 812455, Definitions of Verbs That Are Used Between 2 Exchange Servers.

Related:

SMTP could not connect to any DNS server.

Details
Product: Exchange
Event ID: 754
Source: MSExchangeActiveSyncNotify
Version: 6.5.6940.0
Component: Microsoft Mobile Sync Server
Message: SMTP could not connect to any DNS server.
   
Explanation

Simple Mail Transfer Protocol (SMTP) could not connect to any DNS servers. All DNS servers are down.

   
User Action

Use nslookup.exe to verify that all DNS servers are up and reachable.

Related:

Routing has reported the domain ” as unreachable. The error is ”.

Details
Product: Exchange
Event ID: 577
Source: MSExchangeActiveSyncNotify
Version: 6.5.6940.0
Component: Microsoft Mobile Sync Server
Message: Routing has reported the domain ‘<name>‘ as unreachable. The error is ‘<text>‘.
   
Explanation

Routing cannot find a functioning next-hop.

   
User Action

At some time in the past Exchange failed to deliver to the next-hop and routing marked the link as currently-unreachable. Look for other events in the log indicating problems delivering in the past. If the problem persists, restart the Simple Mail Transport Protocol (SMTP) Virtual Server and note which queue goes to retry. Highlight the queue and note the reason specified.

Related:

Routing has reported the domain ‘%1’ as unreachable. The error is ‘%2’.

Details
Product: Exchange
Event ID: 577
Source: MSExchangeTransport
Version: 6.5.0000.0
Message: Routing has reported the domain ‘%1’ as unreachable. The error is ‘%2’.
   
Explanation
Routing cannot find a functioning next-hop.
   
User Action
At some point of time in the past Exchange failed to deliver to the next-hop and routing marked the link as currently-unreachable. Look for other events in the log indicating problems delivering in the past. If the problem persists, restart the SMTP Virtual Server and note which queue goes to retry. Highlight the queue and note the reason specified.

Related:

Message delivery to the host ” failed while delivering to the remote domain ” for the following reason: The SMTP verb which caused the error is ”. The response from the remoteserver is ”.

Details
Product: Exchange
Event ID: 4007
Source: MSExchangeTransport
Version: 6.5.7638.0
Component: Microsoft Exchange Transport
Message: Message delivery to the host ‘<host name>‘ failed while delivering to the remote domain ‘<name>‘ for the following reason: <text> The SMTP verb which caused the error is ‘<text>‘. The response from the remoteserver is ‘<text>‘.
   
Explanation

This Warning event is logged when Exchange cannot deliver a message to a remote host. The event description should specify the reason for the failure.

Some common reasons for this Warning event include the following:

  • The connection was dropped by the remote host.
  • The remote SMTP service rejected AUTH negotiation.
  • The server trying to deliver the message cannot access the message delivery information in the message.
  • An SMTP protocol error occurred.
  • The server that is trying to deliver the message cannot connect to the remote server.
  • If a smart host has been specified in the properties of the SMTP virtual server, this event can be logged if the smart host is unreachable for any reason.
   
User Action

To resolve this error, try one or more of the following:

Related: