XCON: MTA NDRs Outlook Recall Messages Because of P2 Conversion Failure (814553)



The information in this article applies to:

  • Microsoft Exchange Server 5.5

SYMPTOMS

When you recall an e-mail message that was sent over an X.400 connector, the Microsoft Exchange Message Transfer Agent (MTA) service may fail the P2 conversion process for that message. Because of this, the MTA logs an event 210 "Content Conversion Failure" error message in the Application Log file, and the MTA will then NDR the message. This symptom may occur if all the following conditions exist:
  • You connect two Exchange 5.5 Server sites by using an X.400 connector.
  • You click to select the following check boxes in the properties of the X.400 connector:

    Allow MS Exchange contents
    Remote Clients Support MAPI

RESOLUTION

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Exchange Server 5.5 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 usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. 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.

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         Time   Version         Size       File name
   -----------------------------------------------------------
   01-Aug-2001  17:02                     41,325  Dbserver.sch
   16-Sep-2002  15:49                     88,248  Dsadap.xv2
   16-Sep-2002  15:49                     33,049  Edi.xv2
   19-Feb-2003  20:13  5.5.2657.24     1,941,776  Emsmta.exe
   19-Feb-2003  20:11  5.5.2657.24        69,904  Ems_rid.dll
   13-Jun-2001  17:05                    133,435  Infoplog.cfg
   19-Feb-2003  20:11  5.5.2657.24        19,728  Maxapia.dll
   19-Feb-2003  20:11  5.5.2657.24        12,048  Maxapiv1.dll
   19-Feb-2003  20:15  5.5.2657.24       167,184  Mtacheck.exe
   19-Feb-2003  20:12  5.5.2657.24       743,696  Mtamsg.dll
   19-Feb-2003  20:12  5.5.2657.24        16,144  Mtaperf.dll
   19-Feb-2003  20:12  5.5.2657.24        16,656  Mtxapia.dll
   19-Feb-2003  20:12  5.5.2657.24        11,536  Mtxapiv1.dll
   13-Jun-2001  17:06                     50,789  P2.xv2
   17-Sep-2001  18:45                     14,002  P42.tpl
   16-Sep-2002  15:49                     41,222  P772.tpl
   16-Sep-2002  15:49                      9,028  P772.xv2
   29-Aug-2001  18:16                     23,350  Rdi.xv2
   19-Feb-2003  20:11  5.5.2657.24       322,320  X400om.dll
   19-Feb-2003  20:08  5.5.2657.24        40,208  X400omv1.dll
   16-Sep-2002  15:49                     31,276  X500dap.tpl

STATUS

Microsoft has confirmed that this is a problem in Microsoft Exchange Server 5.5.

Modification Type:MinorLast Reviewed:10/10/2005
Keywords:kbHotfixServer kbQFE kbenv kbprb kbExchange550preSP5fix kbQFE kbfix kbbug KB814553