XADM: The Information Store May Stop Responding When Freeing Non-Heap Memory

This article was previously published under Q310892
This article has been archived. It is offered "as is" and will no longer be updated.
The Exchange 2000 information store may stop responding with the following call stack:
ChildEBP RetAddr  Args to Child3ef7f504 62ff1155 3ef7f5ac 3ef7f5b4 1e2b97fc EXCHMEM!MpHeapValidateHeader+0x303ef7f51c 62ff1121 00e9f650 3ef7f5b4 00000000 EXCHMEM!MpHeapFree+0x253ef7f530 00717026 3ef7f5b4 219c0620 0000000a EXCHMEM!ExchMHeapFree+0xd53ef7f544 00716f50 00001000 00733fd1 61d326c0 store!FreeOmobjData+0xce3ef7f54c 00733fd1 61d326c0 219c0620 fffffc02 store!FreeOmobj+0xc3ef7f6a4 00730144 3a2b9fb0 3a2b07fc fffffc02 store!EcMTNDR+0x14c63ef7ff94 004eeed8 00000000 219c0620 3ef7ffec store!FStartTransferIn+0x8cb3ef7ffa8 006013be 00000000 00000000 77e8758a store!TI__Invoke+0xad3ef7ffb4 77e8758a 00fe3418 00000000 219c0620 store!DwOwnThreadTask+0x1d3ef7ffec 00000000 006013a1 00fe3418 00000000 KERNEL32!BaseThreadStart+0x52					
When the error code path is run, the code tries to free a string. This problem can occur if the string is allocated on the stack, but the free information store is trying to free from the heap; this causes the crash.
To resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
301378 XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server.

This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 2.

Article ID: 310892 - Last Review: 11/02/2013 16:52:00 - Revision: 2.0

  • kbnosurvey kbarchive kbbug kbexchange2000sp2fix kbfix KB310892