The information in this article applies to:
SYMPTOMSIn some cases, a third-party X.400 message transfer agent (MTA) may send an invalid message to Exchange Server. Depending on the amount of corruption, the following events may be written to the Windows NT Server application event log: Event ID: 200NOTE: Event ID 200 indicates a corrupted field in the X.400 P1 message header. You can use the PDU dump reference given in this event to identify the corrupted message in the Bf0.log log file. Event ID: 2124 Event ID: 2175After this, the Exchange Server MTA may run at a very high CPU time for a long time and occasionally it may not be possible to stop the Exchange Server MTA. RESOLUTIONTo resolve this problem, obtain the latest service pack for Exchange Server version 5.5. For additional information, please see the following article in the
Microsoft Knowledge Base: Q191014 XGEN: How to Obtain the Latest Exchange Server 5.5 Service PackThe English version of this fix should have the following file attributes or later: Component: Message Transfer Agent (MTA)
STATUSMicrosoft has confirmed this to be a problem in Microsoft Exchange Server version 5.5. This problem was first corrected in Exchange Server 5.5 Service Pack 3. Additional query words: hang stop kill
Keywords : exc55 EXC55SP3Fix |
Last Reviewed: September 28, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |