Microsoft KB Archive/904418

= FIX: Event ID 20 &quot;Volume Shadow Copy Service error&quot; is logged when you back up the System State on a Windows Server 2003 x64 Edition-based computer that is running SQL Server 2000 =

Article ID: 904418

Article Last Modified on 10/11/2006

-

APPLIES TO

 Microsoft SQL Server 2000 Standard Edition Microsoft SQL Server 2000 Enterprise Edition Microsoft SQL Server 2000 Developer Edition, when used with:  Microsoft Windows Server 2003, Datacenter x64 Edition

 Microsoft Windows Server 2003, Enterprise x64 Edition 

-

<div class="notice_section">

Bug #: 474047 (SQL Server 8.0)

<div class="notice_section">

''Microsoft distributes Microsoft SQL Server 2000 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2000 fix release.''

<div class="summary_section">

SUMMARY
This article describes the following about this hotfix release:
 * The issues that are fixed by this hotfix package
 * The prerequisites for installing the hotfix package
 * Whether you must restart the computer after you apply the hotfix package
 * Whether the hotfix package is replaced by any other hotfix package
 * Whether you must make any registry changes
 * The files that are contained in the hotfix package

<div class="symptoms_section">

SYMPTOMS
When you perform a System State backup operation on a Microsoft Windows Server 2003-based computer that is running Microsoft SQL Server 2000, both of the following events are logged:   Event ID 20 Event Type: Error

Event Source: VSS

Event Category: None

Event ID: 20

Date:

Time:

User: N/A

Computer:

Description: Volume Shadow Copy Service error: A critical component required by the Volume Shadow Copy Service is not registered. This might happen if an error occurred during Windows setup or during installation of a Shadow Copy provider. The error returned from CoCreateInstance on class with CLSID {40700425-0080-11d2-851f-00c04fc21759} and Name MSSQL_ClientVirtualDeviceSet is [0x80040154]. </li>  Event ID 6008 Event Type: Error

Event Source: VSS

Event Category: None

Event ID: 6008

Date:

Time:

User: N/A

Computer:

Description: Sqllib error: Failed to create VDS object. hr = 0x80040154. </li></ul>

For a list of all publicly released SQL Server 2000 Post-Service Pack 3a hotfixes, see the following article in the Microsoft Knowledge Base:

810185 SQL Server 2000 hotfix update for SQL Server 2000 Service Pack 3 and 3a

<div class="cause_section">

CAUSE
This problem occurs because the SQL Server 2000 Virtual Device Interface (Sqlvdi.dll) is a 32-bit DLL. The 64-bit Volume Shadow Copy Service (VSS) writer that is included with the x64 edition of Windows Server 2003 requires an x64 edition of Sqlvdi.dll to work correctly.

<div class="resolution_section">

RESOLUTION
To resolve this problem, download the hotfix that is mentioned in the following Microsoft Knowledge Base article:

913100 FIX: The MSDE writer is not included when you try to use the Vssadmin.exe tool to list subscribed volume shadow copy writers

<div class="resolution_section">

Hotfix information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it 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 Microsoft SQL Server 2000 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

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

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
Microsoft SQL Server 2000 Service Pack 4 (SP4)

For more information about how to obtain SQL Server 2000 Service Pack 4, click the following article number to view the article in the Microsoft Knowledge Base:

290211 How to obtain the latest SQL Server 2000 service pack

Restart information
You do not have to restart the computer after you apply this hotfix.

Registry information
You do not have to change the registry after you apply this hotfix.

Hotfix file information
This hotfix contains only those files that are required to correct the issues that this article discusses. This hotfix may not contain of all the files that you must have to fully update a product to the latest build.

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 tool in Control Panel.

Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.

<div class="resolution_section">

Hotfix installation information
Currently, no automatic hotfix installer is available for this hotfix. Therefore, you must manually apply this hotfix. To do this, follow these steps: <ol> Run the SQL2000-KB913100-v8.00.1101-x64-ENU.exe package to extract the following two files:  x64\Sqlvdi.dll</li> x86\Sqlvdi.dll</li></ul>

These files are extracted into the directory in which you run the SQL2000-KB913100-v8.00.1101-x64-ENU.exe package.</li> Copy the x86\Sqlvdi.dll file to the :\Program Files (x86)\Microsoft SQL Server\80\COM directory.</li> Copy the x64\Sqlvdi.dll file to the :\Program Files\Microsoft SQL Server\80\COM directory.

Note If this path does not exist, you must create this path.</li> Click Start, click Run, type cmd in the Open box, and then click OK.</li> Change the directory to the directory to which you copied the x86 version of the Sqlvdi.dll file.</li> Type the following command, and then press ENTER to register the x86 version of Sqlvdi.dll:

regsvr32 sqlvdi.dll

</li> Change the directory to the directory to which you copied the x64 version of the Sqlvdi.dll file.</li> Type the following command, and then press ENTER to register the x64 version of Sqlvdi.dll:

regsvr32 sqlvdi.dll

</li> Restart the following:  <li>The backup program</li> <li>Any instances of SQL Server 2000</li> <li>The VSS</li></ul> </li></ol>

Important
 * You must apply this hotfix after you install SQL Server 2000 Service Pack 4 (SP4) on any one or more instances of SQL Server.
 * You must apply both the x64 version and the x86 version of the Sqlvdi.dll file at the same time. The new SQL Server Virtual Device Interface (VDI) support that is included in this hotfix is not compatible with earlier x86 versions of Sqlvdi.dll.

If you run SQL Server 2000 in a cluster environment on a Windows Server 2003, Enterprise x64 Edition-based computer, you must also follow these steps: <ol> <li>Click Start, click Run, type Regedit, and then click OK.</li> <li>Locate and then right-click the following registry subkey:

 

</li> <li>Click Export, and then save this registry subkey to a SQL1.reg file.</li> <li>Locate and then right-click the following registry subkey:

 

</li> <li>Click Export, and then save this registry subkey to a SQL2.reg file.</li> <li>In Notepad, open the SQL1.reg file, and then follow these steps: <ol style="list-style-type: lower-alpha;"> <li>On the Edit menu, click Replace.</li> <li>In the Find what box, type Wow6432Node\Microsoft .</li> <li>In the Replace with box, type Microsoft .</li> <li>Save the changes to the SQL1.reg file.</li> <li>Exit Notepad.</li></ol> </li> <li>Repeat step 6 for the SQL2.reg file.</li> <li>Right-click each modified .reg file, click Merge, and then click Yes when you are prompted to add this information to the registry.</li> <li>Restart the server.</li></ol>

<div class="workaround_section">

WORKAROUND
To work around this problem, stop SQL Server 2000 before you perform a System State backup operation.

<div class="status_section">

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

<div class="moreinformation_section">

MORE INFORMATION
For more information about the naming schema for Microsoft SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:

822499 New naming schema for Microsoft SQL Server software update packages

For more information, 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: SYSTEMSTATE NTBACKUP 64bit MSDE Writer

Keywords: kbbug kbfix kbqfe KB904418

-

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

© Microsoft Corporation. All rights reserved.