An Exchange Server 2003 server that hosts many Outlook client sessions may run out of paged pool memory

This article has been archived. It is offered "as is" and will no longer be updated.
A server that is running Microsoft Exchange Server 2003 may run out of Windows kernel paged pool memory. Additionally, you may experience the following symptoms:
  • Users experience slow or unresponsive performance.
  • Paged pool allocation failure events that are similar to the following are logged in the System log:

    Event ID: 2020
    Source: SRV
    Type: Error
    Description: The server was unable to allocate from the system paged pool because the pool was empty.

  • You may have to restart the Exchange server to resume typical performance levels.
This problem occurs when many Microsoft Outlook users are connected to the Exchange server.
This problem occurs when paged pool memory is exhausted because of too much memory being allocated to client access tokens.
After you apply this hotfix, the allocation of client tokens in Microsoft Exchange Server 2003 Service Pack 2 (SP2) is optimized. The number of allocated tokens is reduced by up to one-third.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.


You must install Exchange Server 2003 SP2 before you apply the hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
836993 How to obtain the latest service packs for Exchange Server 2003

Restart requirement

You do not have to restart the computer after you apply the hotfix. However, the Microsoft Exchange Information Store service and all dependent services will be restarted.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
File nameFile versionFile sizeDateTimePlatform
Store.exe6.5.7650.215,248,00006-Jan-20060 4:22x86
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about how to troubleshoot general memory issues on an Exchange Server 2003 server, view the "Ruling Out Memory-Bound Problems" section in the "Troubleshooting Exchange Server 2003 Performance" white paper. To obtain the "Troubleshooting Exchange Server 2003 Performance" white paper, visit the following Microsoft Web site: For more information about how to troubleshoot token memory usage and paged pool memory issues in Exchange, click the following article number to view the article in the Microsoft Knowledge Base:
912376 How to monitor and troubleshoot the use of paged pool memory in Exchange Server 2003 or in Exchange 2000 Server

Article ID: 912480 - Last Review: 01/16/2015 01:50:38 - Revision: 5.0

  • Microsoft Exchange Server 2003 Enterprise Edition
  • Microsoft Exchange Server 2003 Standard Edition
  • kbnosurvey kbarchive kbautohotfix kbhotfixserver kbqfe kbfix kbbug KB912480