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:

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: