This article was previously published under Q322225
This article has been archived. It is offered "as is" and will no longer be updated.
The information store stops unexpectedly during a service shutdown. If a Drwtsn32.log file is produced, you may see an entry similar to the following:
*----> State Dump for Thread Id 0x2f8 <----*eax=ffffffff ebx=77e836e6 ecx=00000384 edx=ffffffff esi=61bd3014 edi=77e836d5eip=77e836f0 esp=191eff74 ebp=191effb4 iopl=0 nv up ei pl nz na po nccs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000206KERNEL32!InterlockedDecrement+a:77e836f0 0fc101 xadd [ecx],eax ds:0023:00000384=????????ChildEBP RetAddr Args to Child 191eff70 61bd11e9 00000384 00000001 075dd9d0 KERNEL32!InterlockedDecrement+0xa191effb4 77e96523 07589f50 00000001 075dd9d0 MDBTASK!MdbTaskPoolThread+0x12d191effec 00000000 61bd1174 07589f50 00000000 KERNEL32!BaseThreadStart+0x52
A region of virtual memory that is used for performance monitor data is freed before the store task threads have ended. When the store task threads try to decrement a performance monitor counter in this region of virtual memory, a failure occurs.
This condition is rarely seen because the thread that controls the virtual memory region usually waits long enough for all the task threads to shut down before they release the memory section.
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 3.