'Messages Pending Submission' Queue is in Retry

[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 StateRetry key for the Simple Mail Transfer Protocol (SMTP) Messages Pending Submission queue.

If the Exchange Server Analyzer finds that the value of the StateRetry key for the Messages Pending Submission queue on an Exchange server is set to True, the Exchange Server Analyzer displays an error.

If a queue is in retry status, this status indicates that at least one error occurred in the previous attempts to process the messages in the queue. You can change queues in the Retry or Scheduled state to Active with the Force Connection command. This causes the queue to function as if the retry interval had passed or the scheduled time was reached. However, this method may not always work.


The properties of a queue can indicate a specific reason for a queue to be in Retry.

The Messages Pending Submission queue holds messages that have been acknowledged and accepted by the SMTP service.

Messages that are in this queue have not been processed. If messages are constantly accumulating, you may have a performance problem. Occasional peaks in CPU performance can cause messages to appear in this queue intermittently. Frequently, problems with event sinks, for example, custom SMTP processing code for antivirus screening and for disclaimers, cause messages to accumulate in this queue.

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: