XADM: Information Store Stops Responding When the Routing Engine Is Started

Article translations Article translations
Article ID: 278306 - View products that this article applies to.
This article was previously published under Q278306
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all


An Exchange 2000 Server computer's information store may stop responding when the routing engine starts.

The call stack is displayed as follows:
FramePtr          RetAddr           Param1           Param2           Param3           Function Name 
000000001163fd34  0000000062ff189f  0000000002bd8350 0000000002bd8358 0000000000000003 EXCHMEM!MpHeapValidateHeader+0x16(0x02BD8350)

000000001163fd4c  0000000062ff186b  00000000015df670 0000000002bd8358 000000000000004f EXCHMEM!MpHeapFree+0x25(0x015DF670, 0x02BD8358)

000000001163fd60  0000000000553c25  0000000002bd8358 0000000062dd13b0 000000000000004c EXCHMEM!ExchMHeapFree+0x29(0x02BD8358)

000000001163fef8  000000000040d964  000000000000004c 000000006102d592 0000000000000002 STORE!EcSetAddressTypes+0x1462ae(0x02BD8350, 0x00000000)


This problem can occur because when the routing engine starts, the routing engine passes all the address space types that are configured to the information store. When an address type of MSA (defined for AppleTalk Connector) is passed with a blank address space, the information store runs erroneous code.


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 the Microsoft Knowledge Base:
301378 XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
The English version of this fix should have the following file attributes or later:

Component: information store

Collapse this tableExpand this table
File nameVersion


To work around this problem, change the address for address type MSA from blank to an asterisk (*).


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 1.


Article ID: 278306 - Last Review: October 21, 2013 - Revision: 1.4
  • Microsoft Exchange 2000 Server Standard Edition
kbnosurvey kbarchive kbbug kbfix kbqfe kbhotfixserver KB278306

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com