Microsoft KB Archive/926662
Article ID: 926662
Article Last Modified on 10/25/2007
- Microsoft Exchange Server 2003 Enterprise Edition
- Microsoft Exchange Server 2003 Standard Edition
When you use the Microsoft Exchange Event service on a server that is running Microsoft Exchange Server 2003, the Microsoft Exchange Event service stops responding.
This problem occurs because of a thread deadlock.
A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.
To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:
Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:
Microsoft Exchange Server 2003 Service Pack 2 (SP2) must be installed on the server before you apply this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
836993 How to obtain the latest service packs for Exchange Server 2003
You do not have to restart your computer after you apply this hotfix. However, the Microsoft Exchange Event service is automatically stopped and then restarted when you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
|File name||File version||File size||Date||Time||Platform|
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
When this problem occurs, the following call stack is generated.
Deadlocked threads: ChildEBP RetAddr 00aae604 7c822124 ntdll!KiFastSystemCallRet 00aae608 7c83970f ntdll!NtWaitForSingleObject+0xc 00aae644 7c839620 ntdll!RtlpWaitOnCriticalSection+0x19c 00aae664 61e4058c ntdll!RtlEnterCriticalSection+0xa8 00aae6d8 61e40e1a mapi32!HrCommonOpenStore+0x56 00aae758 0b3b12c2 mapi32!SESSOBJ_OpenMsgStore+0x56 WARNING: Stack unwind information not available. Following frames may be wrong. 00aae7a8 0b3b75a0 3rd Party Agent DLL 00aafa60 0b3b74b3 3rd Party Agent DLL 00aafa74 0b3b10e0 3rd Party Agent DLL 00aafaa0 00408a9a 3rd Party Agent DLL 00aafbe8 00409ca6 events!LaunchAgent+0x126 00aafc80 6171eff6 events!CMsgSink::SaveChanges+0xd5 00aafca0 617106a9 emsmdb32!IXMSGFXRCV::EcRcv+0x3f2 00aafcb4 6171181e emsmdb32!FXRCVCTX::EcRcv+0x11 00aafcc8 6171fbc2 emsmdb32!FXRCVMGR::EcDoClient+0x39 00aafcf8 6171fc8f emsmdb32!IXCHGSYNC::EcSynchronize+0xf2 00aafd18 00402638 emsmdb32!IXMSGSYNC::Synchronize+0x22 00aafd74 00402d7c events!EventHandlerSync+0xc9 ChildEBP RetAddr 0095fb18 7c822124 ntdll!KiFastSystemCallRet 0095fb1c 7c83970f ntdll!NtWaitForSingleObject+0xc 0095fb58 7c839620 ntdll!RtlpWaitOnCriticalSection+0x19c 0095fb78 61726c18 ntdll!RtlEnterCriticalSection+0xa8 0095fc24 61e41161 emsmdb32!RMSP_Logon+0x133 0095fc84 61e40e79 mapi32!HrIntDoOneClientLogon+0x91 0095fca0 61e40904 mapi32!HrIntClientStoreLogon+0x50 0095fd14 61e40e1a mapi32!HrCommonOpenStore+0x3ce 0095fd94 00407510 mapi32!SESSOBJ_OpenMsgStore+0x56 0095fdf0 00407941 events!CBindingManager::NewBoundFolder+0xb5 0095fef8 0040e79b events!CBindingManager::Notify+0x265 0095ff68 00409275 events!CMaintainence::hrWait+0x1a3 0095ffa4 77f79348 events!ServiceMain+0x2be 0095ffb8 77e66063 advapi32!ScSvcctrlThreadA+0x21 0095ffec 00000000 kernel32!BaseThreadStart+0x34
Additional query words: event hang
Keywords: kbexpertiseinter kbhotfixserver kbqfe KB926662