XADM: Information Store Access Violation with Long One-Off Address Entries

This article was previously published under Q263457
This article has been archived. It is offered "as is" and will no longer be updated.
During normal operation, the Exchange Server information store service may cause an access violation (Dr. Watson) when the information store attempts to process an outbound message that contains a X.400 address that is greater than 1,024 characters. The Drwatson.log file may contain a call stack similar to the following if symbols are properly installed:
ChildEBP RetAddr  0112fa04 004c003d store!EcORNameFromSzX400+0x3410112fa6c 004c003d store!EcMDBEFFromPtag+0xc7 0112fad4 004c003d store!EcMDBEFFromPtag+0xc70112fb3c 004c003d store!EcMDBEFFromPtag+0xc70112fba4 004c003d store!EcMDBEFFromPtag+0xc70112fc0c 004c003d store!EcMDBEFFromPtag+0xc70112fc74 004c003d store!EcMDBEFFromPtag+0xc70112fcdc 004c003d store!EcMDBEFFromPtag+0xc70112fd44 004c003d store!EcMDBEFFromPtag+0xc70112fdac 004c003d store!EcMDBEFFromPtag+0xc70112fe14 004c003d store!EcMDBEFFromPtag+0xc70112fe7c 004c003d store!EcMDBEFFromPtag+0xc70112fee4 004c003d store!EcMDBEFFromPtag+0xc70112ffb4 004c003d store!EcMDBEFFromPtag+0xc7					
This issue can occur because no check is made to determine whether an X.400 address is longer than 1,024 characters. When an X.400 address is longer than 1,024 characters, stack corruption occurs and causes the access violation.
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 theMicrosoft Knowledge Base:
191914 XGEN: How to Obtain the Latest Exchange Server 5.5 Service Pack
The following files are available for download from the MicrosoftDownload Center:
For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How to Obtain Microsoft Support Files from Online Services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file.
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.

Article ID: 263457 - Last Review: 10/20/2013 20:49:51 - Revision: 4.2

Microsoft Exchange Server 5.5 Standard Edition

  • kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbexchange550presp4fix kbexchange550sp4fix kbfix kbgraphxlinkcritical kbqfe KB263457