XADM: Store.exe Causes an Access Violation When IMAIL Checks the Address Type

This article was previously published under Q310080
This article has been archived. It is offered "as is" and will no longer be updated.
The information store (Store.exe) may stop responding. If Dr. Watson is enabled and symbols are installed, the stack of the failing thread is similar to the following:
ChildEBP RetAddr  Args to Child              2fe7da74 77e58f56 000b4ac0 00000000 11aefff8 KERNEL32!NlsAnsiToUnicode+0x232fe7dcbc 77e5901a 00000411 40000001 11aefff8 KERNEL32!CompareStringA+0x17b2fe7dce4 004acf35 11aefff8 007f5678 00000000 KERNEL32!lstrcmpiA+0x212fe7dd08 004994f8 00000004 116d4ff8 11b32fd8 store!CINETconv__HrEmitAddress+0x372fe7dd44 00499350 00000004 1170eb50 00000000 store!CINETconv__HrEmitRecipients+0x1772fe7dd5c 004972a6 1170eb50 117c0460 00000005 store!CmcvtrHdrTo__HrBuildHdrValue+0x3a2fe7ddcc 00496ebb 0000d1ff 00000001 00000000 store!CINETconv__hrEmitHeaders+0x19e2fe7ddec 00496d7c 00072a86 116c0960 00000000 store!CConvertMessage__HrConvertHeadersToMIME+0x1512fe7de04 00496b96 116c0960 116c0960 00000000 store!CConvertMessage__HrConvertToMIME+0x2d2fe7de24 00492bb4 80000000 80000007 11617a60 store!CMdbConverter__HrConvert+0x6f2fe7de40 004abccd 80000007 11617a60 00000000 store!CMdbConverter__HrEnsureMime+0x252fe7de54 004abc71 11617a88 11617a60 00000000 store!CMdbConverter__HrGetBodyStructure+0x2d2fe7de68 004abbcf 00000000 1170bac8 00000000 store!CIMailUrlMessage__HrGetBodyStructure+0x112fe7de7c 004aba53 00000000 00000000 00000000 store!CIMailUrlMessage__HrInitialize+0x2e2fe7dea0 004abda9 1170bac8 00000000 00000000 store!CIMailConvert__HrOpenUrl+0x13f2fe7ded0 0041d7e3 11b47838 00000000 00000000 store!OURL__EcConfig+0x5b2fe7df18 61966550 2fe7e02c 2fe7e024 00120889 store!EcOpenMessageOp2+0x2542fe7df58 619664d0 00000bd3 2fe7e02c 2fe7e024 EXOLEDB!CStoreLogon__ScOpenMessage+0x7d2fe7df7c 6196afbc 00000bd3 2fe7e02c 2fe7e024 EXOLEDB!CAutoLogon__ScOpenMessage+0x302fe7dfc4 6196b85e 2fe7dfe0 ffffffff 00000000 EXOLEDB!CGetRequest__ScOpenObjectHsot+0xdf					
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 2000 Server 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: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

File nameVersion

NOTE: Because of file dependencies, this update requires Microsoft Exchange Server 2000 Service Pack 1.
Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server.

Article ID: 310080 - Last Review: 10/24/2013 08:02:16 - Revision: 1.5

Microsoft Exchange 2000 Server Standard Edition

  • kbnosurvey kbarchive kbbug kbfix KB310080
ERROR: at System.Diagnostics.Process.Kill() at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)