Microsoft KB Archive/249153

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 13:51, 21 July 2020 by X010 (talk | contribs) (Text replacement - """ to """)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Knowledge Base

Article ID: 249153

Article Last Modified on 10/26/2006


  • Microsoft Exchange Server 5.5 Standard Edition
  • Microsoft Exchange Server 5.5 Service Pack 1
  • Microsoft Exchange Server 5.5 Service Pack 2
  • Microsoft Exchange Server 5.5 Service Pack 3

This article was previously published under Q249153


The Exchange Server message transfer agent (MTA) may stop while processing an incoming X.400 message. One of the following 9405 error messages may be logged in the Windows NT application event log:

Access violation (0xc0000005) at Address 0x4144dc reading from 0x3032376c. [BASE APPLICATION 28] (16)

Access violation (0xc0000005) at Address 0x77f7cc66 writing to 0x10. [BASE MAIN BASE 28] (16)

Access violation (0xc0000005) at Address 0x401eac reading from 0x30323766. [BASE SUBMIT 15] (16)

Access violation (0xc0000005) at Address 0x77f74767 writing to 0x3032376a. [BASE SUBMIT 15] (16)

Before the event 9405, an event 2245 may be logged:

ds_read failed with Problem DS_E_NO_SUCH_OBJECT.
Attribute: Directory Name:
[RD Server APPLICATION 27 114] (12)


The Exchange Server MTA receives a malformatted message from a foreign X.400 messaging system. The message in question contains one or more invalid characters in an X.400 P1 directory name, for example "{" or "}". These characters are not part of the T.61 character set which is used here. Also, the directory name field exceeds the maximum allowed length of 64 characters.


To resolve this problem, obtain the latest service pack for Exchange Server 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 only workaround is to configure the link to send messages in 1984 format, so the invalid directory names are removed before the message reaches Exchange Server.


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 4.


When a malformatted message arrives, the following event is written to the Windows NT application event log:

Event ID 2024
Unable to access the object manager (OM) object from the Microsoft Exchange MTA for MH_T_PER_RECIP_REPORTS.

Additional query words: Dr watson crash hang stop malfunction user.dmp drwtsn32

Keywords: kbbug kbexchange550presp4fix kbexchange550sp4fix kbfix kbqfe KB249153