Knowledge Base

XCON: MTA Terminates Unexpectedly with Event ID 2050

Article ID: 152914

Article Last Modified on 10/28/2006

Microsoft Exchange Server 4.0 Service Pack 1
Microsoft Exchange Server 4.0 Service Pack 2

This article was previously published under Q152914

SYMPTOMS

Under certain circumstances The Microsoft Exchange Message Transfer Agent (MTA) may terminate unexpectedly with the following error message:

message NMI2050: Internal Processing Error, severity 16

(BASE XFER-IN(21) Proc 9) 06-27-96 02:03:05pm
Illegal put to element A48E6500 at offset 31081

CAUSE

This problem occurs when the MTA has received a corrupted or incorrectly encoded message from a remote MTA. For example, if the MTA receives a message, the actual content length of which is "x," but the encoded content length was "100x", the MTA will terminate unexpectedly with the Event ID 2050.

RESOLUTION

In order to resolve the problem, the corrupted or incorrectly encoded message must be removed from the remote MTA's queue, and the Exchange MTA must be restarted.

STATUS

Microsoft has confirmed that this is a problem in Microsoft Exchange Server version 4.0 Service Pack 1 (SP1) and Service Pack 2 (SP2).

Keywords: kbusage KB152914