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

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

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: date
  Time: time
  User: N/A
  Computer: computername
  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].

• Event ID 6008

  Event Type: Error
  Event Source: VSS
  Event Category: None
  Event ID: 6008
  Date: date
  Time: time
  User: N/A
  Computer: computername
  Description: Sqllib error: Failed to create VDS object. hr = 0x80040154.

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

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.

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

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.

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, submit a request to 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

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:

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.

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:

1. Run the SQL2000-KB913100-v8.00.1101-x64-ENU.exe package to extract the following two files:
   • x64\Sqlvdi.dll
   • x86\Sqlvdi.dll
   These files are extracted into the directory in which you run the SQL2000-KB913100-v8.00.1101-x64-ENU.exe package.
2. Copy the x86\Sqlvdi.dll file to the Drive:\Program Files (x86)\Microsoft SQL Server\80\COM directory.
3. Copy the x64\Sqlvdi.dll file to the Drive:\Program Files\Microsoft SQL Server\80\COM directory.
   
   Note If this path does not exist, you must create this path.
4. Click Start, click Run, type cmd in the Open box, and then click OK.
5. Change the directory to the directory to which you copied the x86 version of the Sqlvdi.dll file.
6. Type the following command, and then press ENTER to register the x86 version of Sqlvdi.dll:
   regsvr32 sqlvdi.dll
7. Change the directory to the directory to which you copied the x64 version of the Sqlvdi.dll file.
8. Type the following command, and then press ENTER to register the x64 version of Sqlvdi.dll:
   regsvr32 sqlvdi.dll
9. Restart the following:
   • The backup program
   • Any instances of SQL Server 2000
   • The VSS

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:

1. Click Start, click Run, type Regedit, and then click OK.
2. Locate and then right-click the following registry subkey:
   HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\MSSQLServer
3. Click Export, and then save this registry subkey to a SQL1.reg file.
4. Locate and then right-click the following registry subkey:
   HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server
5. Click Export, and then save this registry subkey to a SQL2.reg file.
6. In Notepad, open the SQL1.reg file, and then follow these steps:
   1. On the Edit menu, click Replace.
   2. In the Find what box, type Wow6432Node\Microsoft.
   3. In the Replace with box, type Microsoft.
   4. Save the changes to the SQL1.reg file.
   5. Exit Notepad.
7. Repeat step 6 for the SQL2.reg file.
8. Right-click each modified .reg file, click Merge, and then click Yes when you are prompted to add this information to the registry.
9. Restart the server.

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

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

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: For more information, click the following article number to view the article in the Microsoft Knowledge Base: