XADM: Heap Corruption in MAPI Causes MTA to Stop Responding (269588)
The information in this article applies to:
- Microsoft Exchange Server 5.5
This article was previously published under Q269588 SYMPTOMS
The message transfer agent (MTA) may stop responding (crash) with a call stack that is similar to the following:
0514efcc 77f640fc 04930000 40530000 0514eff8 NTDLL!RtlpFindAndCommitPages+0xde
0514f008 77f64830 04930000 000000b0 048b0588 NTDLL!RtlpExtendHeap+0x56
0514f0d0 6fff1921 04930000 00000001 000000a8 NTDLL!RtlAllocateHeap+0x1ae
0514f0f4 6fff1383 00000015 00000000 0000009e EXCHMEM!MpHeapAlloc+0x101
0514f104 6facfa8b 0000009e 6facfb25 048b0588 EXCHMEM!ExchMHeapAlloc+0x13
0514f10c 6facfb25 048b0588 00000000 0000009e MAPI32!LH_IntHeapAlloc+0xb
0514f11c 6fa960bf 048b0588 00000000 0000009e MAPI32!LH_ExtHeapAlloc+0x15
0514f138 6fa96118 00000001 048b0588 0514f16c MAPI32!MAPIAllocateBufferExt+0x2f
0514f14c 00593ce1 00000096 0514f16c 00000001 MAPI32!MAPIAllocateBuffer+0x28
0514f16c 00593ae3 063c7428 405904fc 00000000 EMSMTA!HrStrAToStrW+0x67
00000001 00000000 00000000 00000000 00000000 EMSMTA!HrTrackWriteLogA+0x187
CAUSE
This problem can occur because of a problem in the Mapi32.dll file.
RESOLUTIONA 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: 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: MTA
WORKAROUND
To work around this problem, disable message tracking on the affected servers, both for the information store and the MTA. You can do so on a site level by using the Exchange Server Administrator program, or on a for-each-server basis. For additional information, click the article number below
to view the article in the Microsoft Knowledge Base:
148963 XADM: Disabling Message Tracking For One or More Servers
STATUSMicrosoft has confirmed that this is a problem in Microsoft Exchange Server version 5.5.
| Modification Type: | Minor | Last Reviewed: | 10/6/2005 |
|---|
| Keywords: | kbbug kbExchange550preSP5fix kbExchange550sp4Fix kbfix kbQFE KB269588 |
|---|
|