XADM: The MTA Stops Processing Messages and Pulls All of the Messages That Are Queued (309194)

SYMPTOMS

In a mixed-mode Exchange site, an Exchange 2000 server may temporarily stop processing messages from Exchange Server 5.5 computers. Eventually the Exchange 2000 server message transfer agent (MTA) pulls all of the messages that are queued on the Exchange 5.5 server in the same site on a sporadic basis (every ten minutes).

This problem can occur in the following scenario:

Exchange Server 5.5 Computer ---- Intrasite MTA ---- Exchange 2000 Bridgehead Server ---- SMTP Mail ---- Other Sites

The messages on the Exchange Server 5.5 computer are not rerouted and may remain queued on the Exchange Server 5.5 MTA until the open interval timer expires.

CAUSE

This problem can occur if the Exchange 2000 MTA mishandles a failure to open an association with the Exchange Server 5.5 computer by doing a ResetRoute of that link, even if other associations between the two servers are currently open. If you stop all MTA communications, the Exchange 2000 server successfully re-establishes a brand new association by default 10 minutes later.

RESOLUTION

To resolve this problem, obtain the latest service pack for Exchange 2000 Server. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

301378 How to Obtain the Latest Exchange 2000 Server Service Pack

WORKAROUND

To work around this problem, in Exchange System Manager, in the X.400 Protocols properties, increase the Association parameters x400 Message Threshold association parameter from the default value of 50 to a larger value to avoid attempts at creating new associations. You can also work around this problem by changing the X.400 Open Interval value from the default value of 600 seconds to a larger value, such as 1800 seconds; this change causes the problem to occur once every 30 minutes instead of once every 10 minutes.

STATUS

Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. This problem was first corrected in Exchange 2000 Server Service Pack 2.