Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
FIX: The MSDE writer is not included when you try to use the Vssadmin.exe tool to list subscribed volume shadow copy writers
Article ID: 913100 - View products that this article applies to.
Bug number: 165 (SQL Hotfix)
Consider the following scenario. On a Microsoft Windows Server 2003 x64-based computer that is running Microsoft SharePoint Team Services, you try to use the Volume Shadow Copy Service (VSS) administrative command-line tool (Vssadmin.exe) to list subscribed volume shadow copy writers. You may notice that the Microsoft SQL Server 2000 Desktop Engine (MSDE) writer is not included in the list. In this scenario, you may find that the Vssadmin.exe tool stops responding. You may receive the following error message in the Windows event log:
Note This problem also occurs with other 32-bit SKUs in SQL Server 2000 that are configured to use the shared memory protocol only.
Sqllib error: OLEDB Error encountered calling IDBInitialize::Initialize. hr = 0x80004005. SQLSTATE: 08001, Native
Error state: 1, Severity: 16
Source: Microsoft OLE DB Provider for SQL Server
Error message: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
This problem occurs when you configure the instance of MSDE to use the shared memory protocol only. In this scenario, the Vssadmin.exe tool for Windows Server 2003 x64 cannot communicate with MSDE by using the 32-bit client network library component for the shared memory protocol (Dbmslpcn.dll). Additionally, SQL Server Desktop Engine (Windows) is installed when you install SharePoint Team Services. The instance of SQL Server Desktop Engine (Windows) can only use the shared memory protocol.
Hotfix informationA supported feature that modifies the default behavior of the product is now available from Microsoft, but it is only intended to modify the behavior that this article describes. Apply it only to systems that specifically require it. This feature may receive additional testing. Therefore, if you are not severely affected by the lack of this feature, we recommend that you wait for the next SQL Server 2000 service pack that contains this feature.
To obtain this feature immediately, download the feature by following the instructions later in this article or contact Microsoft Product Support Services. 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=supportThe following files are available for download from the Microsoft Download Center:
Download the 913100 hotfix for SQL Server 2000 package now.
Collapse this imageExpand this image
(http://download.microsoft.com/download/7/5/4/7543712c-9d50-4600-b8c5-7a7d2dd5a5b0/SQL2000-KB913100-v8.00.1101-x64-ENU.exe)Release Date: January 31, 2006
For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.
(http://support.microsoft.com/kb/119591/ )How to obtain Microsoft support files from online services
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.
Collapse this tableExpand this table
To work around this problem, configure the instance of MSDE to use a protocol other than the shared memory protocol. For example, you can use TCP/IP instead.
Note This workaround does not work for SQL Server Desktop Engine (Windows).
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:
822499For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/822499/ )New naming schema for Microsoft SQL Server software update packages
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
Article ID: 913100 - Last Review: October 9, 2011 - Revision: 2.0