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.
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
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:
Hotfix InformationA 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];CNTACTMSNote 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.
PrerequisitesThis hotfix requires Microsoft Exchange Server 5.5 Service Pack 4 (SP4).
Restart RequirementYou do not have to restart your computer after you apply this hotfix.
File InformationThe 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
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.
For additional information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base:
817903For 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:
(http://support.microsoft.com/kb/817903/ )XADM: New Naming Schema for Exchange Server Hotfix Packages
(http://support.microsoft.com/kb/824684/ )Description of the Standard Terminology That Is Used to Describe Microsoft Software Updates
Article ID: 821698 - Last Review: October 26, 2013 - Revision: 1.4