PRB: Transport Causes MAPI Spooler to Shutdown Unexpectedly

ID: Q188653

The information in this article applies to:

Extended Messaging Application Programming Interface (MAPI), version 1.0
Microsoft Outlook 8.03
Microsoft Exchange Windows 95/98 client, versions 4.0, 5.0
Microsoft Exchange Windows NT client, versions 4.0, 5.0

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 kbEDK kbMsg kbGrpMsg
Version : WINDOWS:1.0,4.0,5.0,8.03
Platform : WINDOWS
Issue type : kbprb