Article ID: 328654
Article Last Modified on 2/20/2007
APPLIES TO
- Microsoft Exchange 2000 Server Standard Edition
This article was previously published under Q328654
SYMPTOMS
If too many link state changes occur because of changes in network topology, the message transfer agent (MTA) process may generate non-delivery reports (NDRs) for some of the messages. The following warning messages may be logged:
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: server_name
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 the routing table for a possible incorrect routing configuration. (MTA DISP:ROUTER 16 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: server_name
Description:
A non-delivery report (reason code unable-to-transfer and diagnostic code unrecognised-OR-name) is being generated for message C=US;A= ;P=Company;L=OrginateServer-020208210308Z-521102. It was originally destined for C=US;A= ;P=Company;O=Site;DDA:SMTP=user(a)Company.net; (recipient number 1), and was 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: server_name
Description:
The MTA is unable to route a report for message C=US;A= ;P=Company;L=OrginateServer-020208210308Z-521102 to recipient DN:CN=Alias,CN=Name,OU=Site,O=Company -- C=US;A= ;P=Company;O=Site;S=SurName;G=GivenName;. MTA object at fault: 060009B3. Check the routing table for a possible incorrect routing configuration. (MTA DISP:ROUTER 16 40) (12)
This problem typically occurs on the bridgehead servers. Also, if you monitor the Private Bytes counter of the MTA process, the counter shows a memory leak, and memory use by the MTA process is very high (sometimes up to 2 gigabytes [GB]).
RESOLUTION
Cumulative Patch Information
To resolve this problem, obtain the March 2003 Exchange 2000 Server Post-Service Pack 3 (SP3) Rollup. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
813840 XGEN: March 2003 Exchange 2000 Server Post-Service Pack 3 Rollup
Hotfix Information
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Microsoft Exchange 2000 Server service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
Component: MTA
The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Version Size File name
------------------------------------------------
03-SEP-2002 6.0.6320.0 520,192 Reapi.dll
03-SEP-2002 6.0.6320.0 307,200 Resvc.dll
NOTE: Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 3 (SP3). For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
301378 How to Obtain the Latest Exchange 2000 Server Service Pack
STATUS
Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server.
MORE INFORMATION
Microsoft recommends that you run Exchange 2000 Server Service Pack 3 (SP3) because some of aspects of this problem are addressed in Exchange 2000 SP3.
For additional information about a similar problem, click the article number below to view the article in the Microsoft Knowledge Base:
320225 XCON: MTA Process Can Leak Memory Because of Excessive Rerouting
Additional query words: link state change routing exch2kp2w kbExchange2000preSP4marchbarFix XCON
Keywords: kbhotfixserver kbqfe kbbug kberrmsg kbexchange2000presp4fix kbfix kbqfe KB328654
