XADM: Information Store Fails in EcCodePageConvertXRaw (198581)
The information in this article applies to:
- Microsoft Exchange Server 5.0
- Microsoft Exchange Server 5.5
This article was previously published under Q198581 SYMPTOMS
The information store fails (crashes) during a non-delivery report (NDR) to
an address that has invalid attributes.
CAUSE
This crash is caused by an NDR that is normally not seen. The reason for
the NDR is that invalid attributes of the Address are passed into the
information store for conversion to Unicode, Multibyte, or ASCII. The
actual return address was NULL.
Below is the stack trace of the crash.
FramePtr RetAddr Param1 Param2 Param3 Function Name
03ecf7b0 00414111 00000001 6fff1921 0040feb2
STORE!EcCodePageConvertXRaw+0x104
03ecf7dc 004e9286 03ecf830 000004e4 00000000
STORE!EcCodePageConvert+0x37
03ecf850 005ec646 000004e4 00000000 000004e4
STORE!EcORNameFromAddr+0x4c4
03ecf8c4 005f1c8d 000004b0 0146f6f0 000004b0 STORE!FEqAddr+0x277
03ecfb14 005f0e30 00000000 0146ba60 01469e28 STORE!EcDeliverNDR+0x984
03ecfc7c 00499aa2 01461298 010bcadc 03ecfdfc
STORE!EcDeliverReport+0x138c
03ecfdbc 004f1fba 10567b50 01461298 010bcadc
STORE!EcDeliverMessage+0x598
03ecffa0 004fb173 0134f598 77e1f632 03ecffec
STORE!FStartReceive+0x82a
03ecffb8 77f04f2c 00000000 0134f598 77e1f632
STORE!EcProcessTask+0x11d
0134f5a8 74ff516f 0fa70000 00000000 0000007c
KERNEL32!BaseThreadStart+0x51
RESOLUTIONExchange Server Version 5.0A 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 Exchange Server version 5.0 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 |
Store.exe | 5.0.1462.3 | Mdbmsg.dll | 5.0.1462.3 |
Exchange Server Version 5.5To resolve this problem, obtain the latest service pack for Exchange Server version 5.5. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
191014 XGEN: How to Obtain the Latest Exchange Server 5.5 Service Pack
The English version of this fix should have the following file attributes
or later:
Component: Information Store |
Gapi32.dll | 5.5.2527.0 | Mdbmsg.dll | 5.5.2527.0 | Store.exe | 5.5.2527.0 |
STATUSMicrosoft has confirmed that this is a problem in Microsoft Exchange Serverversions 5.0 and 5.5. This problem was first corrected in Exchange Server 5.5 Service Pack 3.
Modification Type: | Minor | Last Reviewed: | 10/7/2005 |
---|
Keywords: | kbHotfixServer kbQFE EXC55SP3Fix kbbug kbExchange500preSP3fix kbfix KB198581 |
---|
|