Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

The backup process may fail and a time-out error may occur in Volume Shadow Copy Service writers


View products that this article applies to.

Symptoms

Volume Shadow Copy Service (VSS) writers may time out during the backup process and cause the backup to fail. Additionally, you may find the following error message as the status of the backup process:
FAILED_AT_FREEZE (0x800423f2 - VSS_E_WRITERERROR_TIMEOUT)

↑ Back to the top


Cause

During snapshot creation, the freeze event suspends all program write activity for data consistency. For example, an SQL database must be in freeze mode for snapshot creation. The thaw event releases the program after successful snapshot creation. The snapshot creation process takes less than 60 seconds.

When the freeze event is called, a worker thread is created to issue a time-out after 60 seconds. If the thaw event is not called within 60 seconds, the worker thread issues a time-out.

This problem occurs if the thaw event is called before the worker thread is started. The worker thread issues a time-out after the thaw event is called and causes the VSS writer to fail.

↑ Back to the top


Resolution

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:
889100 How to obtain the latest service pack for Windows Server 2003

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

This hotfix requires Windows Server 2003 Service Pack 1 (SP1).

Restart requirement

You must restart your 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, Itanium-based versions
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Eventcls.dll5.2.3790.264182,43218-Feb-200604:03IA-64SP1SP1QFE
Ftdisk.sys5.2.3790.2641499,20018-Feb-200604:03IA-64SP1SP1QFE
Partmgr.sys5.2.3790.264183,45618-Feb-200604:03IA-64SP1SP1QFE
Volsnap.sys5.2.3790.2641476,67218-Feb-200604:03IA-64SP1SP1QFE
Vssui.dll5.2.3790.2641408,06418-Feb-200604:03IA-64SP1SP1QFE
Vss_ps.dll5.2.3790.264131,23218-Feb-200604:03IA-64SP1SP1QFE
Swprv.dll5.2.3790.2641832,51218-Feb-200604:03IA-64SP1SP1QFE
Vssadmin.exe5.2.3790.2641314,36818-Feb-200604:03IA-64SP1SP1QFE
Vssapi.dll5.2.3790.26411,643,52018-Feb-200604:03IA-64SP1SP1QFE
Vssvc.exe5.2.3790.26412,589,69618-Feb-200604:03IA-64SP1SP1QFE
Swprv.dll5.2.3790.2641832,51218-Feb-200604:03IA-64SP1SP1QFE
Vssadmin.exe5.2.3790.2641314,36818-Feb-200604:03IA-64SP1SP1QFE
Vssapi.dll5.2.3790.26411,643,52018-Feb-200604:03IA-64SP1SP1QFE
Vssvc.exe5.2.3790.26412,589,69618-Feb-200604:03IA-64SP1SP1QFE
Wvssapi.dll5.2.3790.2641561,66418-Feb-200604:03x86SP1WOW
Wvss_ps.dll5.2.3790.264119,45618-Feb-200604:03x86SP1WOW
Windows Server 2003, x64-based versions
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Eventcls.dll5.2.3790.264146,08018-Feb-200604:03x64SP1SP1QFE
Ftdisk.sys5.2.3790.2641240,12818-Feb-200604:03x64SP1SP1QFE
Partmgr.sys5.2.3790.264145,05618-Feb-200604:03x64SP1SP1QFE
Volsnap.sys5.2.3790.2641288,76818-Feb-200604:03x64SP1SP1QFE
Vssui.dll5.2.3790.2641233,47218-Feb-200604:03x64SP1SP1QFE
Vss_ps.dll5.2.3790.264125,60018-Feb-200604:03x64SP1SP1QFE
Swprv.dll5.2.3790.2641656,38418-Feb-200604:03x64SP1SP1QFE
Vssadmin.exe5.2.3790.2641245,24818-Feb-200604:03x64SP1SP1QFE
Vssapi.dll5.2.3790.26411,320,96018-Feb-200604:03x64SP1SP1QFE
Vssvc.exe5.2.3790.26412,061,82418-Feb-200604:03x64SP1SP1QFE
Swprv.dll5.2.3790.2641656,38418-Feb-200604:03x64SP1SP1QFE
Vssadmin.exe5.2.3790.2641245,24818-Feb-200604:03x64SP1SP1QFE
Vssapi.dll5.2.3790.26411,320,96018-Feb-200604:03x64SP1SP1QFE
Vssvc.exe5.2.3790.26412,061,82418-Feb-200604:03x64SP1SP1QFE
Swprv.dll5.2.3790.2641656,38418-Feb-200604:03x64SP1SP1QFE
Vssadmin.exe5.2.3790.2641245,24818-Feb-200604:03x64SP1SP1QFE
Vssapi.dll5.2.3790.26411,320,96018-Feb-200604:03x64SP1SP1QFE
Vssvc.exe5.2.3790.26412,061,82418-Feb-200604:03x64SP1SP1QFE
Swprv.dll5.2.3790.2641656,38418-Feb-200604:03x64SP1SP1QFE
Vssadmin.exe5.2.3790.2641245,24818-Feb-200604:03x64SP1SP1QFE
Vssapi.dll5.2.3790.26411,320,96018-Feb-200604:03x64SP1SP1QFE
Vssvc.exe5.2.3790.26412,061,82418-Feb-200604:03x64SP1SP1QFE
Wvssapi.dll5.2.3790.2641561,66418-Feb-200604:03x86SP1WOW
Wvss_ps.dll5.2.3790.264119,45618-Feb-200604:03x86SP1WOW
Windows Server 2003, x86-based versions
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Eventcls.dll5.2.3790.264131,23218-Feb-200604:24x86SP1SP1QFE
Ftdisk.sys5.2.3790.2641137,21618-Feb-200602:07x86SP1SP1QFE
Partmgr.sys5.2.3790.264125,08818-Feb-200602:32x86SP1SP1QFE
Swprv.dll5.2.3790.2641275,96818-Feb-200604:24x86SP1SP1QFE
Volsnap.sys5.2.3790.2641153,08818-Feb-200602:08x86SP1SP1QFE
Vssadmin.exe5.2.3790.2641133,63218-Feb-200602:08x86SP1SP1QFE
Vssapi.dll5.2.3790.2641561,66418-Feb-200604:24x86SP1SP1QFE
Vssui.dll5.2.3790.2641144,38418-Feb-200604:24x86SP1SP1QFE
Vssvc.exe5.2.3790.2641836,09618-Feb-200602:08x86SP1SP1QFE
Vss_ps.dll5.2.3790.264119,45618-Feb-200604:24x86SP1SP1QFE

↑ Back to the top


Status

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

↑ Back to the top


More information

For more information about the standard terminology that is used to describe Microsoft software updates, 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

↑ Back to the top


Keywords: kbautohotfix, kbwinserv2003sp2fix, kbbug, kbfix, kbqfe, KB915331

↑ Back to the top

Article Info
Article ID : 915331
Revision : 3
Created on : 10/9/2011
Published on : 10/9/2011
Exists online : False
Views : 326