Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

XADM: Information Store Does Not Respond to Remote Procedure Call Requests


View products that this article applies to.

This article was previously published under Q322124

↑ Back to the top


Symptoms

The information store can cause undue memory pressure to a system that has a large number of users. This causes performance issues for Messaging Application Program Interface (MAPI) and non-MAPI users. In extreme cases, the information store may not respond to remote procedure call (RPC) requests.

↑ Back to the top


Cause

When a message has attachments, a subobject is created on the message object for each attachment. The system allocates memory for each attachment subobject. When you have messages that have many attachments, the information store may erroneously keep memory allocated for these subobjects even when the objects are no longer needed and can be destroyed. System memory is not freed up if these subobjects are not destroyed.

↑ Back to the top


Resolution

To resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
301378 XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
The English version of this fix should have the following file attributes or later:

Component: Information Store
File nameVersion
Store.exe6.0.5770.97
Davex.dll6.0.5770.97
Dsaccess.dll6.0.5770.97
Dscmsg.dll6.0.5770.97
Excdo.dll6.0.5770.97
Exmgmt.exe6.0.5770.97
Exoledb.dll6.0.5770.97
Exprox.dll6.0.5770.97
Exres.dll6.0.5770.97
Exsp.dll6.0.5770.97
Exwmi.dll6.0.5770.97
Jcb.dll6.0.5770.97
Mad.exe6.0.5770.97
Mdbmsg.dll6.0.5770.97
Mdbsz.dll6.0.5770.97
Phatcat.dll6.0.5770.97


↑ Back to the top


Status

Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 3.

↑ Back to the top


Keywords: KB322124, kbfix, kbexchange2000sp3fix, kbexchange2000presp3fix, kbbug, kbqfe, kbhotfixserver

↑ Back to the top

Article Info
Article ID : 322124
Revision : 5
Created on : 2/20/2007
Published on : 2/20/2007
Exists online : False
Views : 292