XADM: Information Store Crashes Because Text Property Is Missing Terminating Null Character

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


The Exchange 2000 information store may stop responding, and the following call stack may be generated:
18b6f85c 005e6075 store!MSGFXRCV__EcSetProps+0x2b3
18b6fa8c 005e617b store!PROPFXRCV__EcUpdateDst+0xe5
18b6fab4 005e43e4 store!PROPFXRCV__EcRcv+0x6b
18b6fac4 005e916c store!FXDSTCTX__EcRcv+0x14
18b6fae0 0058af10 store!FXDSTCTX__EcPutBuffer+0x8c
18b6fb04 0045b0a5 store!EcFXDstPutBufferOp+0x70
18b6fb44 0044dffe store!EcFXDstPutBuffer+0xb5
00000006 0000012b store!EcRpc+0x198e


This problem can occur if a text property on a message is missing the terminating null character.


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: Store.exe

Collapse this tableExpand this table
File nameVersion


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: 288701 - Last Review: October 23, 2013 - Revision: 1.5
  • Microsoft Exchange 2000 Server Standard Edition
kbnosurvey kbarchive kbbug kbexchange2000presp1fix kbfix kbqfe KB288701

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