Article ID: 326374
Article Last Modified on 2/28/2007
APPLIES TO
- Microsoft Exchange 2000 Server Standard Edition
This article was previously published under Q326374
SYMPTOMS
The Microsoft Exchange 2000 Server information store process may unexpectedly stop responding, and an access violation may occur.
If the correct symbols are installed on the computer, the Dr. Watson log (Drwtsn32.log) or the corresponding User.dmp file may contain a call stack similar to the following:
ChildEBP RetAddr Args to Child
16e4f5bc 77f838c6 03e21000 005468af 03e21060 ntdll!RtlpWaitForCriticalSection+0x8a
16e4f5c4 005468af 03e21060 0c634e28 09db18b8 ntdll!RtlEnterCriticalSection+0x46
16e4f5e4 00628041 16e4f764 77e86779 00003a88 store!LOGON::DeleteMidFromLockedMid+0x16
16e4f608 00628240 16e4f684 00000000 00000000 store!EcUnlockMid+0x51
16e4f62c 00405a08 00000000 09cb4fd8 00000000 store!BlockOnRowFoundEvt+0x81
16e4f690 00416de3 00000000 16e4f764 00000001 store!EcCheckReslockAccess+0x34
16e4f6dc 004b28b1 16e4f75c 16e4f764 02000000 store!EcOpenMessageOp2+0xb5
16e4f714 004b2699 16e4f75c 16e4f764 02000000 store!EcOpenMessageOpX+0x42
16e4f7b0 00487997 00000000 000002c5 16e4f8f4 store!EcOpenMessage+0x211
16e4f8d8 00487152 16e4f900 000004f1 16e4f8f4 store!EcRpc+0x5ac
16e4f8f0 77d447d8 52b526a0 042c4298 00000021 store!EcDoRpc+0x60
16e4f914 77da2586 0048710d 16e4fab8 00000004 RPCRT4!Invoke+0x30
16e4fd10 77da31d1 00000000 00000000 16e4fdfc RPCRT4!NdrStubCall2+0x63d
16e4fd2c 77d44cee 16e4fdfc 0011d380 16e4fdfc RPCRT4!NdrServerCall2+0x17
16e4fd64 77d44bfb 004870fd 16e4fdfc 16e4fe40 RPCRT4!DispatchToStubInC+0x84
16e4fdbc 77d44b21 00000002 00000000 16e4fe40 RPCRT4!RPC_INTERFACE::DispatchToStubWorker+0x100
16e4fddc 77d49cb8 16e4fdfc 00000000 16e4fe40 RPCRT4!RPC_INTERFACE::DispatchToStub+0x5e
16e4fe44 77d49bac 00000000 52cbb288 4d79c678 RPCRT4!OSF_SCALL::DispatchHelper+0xa4
16e4fe58 77d499a5 00000000 00000002 00000001 RPCRT4!OSF_SCALL::DispatchRPCCall+0x115
16e4fe90 77d496cb 52cbb270 00000003 00000002 RPCRT4!OSF_SCALL::ProcessReceivedPDU+0x43
CAUSE
This problem may occur if a logon object that is contained in memory is incorrectly removed from an array of logon objects.
RESOLUTION
Cumulative Patch Information
To resolve this problem, obtain the March 2003 Exchange 2000 Server Post-Service Pack 3 (SP3) Rollup. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
813840 XGEN: March 2003 Exchange 2000 Server Post-Service Pack 3 Rollup
Hotfix Information
To resolve this problem, install the Microsoft Exchange 2000 Server Post-Service Pack 3 Messaging Database (MDB) patch. For additional information about how to obtain this update, click the article number below to view the article in the Microsoft Knowledge Base:
329882 XGEN: Post-Exchange 2000 Server Service Pack 3 Messaging Database Fixes That Are Available
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
Additional query words: kbExchange2000preSP4mdbFix kbExchange2000preSP4marchbarFix
Keywords: kbhotfixserver kbqfe kbbug kbexchange2000presp3fix kbexchange2000presp4fix kbexchange2000sp3fix kbfix kbqfe KB326374
