Article: Q232388
Product(s): Microsoft Exchange
Version(s): winnt:5.5
Operating System(s):
Keyword(s): exc55 EXC55SP3Fix
Last Modified: 30-SEP-1999
-------------------------------------------------------------------------------
The information in this article applies to:
- Microsoft Exchange Server, version 5.5
-------------------------------------------------------------------------------
SYMPTOMS
========
Exchange Server users might receive non-delivery reports (NDRs) with the
diagnostic "content-syntax-error." In the event log, the event ID 210 "Content
conversion error: Database server read failure" appears.
CAUSE
=====
This behavior occurs if a recipient has more than 32 bytes in the Telephone
Number field.
RESOLUTION
==========
To 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 Pack
The English version of this fix should have the following file attributes or
later:
Component: Message Transfer Agent (MTA)
+---------------------------+
| File name | Version |
+---------------------------+
| Dbserver.sch | N/A |
+---------------------------+
| Dcprods.cat | N/A |
+---------------------------+
| Ems_rid.dll | 5.5.2621.0 |
+---------------------------+
| Emsmta.exe | 5.5.2621.0 |
+---------------------------+
| Info4log.cfg | N/A |
+---------------------------+
| Infoblog.cfg | N/A |
+---------------------------+
| Infodlog.cfg | N/A |
+---------------------------+
| Infollog.cfg | N/A |
+---------------------------+
| Infoplog.cfg | N/A |
+---------------------------+
| Infotlog.cfg | N/A |
+---------------------------+
| Mtacheck.exe | 5.5.2621.0 |
+---------------------------+
| Mtamsg.dll | 5.5.2621.0 |
+---------------------------+
| P2.xv2 | N/A |
+---------------------------+
| X400om.dll | 5.5.2621.0 |
+---------------------------+
| X400omv1.dll | 5.5.2621.0 |
+---------------------------+
STATUS
======
Microsoft 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: NDR
======================================================================
Keywords : exc55 EXC55SP3Fix
Technology : kbExchangeSearch kbExchange550 kbZNotKeyword2
Version : winnt:5.5
Issue type : kbbug
Solution Type : kbfix
=============================================================================