Topic Last Modified: 2006-05-04

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 any 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 1037 for the EntryType property, the Exchange Server Analyzer displays a warning.

This warning indicates that at least one error occurred in the previous attempts to process the message in the Local Delivery queue.

The Local Delivery queue contains messages that are queued on the Exchange server for local delivery to an Exchange Server mailbox or public folder store.

Messages can accumulate in this queue if the Exchange server is not accepting messages for local delivery. Slow or intermittent message delivery can indicate a looping message or a performance problem.

You can change queues that are in the Retry or Scheduled state to the Active state 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.

To resolve this error, increase diagnostic logging for the MSExchangeIS and MSExchangeTransport service SMTP store driver components.

For more information about how to modify logging settings, see "How to Modify Logging Settings for MSExchangeTransport" in the "Troubleshooting Mailflow and SMTP" section of the Exchange Server Transport and Routing Guide (

For more information about how to troubleshoot SMTP queues, see the following Exchange resources: