VSS cannot create a volume snapshot even when VSS has sufficient memory space in Windows Server 2003

On a computer that is running Windows Server 2003, Volume Shadow Copy Service (VSS) cannot create a volume snapshot. Instead, you receive the following error message:This problem occurs even when VSS has sufficient memory space to create the volume snapshot.

Note System Center Data Protection Manager (DPM) depends heavily on VSS snapshots. The issue makes DPM unreliable.

When this problem occurs, the following event is logged in the Application log:

Event Type: Error
Event Source: VolSnap
Event ID: 21
Description:
The flush and hold operation for volume volume_name was aborted because of low available system memory.

This problem usually occurs if either of the following conditions is true:

• The system can allocate sufficient memory space for the VSS service. However, the available memory space is low.
• VSS obtains sufficient memory space when Memory Manager trims other processes.

This problem occurs because VSS incorrectly detects low-memory conditions. Low-memory conditions are based on the LowMemoryCondition event. If the LowMemoryCondition event is signed, VSS denies the volume snapshot action.

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

You must have Windows Server 2003 Service Pack 1 or Service Pack 2 installed to apply this hotfix.

Restart requirement

You have to 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 2, x86-based versions

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

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

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

Windows Server 2003, x64-based versions

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

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

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