XADM: Information Store Stops Unexpectedly Writing to Message Tracking Log Because of NULL Address

This article was previously published under Q256315
This article has been archived. It is offered "as is" and will no longer be updated.
SYMPTOMS
During normal operation of the Exchange Server information store (Store.exe), if a non-delivery report (NDR) is returned that has a blank e-mail address and message tracking enabled, the Exchange Server information store service may stop unexpectedly with an access violation when it tries to write the message details to the tracking logs. If the correct Microsoft Windows NT and Exchange Server debug symbols are installed, the resulting Dr. Watson log may contain a stack dump that is similar to the following:
0232fc4c  00412074  STORE!CchStrlenW0232fc60  00600c15  STORE!CchStrlen+0x880232fd90  004fcef1  STORE!EcGenerateGWNDR+0xbc30232ffa0  004dfd21  STORE!FStartTransferOut+0xd00					
CAUSE
This issue can occur if the Exchange Server information store erroneously handled the NULL value for the NDR e-mail address when the Exchange Server information store attempted to write the message details to the tracking logs. This causes the Exchange Server information store to try to access invalid memory.
RESOLUTION
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.
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 4.
Properties

Article ID: 256315 - Last Review: 10/20/2013 18:02:17 - Revision: 4.1

  • Microsoft Exchange Server 5.5 Standard Edition
  • kbnosurvey kbarchive kbbug kbexchange550presp4fix kbexchange550sp4fix kbfix kbgraphxlinkcritical kbqfe KB256315
Feedback