XADM: "Content Conversion Failed" Messages for Event ID 210 Are Logged and Non-Delivery Reports Are Generated

Article translations Article translations
Article ID: 821698 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

On This Page

SYMPTOMS

The Microsoft Exchange 5.5 Server Message Transfer Agent (MTA) may experience content conversion failures on certain e-mail messages. Event ID 210 messages that are similar to the following are logged in the application log of Event Viewer:

Event ID: 210
Source: MSExchangeMTA
Type: Warning
Description:
An internal MTA error occurred. Content conversion for message message failed.

When this event is logged, the e-mail messages do not reach their destination. Additionally, non-delivery reports (NDR) that are similar to the following are received by the sender of the e-mail messages:
The following recipient(s) could not be reached:

UserName on Date and Time
A syntax error was detected in the content of the message
The MTS-ID of the original message is: c=US;a=xyz;l=SERVER1-030403142356Z-6678
MSEXCH:MSExchangeMTA:Site:Server

CAUSE

This problem may occur when the messages contain Microsoft Database Format (MDBEF) encoding that is incorrectly formatted. The MDBEF encoding contains MAPI properties that do not belong to certain contexts. This problem may occur if either one of the following conditions is true:
  • The MDBEF encoding contains the PR_NORMALIZED_SUBJECT MAPI property in a recipient context.
  • The MDBEF encoding contains the PR_EMAIL_ADDRESS MAPI property in a non-recipient context.

RESOLUTION

Hotfix Information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/default.aspx?scid=fh;[LN];CNTACTMS
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.

Prerequisites

This hotfix requires Microsoft Exchange Server 5.5 Service Pack 4 (SP4).

Restart Requirement

You do not have to restart your computer after you apply this hotfix.

File Information

The English version of this hotfix 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
26-Jun-2003  20:49  5.5.2657.49     1,941,776  Emsmta.exe       
26-Jun-2003  20:47  5.5.2657.49        69,904  Ems_rid.dll      
13-Jun-2001  17:05                    133,435  Infoplog.cfg
26-Jun-2003  20:47  5.5.2657.49        19,728  Maxapia.dll      
26-Jun-2003  20:47  5.5.2657.49        12,048  Maxapiv1.dll     
26-Jun-2003  20:49  5.5.2657.49       167,184  Mtacheck.exe     
26-Jun-2003  20:47  5.5.2657.49       743,696  Mtamsg.dll       
26-Jun-2003  20:47  5.5.2657.49        16,144  Mtaperf.dll      
26-Jun-2003  20:47  5.5.2657.49        16,656  Mtxapia.dll      
26-Jun-2003  20:47  5.5.2657.49        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
26-Jun-2003  20:47  5.5.2657.49       322,320  X400om.dll       
26-Jun-2003  20:47  5.5.2657.49        40,208  X400omv1.dll     
16-Sep-2002  15:49                     31,276  X500dap.tpl

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.

MORE INFORMATION

For additional information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base:
817903 XADM: New Naming Schema for Exchange Server Hotfix Packages
For additional information about the terminology that is used to describe Microsoft product updates, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the Standard Terminology That Is Used to Describe Microsoft Software Updates

Properties

Article ID: 821698 - Last Review: October 26, 2013 - Revision: 1.4
APPLIES TO
  • Microsoft Exchange Server 5.5 Standard Edition
Keywords: 
kbnosurvey kbarchive kbhotfixserver kbqfe kbexchange550presp5fix kbbug kbfix kbqfe KB821698

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com