[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 there were issues 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 the cause of the message tracking log entry.
If the Exchange Server Analyzer finds a value of 1032 for the EntryType property, the Exchange Server Analyzer displays a warning.
This warning indicates that the test message is in a queue that is scheduled for a retry of categorization. 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.
Generally, messages accumulate in queues awaiting retry because the advanced queuing engine is unable to categorize the message. The advanced queuing engine may not be able to access the global catalog servers and access recipient information, or the global catalog servers are unreachable or performing slowly. In addition, messages can accumulate for the following reasons:
Active Directory is unavailable.
The categorizer uses Active Directory to categorize messages.
Active Directory may be too heavily loaded if many messages are queuing in the pre-categorization queue.
There is a failure in conversion. The categorizer also handles content conversion.
The message categorizer cannot find the mailbox stores.
If SMTP was reinstalled or removed, this may invalidate the following IIS metabase keys: /smtpsvc/DsUseCat and /smtpsvc/vsi#/DsUseCat.
Determine whether SMTP was reinstalled or removed.
If a queue is in a "Retry" status, examine the properties of the queue to determine the cause. For example, if the queue properties display a message that resembles "An SMTP error has occurred," you should review your server's event logs to locate any SMTP errors. If there are no events in the log, you should increase the SMTP Protocol logging level.
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).