This article was previously published under Q256467
This article has been archived. It is offered "as is" and will no longer be updated.
The Exchange Server information store may not log application events, or the information store may stop responding with an access violation. This issue occurs only if the information store diagnostics Transport Delivering option is set to medium or higher and you receive a message that contains many recipients.
This issue can occur if the information store attempts to log an application event and submits more than 32 kilobytes (KB) of data to the Microsoft Windows NT ReportEvent() application programming interface (API). In Windows NT 4.0, if more than 32 KB of data is passed to this API, the API may stop responding and may cause unpredictable behavior such as a crash, or an inability to log subsequent events.Any attempt to submit more than 32 KB of data to the ReportEvent() API is an error, and the attempt to log the event does not work (which results in the absence of this diagnostic event).
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.
To work around this issue, change the Transport Delivering diagnostic option to a setting of minimum or less.
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.