XADM: Insufficient Memory when CDO/MAPI Application Accesses a Message on Exchange Server

Article translations Article translations
Article ID: 241278 - View products that this article applies to.
This article was previously published under Q241278
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

Symptoms

A Messaging Application Programming Interface (MAPI) or Collaboration Data Objects (CDO) application may return an error of MAPI_E_NOT_ENOUGH_MEMORY (which is defined as E_OUTOFMEMORY = 0x8007000E) when attempting to perform MAPI or CDO operations against a particular message.

The user may see an error message similar to the following:
There is not enough memory available to perform the operation. [Microsoft Exchange Server Information Store - [E_OUTOFMEMORY(8007000E)]]

Cause

The Exchange Server information store can return a remote procedure call (RPC) response to the client's RPC request indicating that the buffer size required for the RPC data is greater than the maximum allowable buffer size (32 KB). The client handles this request to set up an "illegal" buffer size as a memory error.

Resolution

To resolve this problem, obtain the latest service pack for Exchange Server 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 following files are available for download from the Microsoft Download Center:
x86:
Collapse this imageExpand this image
Download
Download Q248838engi.exe now
Alpha:
Collapse this imageExpand this image
Download
Download Q248838enga.exe now
For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How to Obtain Microsoft Support Files from Online Services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file.

Status

Microsoft has confirmed that this is a problem in Microsoft Exchange Server version 5.5. This problem was first corrected in Exchange Server 5.5 Service Pack 4.

More information

Under certain boundary conditions, the Exchange Server information store can return an RPC response to the client's RPC request, which informs the client that the buffer the client had originally set up for the request is of insufficient size. The server's RPC response indicates this with the "ropBufferTooSmall" string; it also indicates how large the buffer needs to be. This, in itself, is not a issue for the client, as the client typically sets up an appropriately sized buffer for the response and makes the request again. This typically succeeds.

The issue occurs when the information store fails to properly account for all buffers overhead when it calculates the actual buffer size that is required. Thus, the information store indicates in the response that the buffer required is larger that the maximum RPC buffer size allowed. When this is the case, MAPI or CDO applications can report "insufficient memory" type of errors.

Properties

Article ID: 241278 - Last Review: November 2, 2013 - Revision: 5.0
Applies to
  • Microsoft Exchange Server 5.5 Standard Edition
Keywords: 
kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbexchange550presp4fix kbexchange550sp4fix kbfix kbgraphxlinkcritical KB241278

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com