XFOR: MSMI Terminating with Memory Access Violation, Event ID 23Last reviewed: September 11, 1997Article ID: Q149387 |
The information in this article applies to:
SYMPTOMSThe MS Mail Connector Interchange (MSMI) may terminate unexpectedly with the following events reported to the application log:
Event ID: 2380 Source: MSExchangeMSMI Description: A memory access violation has occurred that prevents further processing of a message. The access violation that occurred is an attempt to read from 0x480df78. Please refer to the immediately following event(s) logged by MS Mail Connector Interchange for more information on the message that could not be processed. (Exception address: 0x4496c2.)NOTE: The exception addresses above are examples; they will not match exactly every time.
CAUSEThe MSMI is freeing a block of heap memory before the actual process is done with it. When the process tries to access this freed area of memory, an access violation occurs.
STATUSMicrosoft has confirmed this to be a problem in Microsoft Exchange Server version 4.0. A supported fix to this problem is in development, but has not been fully regression-tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information on the availability of this fix. Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 5.0. This problem was corrected in the latest Microsoft Exchange 5.0 Server U.S. Service Pack. For information on obtaining the service pack, query on the following word in the Microsoft Knowledge Base (without the spaces):
S E R V P A C K |
Additional query words: heap corruption crash
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |