The backup application stops responding when you perform a backup that uses a volume snapshot in Windows Server 2003 with SP1

When you use the backup utility in Microsoft Windows Server 2003 to perform a backup, the backup utility stops responding. Therefore, the backup fails. Additionally, if you have other scheduled backup jobs, these backup jobs may also fail.

When this problem occurs, an event that resembles the following appears in Event Viewer:

Event Type: Error
Event Source: VolSnap
Event Category: None
Event ID: 32
Description: The description for Event ID ( 32 ) in Source ( VolSnap ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event:
C:\...ck\tmp\computer.domain.com\L_2006-05-02-32.

This problem occurs if the backup uses a volume snapshot.

This problem occurs because of an issue in the Volsnap.sys file. This issue generates a deadlock condition. In the deadlock condition, the system I/O is suspended. A file deletion operation is waiting for the system I/O to resume.

Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

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 update, you must have Microsoft Windows Server 2003 Service Pack 1 (SP1) installed. For more information about how to obtain Windows Server 2003 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:

Restart information

You must restart the computer after you apply this update.

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, x86-based versions

Windows Server 2003, x64-based versions

Windows Server 2003, Itanium-based versions

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 2.

To start the Windows backup utility in Windows Server 2003, click Start, click Run, type ntbackup, and then click OK.

For more information about the terms that are used to describe software updates, click the following article number to view the article in the Microsoft Knowledge Base: