Microsoft KB Archive/940239

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

Article ID: 940239

Article Last Modified on 10/11/2007

-

APPLIES TO


 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)
 * Microsoft Windows Server 2003, Enterprise Edition
 * Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
 * Microsoft Windows Server 2003, Web Edition
 * Microsoft Windows Server 2003, Standard x64 Edition
 * Microsoft Windows Server 2003, Enterprise x64 Edition
 * Microsoft Windows Server 2003, Datacenter x64 Edition

-



SYMPTOMS
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:

out of memory

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  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.



CAUSE
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 now 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 Windows Server 2003 service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

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 1, Itanium-based versions


STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



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

824684Description of the standard terminology that is used to describe Microsoft software updates

Keywords: kbfix kbqfe kbpubtypekc kbexpertiseinter kbhotfixserver KB940239

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.