'Remote Delivery' Queue Issue
[This topic is intended to address a specific issue called out by the Exchange Server Analyzer Tool. You should apply it only to systems that have had the Exchange Server Analyzer Tool run against them and are experiencing that specific issue. The Exchange Server Analyzer Tool, available as a free download, remotely collects configuration data from each server in the topology and automatically analyzes the data. The resulting report details important configuration issues, potential problems, and nondefault product settings. By following these recommendations, you can achieve better performance, scalability, reliability, and uptime. For more information about the tool or to download the latest versions, see "Microsoft Exchange Analyzers" at http://go.microsoft.com/fwlink/?linkid=34707.]
Topic Last Modified: 2006-05-17
The Microsoft® Exchange Server Analyzer Tool sends a test message from the Exchange server to the Postmaster account or a user-defined account for the Simple Mail Transfer Protocol (SMTP) domain and then scans the message tracking logs of the server to determine whether any issues were found with the delivery of the test message.
As a part of this scan, the Exchange Server Analyzer queries the EntryType property for the Exchange_MessageTrackingEntry Microsoft Windows® Management Instrumentation (WMI) class under the root\MicrosoftExchangeV2 namespace to determine what caused the message tracking log entry(s) to be created.
The Exchange Server Analyzer displays an error if the following conditions are true:
The message tracking log can be scanned successfully.
The test message did not successfully transfer out of the queue.
A Non Delivery Report (NDR) was not generated.
A value of 1034 exists for the EntryType property.
This error indicates that the test message is still in one of the Simple Mail Transfer Protocol (SMTP) Remote Delivery queues for the sending server and there is an issue with the queue.
A Remote Delivery queue holds messages that are destined for remote delivery. The name of the queue matches the remote delivery destination. This destination may be a connector, a server, or a domain.
To resolve this error, use the NSlookup utility to review possible issues with Domain Name System (DNS) resolution. For connection and protocol issues such as Host unreachable errors, use Telnet.exe to try to connect to the destination computer. To troubleshoot protocol errors, increase diagnostic logging for the MSExchangeTransport service for the SMTP Protocol component, and review the logs for errors. Alternatively, you can use the Network Monitor (Netmon.exe) tool to obtain information about network connection errors. To reproduce the problem, you may have to force the queue to try again. Examine the event log for possible errors associated with the Microsoft Exchange Information Store service.
For more information about how to modify logging settings, see "How to Modify Logging Settings for MSExchangeTransport" in the "Troubleshooting Mail Flow and SMTP" section of the Exchange Server Transport and Routing Guide (http://go.microsoft.com/fwlink/?LinkId=47579).
For more information about how to troubleshoot SMTP queues, see the following Exchange resources:
"Troubleshooting Mail Flow and SMTP" in the Exchange Server Transport and Routing Guide (http://go.microsoft.com/fwlink/?LinkId=47579).
Microsoft Knowledge Base article 823489, "How to use Queue Viewer to troubleshoot mail flow issues in Exchange Server 2003" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=823489).
Microsoft Knowledge Base article 821877, "Description of Fields on the SMTP and X.400 Queue Properties Tabs" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=821877).
Microsoft Knowledge Base article 264054, "XCON: Understanding Queue States in Exchange 2000 Server" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=264054).