Article ID: 232396
Article Last Modified on 10/28/2006
APPLIES TO
- Microsoft Exchange Server 5.5 Standard Edition
This article was previously published under Q232396
SYMPTOMS
When an outgoing X.400 message fails content conversion, it may be re-routed to another server in the site that has an X.400 connector with a suitable address space.
CAUSE
The logic behind this process is that another route may not require the same content conversion and so the message may get sent.
RESOLUTION
To resolve this problem, obtain the latest service pack for Exchange Server version 5.5. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
191014 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.2608.0 |
| Emsmta.exe | 5.5.2608.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.2608.0 |
| Mtamsg.dll | 5.5.2608.0 |
| P2.xv2 | N/A |
| X400om.dll | 5.5.2608.0 |
| X400omv1.dll | 5.5.2608.0 |
STATUS
Microsoft has confirmed that this is a problem in Microsoft Exchange Server version 5.5. This problem was first corrected in Exchange Server 5.5 Service Pack 3.
Keywords: kbbug kbfix kbqfe KB232396
