XADM: Information Store Runs Out of Memory While Processing an NDR Message

This article was previously published under Q306937
This article has been archived. It is offered "as is" and will no longer be updated.
The Exchange 2000 information store may run out of memory while the information store is processing a non-delivery report (NDR) message. The following error message is logged in the Application event log:
Event Type: Error
Event Source: MSExchangeIS
Event Category: Content Engine
Event ID: 12800
User: N/A
Message processing failed because there is not enough available memory (8007000E-82000387).
This problem can occur if the message loops in the information store. Each time that the message loops, it is appended upon itself until the information store runs out of memory.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.The English version of this fix should have the following file attributes or later:

Component: Information store

File nameVersion

NOTE: Because of file dependencies, this update requires Microsoft Exchange Server 2000 Service Pack 1.
Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server.

Article ID: 306937 - Last Review: 10/24/2013 07:30:38 - Revision: 1.7

Microsoft Exchange 2000 Server Standard Edition

  • kbnosurvey kbarchive kbautohotfix kbhotfixserver kbqfe kbbug kberrmsg kbexchange2000presp2fix kbfix kbqfe KB306937