Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

XADM: Microsoft Exchange Information Store Process Fails on Shutdown


View products that this article applies to.

This article was previously published under Q322225

↑ Back to the top


Symptoms

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=77e836d5
eip=77e836f0 esp=191eff74 ebp=191effb4 iopl=0         nv up ei pl nz na po nc
cs=001b  ss=0023  ds=0023  es=0023  fs=0038  gs=0000             efl=00000206

KERNEL32!InterlockedDecrement+a:
77e836f0 0fc101           xadd    [ecx],eax         ds:0023:00000384=????????

ChildEBP RetAddr  Args to Child 
191eff70 61bd11e9 00000384 00000001 075dd9d0 KERNEL32!InterlockedDecrement+0xa
191effb4 77e96523 07589f50 00000001 075dd9d0 MDBTASK!MdbTaskPoolThread+0x12d
191effec 00000000 61bd1174 07589f50 00000000 KERNEL32!BaseThreadStart+0x52
					

↑ Back to the top


Cause

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.

↑ Back to the top


Resolution

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

↑ Back to the top


Status

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.

↑ Back to the top


Keywords: KB322225, kbfix, kbexchange2000sp3fix, kbbug

↑ Back to the top

Article Info
Article ID : 322225
Revision : 4
Created on : 2/19/2007
Published on : 2/19/2007
Exists online : False
Views : 273