PRB: Transport Causes MAPI Spooler to Shutdown Unexpectedly
Article ID: 188653
Article Last Modified on 8/18/2005
APPLIES TO
- Microsoft Messaging Application Programming Interface
- Microsoft Outlook 97 Standard Edition
- Microsoft Exchange Client 5.5
- Microsoft Exchange Client 5.0
- Microsoft Exchange Client 4.0
- Microsoft Exchange Client 5.0
This article was previously published under Q188653
SYMPTOMS
A Message Transport may cause the MAPI Spooler (Mapisp32.exe) to shutdown
unexpectedly with an
Access Violation
error. If run in debug mode, you get
an exception indicating that you are attempting to allocate too much memory
as well as a Heap Corruption error message.
CAUSE
The message transport is not written with an implementation of the
XPLogon::InitializeStatusRow() method.
When XPLogon::InitializeStatusRow() is not implemented, MAPI expects to
have a tightly-coupled store and attempts to allocate space for it. The
count of bytes eventually fails and an access violation is generated,
causing the mapi spooler to shutdown.
REFERENCES
There is a sample transport available on the Microsoft Developer Network
Library named XPWDS.
"Inside Mapi", Irving De La Cruz and Les Thaler, Microsoft Press
Additional query words: kbMsg kbMAPI100 kbEDK500 kbEDK kbEDKAPI
Keywords: kbapi kbmsg kbprb KB188653