Microsoft KB Archive/276057

= XADM: Access Violation in Information Store =

Article ID: 276057

Article Last Modified on 10/26/2006

-

APPLIES TO


 * Microsoft Exchange Server 5.5 Service Pack 4

-



This article was previously published under Q276057





SYMPTOMS
The Information Store service in Exchange Server version 5.5 may experience an access violation and stop responding (crash) with the following call stack:

1180f87c 6fff1a40 bcd3d88c 6df2b4f0 00000000 KERNEL32!InterlockedCompareExchange+0xc 1180f89c 6fff13c4 01040588 6df2b4f8 00409444 EXCHMEM!MpHeapFree+0x50 1180f8a8 00409444 6df2b4f8 005d52ea 6df2b4f8 EXCHMEM!ExchMHeapFree+0x14 1180f8b0 005d52ea 6df2b4f8 00000002 00000000 store!operator delete+0xd 1180f8c0 005c8fc3 00000002 00000000 00000002 store!ROWDATABUFFER__EcConfig+0xb9 1180f908 00528a89 5e289708 00000002 000004e4 store!EcGetMailboxTableOp+0x58 1180f92c 77e11dc7 1180fd24 00000000 2cc6cd40 store!EcAdminGetMailboxTable20+0x39 1180f95c 77e56205 00528a50 1180fb50 00000008 RPCRT4!Invoke+0x28 1180f978 77e561d6 00528a50 1180fb50 00000008 RPCRT4!NdrCallServerManager+0x15 1180fc3c 77e55f3e 00000000 00000000 1180ff28 RPCRT4!NdrStubCall+0x292 1180fc54 77e113a4 1180ff28 0015d778 1180ff28 RPCRT4!NdrServerCall+0x19 1180fc90 77e111be 0040e9cd 1180ff28 1180fdd8 RPCRT4!DispatchToStubInC+0x33 1180fce4 77e11403 1180ff28 00000000 1180fdd8 RPCRT4!RPC_INTERFACE__DispatchToStubWorker+0xb0 1180fd04 77e11903 1180ff28 00000000 1180fdd8 RPCRT4!RPC_INTERFACE__DispatchToStub+0x41 1180fddc 77e15af1 001392b8 1180fe10 1180ff28 RPCRT4!WMSG_SASSOCIATION__DealWithRequestMessage+0x182 1180ff90 77e15a1d 77e16125 00132d78 1180ffec RPCRT4!WMSG_ADDRESS__ReceiveLotsaCalls+0xd1 1180ff94 77e16125 00132d78 1180ffec 00000020 RPCRT4!RecvLotsaCallsWrapper+0x9 1180ffac 77e160bb 00152680 00000020 77f04ede RPCRT4!BaseCachedThreadRoutine+0x50 1180ffb8 77f04ede 001526a8 00000020 00000020 RPCRT4!ThreadStartRoutine+0x17 1180ffec 00000000 77e160a4 001526a8 00000000 KERNEL32!BaseThreadStart+0x51



CAUSE
This problem can occur if a variable is deleted twice. The second attempt results in the crash because the variable is no longer pointing to the valid data.



RESOLUTION
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Microsoft Exchange Server version 5.5 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix should have the following file attributes or later:

Component: Information Store



STATUS
Microsoft has confirmed that this is a problem in Microsoft Exchange Server version 5.5.

Keywords: kbhotfixserver kbqfe kbbug kbexchange550presp4fix kbexchange550presp5fix kbfix kbqfe KB276057

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.