XADM: Store.exe Stops Responding in EXOLEDB!CDestroyLogonCallbackHash__Uninitialize (284027)
The information in this article applies to:
- Microsoft Exchange 2000 Server
This article was previously published under Q284027 SYMPTOMS
The Exchange 2000 information store may not start, and Store.exe may generate a Dr. Watson error during shutdown. The User.dmp file contains the following call stack:
29d1f9bc 77f8ecf1 61881000 6177ddaf 61881088 ntdll!RtlpWaitForCriticalSection+0x8a
29d1f9c4 6177ddaf 61881088 00000000 00000000 ntdll!RtlEnterCriticalSection+0x46
29d1f9d8 6177b2c8 007e1218 007e1218 61760176 EXOLEDB!CDestroyLogonCallbackHash__Uninitialize+0x38
29d1f9e4 61760176 007e1218 007e1218 617600a2 EXOLEDB!COleDbModule__EcStop+0xe9
29d1f9f0 617600a2 007e1218 80070005 617600b8 EXOLEDB!EcStopOledbServer+0x1b
29d1f9fc 617600b8 007e1218 00000001 007e17d0 EXOLEDB!EcStopServer+0x16
29d1fa0c 0040662a 007e1218 00000000 00000000 EXOLEDB!EcInitializeServer+0x3b
29d1fe58 00405f0c 00000000 00000010 00405ce2 store!EcMainInit+0x8d6
29d1fe64 00405ce2 00000000 0013c0f8 29d1ffec store!EcMuckWithWindow+0x19
29d1ffa4 77dc95d3 00000001 0013c100 0012f844 store!ServiceMain+0x340
29d1ffb4 77e92ca8 0013c0f8 00000000 0012f844 ADVAPI32!ScSvcctrlThreadW+0xe
29d1ffc0 0012f844 0013c0f8 bffdd000 c0000005 KERNEL32!BaseThreadStart+0x52
CAUSE
This problem can occur if the information store does not load Oledb during initialization. When the information store service shuts down, Exchange 2000 enters a critical section that is not initialized. The information store stops responding when Exchange 2000 tries to free that critical section.
RESOLUTIONTo 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
STATUSMicrosoft 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.
| Modification Type: | Minor | Last Reviewed: | 6/5/2003 |
|---|
| Keywords: | kbbug kbExchange2000preSP1fix kbfix kbQFE KB284027 |
|---|
|