Article ID: 940307
Article Last Modified on 10/11/2007
APPLIES TO
- Microsoft Windows Server 2003, Standard Edition (32-bit x86)
- Microsoft Windows Server 2003, Web Edition
- Microsoft Windows Server 2003, Enterprise Edition
- Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
- Microsoft Windows Server 2003, Standard x64 Edition
- Microsoft Windows Server 2003, Enterprise x64 Edition
- Microsoft Windows Server 2003, Datacenter x64 Edition
- Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
- Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
SYMPTOMS
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.
CAUSE
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.
RESOLUTION
Hotfix information
A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows Server 2003 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
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:
889100 How to obtain the latest service pack for Windows Server 2003
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
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Mountmgr.sys | 5.2.3790.2979 | 46,592 | 20-Jul-2007 | 12:11 | x86 |
Windows Server 2003 with Service Pack 2, x86-based versions
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Mountmgr.sys | 5.2.3790.4121 | 46,592 | 20-Jul-2007 | 13:27 | x86 |
Windows Server 2003 with Service Pack 1, Itanium-based versions
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Mountmgr.sys | 5.2.3790.2979 | 155,648 | 20-Jul-2007 | 02:49 | IA-64 |
Windows Server 2003 with Service Pack 2, Itanium-based versions
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Mountmgr.sys | 5.2.3790.4121 | 155,648 | 20-Jul-2007 | 02:53 | IA-64 |
Windows Server 2003, x64-based versions
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Mountmgr.sys | 5.2.3790.2979 | 72,192 | 20-Jul-2007 | 02:49 | x64 |
Windows Server 2003 with Service Pack 2, x64-based versions
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Mountmgr.sys | 5.2.3790.4121 | 72,192 | 20-Jul-2007 | 02:53 | x64 |
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
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:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Additional query words: MntA NonPaged Pool Leak Mount Manager IOCTL_MOUNTMGR_QUERY_POINTS
Keywords: kbbug kbfix kbqfe kbpubtypekc kbexpertiseinter kbhotfixserver kbwinserv2003postsp2fix KB940307
