Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

The Message Tracking Center indicates that a message was delivered to an incorrect server in Exchange Server 2003


View products that this article applies to.

Symptoms

On a computer that is running Microsoft Exchange Server 2003, when you use the Message Tracking Center tool to view the message history of a sent message, incorrect information appears in the Message History dialog box.

In this scenario, the Message History dialog box indicates that a message has been delivered to an incorrect Exchange Server computer. For example, information that is similar to the following appears in the Message History dialog box:
Event TimeEvent
9/3/2004 2:25 PMSMTP: Message to Advanced Queuing
9/3/2004 2:25 PMSMTP: Started Message Submission to Advanced Queue
9/3/2004 2:25 PMSMTP: Message Submitted to Categorizer
9/3/2004 2:25 PMSMTP: Message Categorized and Queued for Routing
9/3/2004 2:25 PMSMTP: Message Routed and Queued for Gateway Delivery
9/3/2004 2:25 PMSMTP: Message Delivered Locally to username@contoso.com
9/3/2004 2:25 PMSMTP: Store Driver Submitted Message to MTA
This information indicates that the message was delivered to the user on the local Exchange Server computer. However, the message was delivered to a user on a remote Exchange Server computer.

↑ Back to the top


Cause

This is a Message Tracking Center display issue. The message has to be sent to the MTA through the Information Store, or it will not reach a recipient through X.400. For example, this problem may occur if the following conditions are true:
  • You configure an X.400 connector between two Exchange Server 2003 computers.
  • You send a message from one of those Exchange Server 2003 computers to a user whose mailbox is hosted on the other Exchange Server 2003 computer.

↑ Back to the top


Workaround

To work around this problem, configure a Simple Mail Transfer Protocol (SMTP) connector between your Exchange Server 2003 routing groups. For additional information about how to create and configure an SMTP connector in Exchange Server 2003, see the Exchange Server 2003 Administration Guide. To obtain this guide, visit the following Microsoft Web site:http://technet.microsoft.com/en-us/library/3b5e4430-6f3e-42a9-b44f-def97fc42d0c.aspx

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


More information

For more information, click the following article number to view the article in the Microsoft Knowledge Base:
821905 Message tracking event IDs in Exchange Server 2003

↑ Back to the top


Keywords: KB870710, kbprb, kbtshoot, kbbug, kbpending, kbenv, kbarchive, kbnosurvey

↑ Back to the top

Article Info
Article ID : 870710
Revision : 5
Created on : 1/8/2015
Published on : 1/8/2015
Exists online : False
Views : 433