The Exchange Information Store service may crash after you enable tracing for the logon actions

This article has been archived. It is offered "as is" and will no longer be updated.
On an Exchange Server 2007 environment, you can trace logon processes by using the Microsoft Exchange Troubleshooting Assistant tool (Extra.exe) and the TagRPCIntfLogon trace tag of the Store component in the Set Trace Tags Manually option. When you do this, if a user who has the suitable permissions on other user’s mailbox opens another user’s mailbox in Outlook, the logon action will be logged in the trace log. However, the Exchange Information Store service may crash in certain scenarios. Additionally, the following event error messages are logged in the Application log on the Exchange server:

Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Faulting application store.exe, version <version number>, faulting module store.exe, version <version number>, fault address <address>.

Event Type: Error
Event Source: MSExchange Common
Event Category: General
Event ID: 4999
Watson report about to be sent to dw20.exe for process id: 1044, with parameters: E12N, c-rtl-AMD64, <version number>, store.exe, store.exe, e3de, c0000005, ea3d, <version number>. ErrorReportingEnabled: False.

Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9659
The Microsoft Exchange Information Store encountered an unexpected exception 0xC0000005 at address <address> while processing a request for user <user name>.

To resolve this problem, install Update Rollup 7 for Exchange 2007 Service Pack 1. For more information about Update Rollup 7 for Exchange Server 2007 Service Pack 1, see the following Exchange Help topic: For more information about how to obtain the latest Exchange service pack or update rollup, see the following Exchange Help topic:
When this issue occurs, the following call stack is generated:
Child-SP          RetAddr           Call Site00000000`11afdd90 00000001`4000e57f store!JTAB_BASE::EcRetrieveColumnByPtagid+0x37500000000`11afde30 00000001`4003d68e store!JTAB_BASE::EcRetrieveColumn+0x3f00000000`11afde90 00000001`4003ccb1 store!MINIMSG::EcGetNTSD+0x63300000000`11afdfd0 00000001`4003c670 store!OMSG::EcGetNTSD+0x1bf00000000`11afe080 00000001`4003f459 store!OMSG::EcConfig2+0x38b100000000`11afe330 00000001`4014e8f1 store!EcCreateOMSG2+0x26f00000000`11afe420 00000001`4014e72a store!EcCreateOMSG+0xa400000000`11afe4c0 00000001`4014e634 store!INCRMSGFXSND::EcConfigMsgToSend+0x1e000000000`11afe580 00000001`400b8f68 store!INCRMSGFXSND::EcSnd+0x42000000000`11afe5e0 00000001`400b8d2d store!FXSRCCTX::EcSnd+0x2800000000`11afe6c0 00000001`400b8e91 store!FXSRCCTX::EcGetBuffer+0xcd00000000`11afe740 00000001`400b9202 store!EcFXSrcGetBufferOp+0x10700000000`11afe7d0 00000001`400b947d store!EcFXSrcGetBuffer+0x7bd00000000`11afe870 00000001`4001dbbd store!EcRpc+0x313000000000`11aff070 00000001`4001d85a store!EcRpcExt+0x28d00000000`11aff190 00000001`4001d6e0 store!EcRpcExt2+0xe000000000`11aff2c0 000007ff`7fd69a75 store!EcDoRpcExt2+0x10c00000000`11aff380 000007ff`7fe96cc9 rpcrt4!Invoke+0x6500000000`11aff420 000007ff`7fe9758d rpcrt4!NdrStubCall2+0x54d00000000`11aff9e0 000007ff`7fd697b4 rpcrt4!NdrServerCall2+0x1d00000000`11affa10 000007ff`7fd6990d rpcrt4!DispatchToStubInCNoAvrf+0x1400000000`11affa40 000007ff`7fd69766 rpcrt4!RPC_INTERFACE::DispatchToStubWorker+0x50d00000000`11affbb0 000007ff`7fd48b65 rpcrt4!RPC_INTERFACE::DispatchToStub+0x2ec00000000`11affc30 000007ff`7fd497b9 rpcrt4!OSF_SCALL::DispatchHelper+0x2d300000000`11affcb0 000007ff`7fd49674 rpcrt4!OSF_SCALL::DispatchRPCCall+0x1ba00000000`11affce0 000007ff`7fd490c2 rpcrt4!OSF_SCALL::ProcessReceivedPDU+0x7f800000000`11affd50 000007ff`7fd46f8c rpcrt4!OSF_SCONNECTION::ProcessReceiveComplete+0x1d600000000`11affe00 000007ff`7fd47179 rpcrt4!LOADABLE_TRANSPORT::ProcessIOEvents+0x1e100000000`11affeb0 000007ff`7fd65996 rpcrt4!ProcessIOEventsWrapper+0x900000000`11affee0 000007ff`7fd65d51 rpcrt4!BaseCachedThreadRoutine+0xde00000000`11afff50 00000000`77d6b6da rpcrt4!ThreadStartRoutine+0x2100000000`11afff80 00000000`00000000 kernel32!BaseThreadStart+0x3a
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Article ID: 960349 - Last Review: 01/16/2015 03:25:19 - Revision: 1.1

  • Microsoft Exchange Server 2007 Service Pack 1
  • kbnosurvey kbarchive kbexpertiseadvanced kbqfe kbsurveynew kbhotfixrollup KB960349