Article ID: 306937
Article Last Modified on 2/20/2007
APPLIES TO
- Microsoft Exchange 2000 Server Standard Edition
This article was previously published under Q306937
SYMPTOMS
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:
CAUSE
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.
RESOLUTION
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Microsoft Exchange 2000 Server service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this fix should have the following file attributes or later:
Component: Information store
| File name | Version |
|---|---|
| Store.exe | 6.0.4720.68 |
| Jcb.dll | 6.0.4720.68 |
| Exoledb.dll | 6.0.4720.68 |
| Excdo.dll | 6.0.4720.68 |
| Davex.dll | 6.0.4720.68 |
| Mdbsz.dll | 6.0.4720.68 |
| Exprox.dll | 6.0.4720.68 |
NOTE: Because of file dependencies, this update requires Microsoft Exchange Server 2000 Service Pack 1.
STATUS
Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server.
Additional query words: exch2kp2w
Keywords: kbhotfixserver kbqfe kbbug kberrmsg kbexchange2000presp2fix kbfix kbqfe KB306937
