Export (0) Print
Expand All
Expand Minimize

'Remote Delivery' Queue is Frozen

[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 queries the ExchangeLink Windows® Management Instrumentation (WMI) class to determine the value of the StateFrozen key for the Simple Mail Transfer Protocol (SMTP) Remote Delivery queue.

If the Exchange Server Analyzer finds that the value of the StateFrozen key for the Remote Delivery queue on an Exchange server is set to True, the Exchange Server Analyzer displays an error.

A frozen queue means the transport sessions for that queue are stopped. A frozen queue prevents outgoing messages, although new messages can be added. You can manually change the state of a connection by using the shortcut menu on each link queue. When you use the Force Connection command to change a queue state to Active, you immediately enable a connection that sends the messages from that queue.

The 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:

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft