A Microsoft Windows Server 2003-based computer may stop responding if an application frequently uses the mount manager to query volume information

A Microsoft Windows Server 2003-based computer may stop responding if an application frequently uses the mount manager to query volume information.

For example, this problem is likely to occur when you frequently use backup software to perform Volume Shadow Copy Service (VSS)-based backups.

When this problem occurs, the following events may be logged in the System log.

Event ID 2020

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

Event ID 1055

Type: Error
Event ID: 1055
Source: ClusSvc
Date: Date
Time: Time
User: N/A
Computer: Computer
Details: Cluster File Share resource ResourceName has failed a status check. The error code is 1450.

This problem occurs because the mount manager leaks some paged pool memory.

VSS is a mount manager client. A mount manager client may call the mount manager to query mount points. If the call fails, the mount manager leaks some paged pool memory. Therefore, this problem may occur if you frequently use backup software.

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.

Prerequisites

To apply this hotfix, you must have Windows Server 2003 Service Pack 1 or Windows Server 2003 Service Pack 2 installed on the computer. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Restart requirement

You must restart the computer after you apply this hotfix.

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.

Windows Server 2003 with Service Pack 1, x86-based versions

Windows Server 2003 with Service Pack 2, x86-based versions

Windows Server 2003 with Service Pack 1, Itanium-based versions

Windows Server 2003 with Service Pack 2, Itanium-based versions

Windows Server 2003, x64-based versions

Windows Server 2003 with Service Pack 2, x64-based versions

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Currently, the mount manager performs all pool allocations by using the MntA tag. Therefore, all leaks that are related to the mount manager may appear to be similar.

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: