XCON: MTA Process Can Leak Memory Because of Excessive Rerouting

This article was previously published under Q320225
This article has been archived. It is offered "as is" and will no longer be updated.
SYMPTOMS
The private bytes usage for the message transfer agent (MTA) process can reach up to 2 gigabytes (GB) in an environment where minor revision changes are made to the link state tables. This problem usually occurs on bridgehead servers. Usually, the minor version changes occur when there is any of the following situations (this is not a complete list):
  • A change in the connector settings
  • Misconfigured connectors (for example, an incorrect password)
  • Frequent addition and deletion of connectors
  • Unreliable network
After this condition occurs, the MTA generates the following events for any message that enter the MTA.
Event Type: Warning
Event Source: MSExchangeMTA
Event Category: X.400 Service
Event ID: 142
Date: 2/8/2002
Time: 3:08:36 PM
User: N/A
Computer: ServerName
Description:
The MTA was unable to route to recipient C=US;A=;P=Company;O=Site;DDA:SMTP=user(a)Company.net;. The message (MTS-ID): C=US;A=;P=Company;L=OrginateServer-020208210308Z-521102, recipient: C=US;A=;P=Company;O=Site;DDA:SMTP=user(a)Company.net;, recipient number 1. Check therouting table for a possible incorrect routing configuration. (MTA DISP:ROUTER16 119) (12)

Event Type: Warning
Event Source: MSExchangeMTA
Event Category: X.400 Service
Event ID: 290
Date: 2/8/2002
Time: 3:08:36 PM
User: N/A
Computer: ServerName
Description:
A non-delivery report (reason code unable-to-transfer and diagnostic codeunrecognised-OR-name) is being generated for message C=US;A=;P=Company;L=OrginateServer-020208210308Z-521102. It was originally destined forC=US;A= ;P=Company;O=Site;DDA:SMTP=user(a)Company.net; (recipient number 1), andwas to be redirected to . (MTA DISP:RESULT 36 136 (12)

Event Type: Warning
Event Source: MSExchangeMTA
Event Category: X.400 Service
Event ID: 141
Date: 2/8/2002
Time: 3:08:37 PM
User: N/A
Computer: ServerName
Description:
The MTA is unable to route a report for message C=US;A=;P=Company;L=OrginateServer-020208210308Z-521102 to recipientDN:CN=Alias,CN=Name,OU=Site,O=Company -- C=US;A=;P=Company;O=Site;S=SurName;G=GivenName;. MTA object at fault: 060009B3. Checkthe routing table for a possible incorrect routing configuration. (MTADISP:ROUTER 16 40) (12)
RESOLUTION
To resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
301378 XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
The English version of this fix should have the following file attributes or later:

Component: MTA

File nameVersion
Emsmta.exe6.0.5770.85
X400om.dll6.0.5770.85
X400omv1.dll6.0.5770.85

NOTE: Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 2.
STATUS
Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 3.
memory leak mta reset routes
Properties

Article ID: 320225 - Last Review: 10/24/2013 11:10:12 - Revision: 2.3

Microsoft Exchange 2000 Enterprise Server

  • kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbexchange2000presp3fix kbexchange2000sp3fix kbfix KB320225
Feedback