Error message when you open SQL Server Enterprise Manager after you uninstall the SQL Server 2005 Backward Compatibility Components: "Snap-in failed to initialize" (914157)


The information in this article applies to:

  • Microsoft SQL Server 2000 Personal Edition
  • Microsoft SQL Server 2000 Standard Edition
  • Microsoft SQL Server 2000 Enterprise Edition
  • Microsoft SQL Server 2000 Developer Edition
  • Microsoft SQL Server 2000 Workgroup Edition
Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry

SYMPTOMS

Consider the following scenario. You install the Microsoft SQL Server 2005 Backward Compatibility Components on a computer where SQL Server 2000 is installed. If you uninstall the SQL Server 2005 Backward Compatibility Components from the computer and then try to open SQL Server Enterprise Manager, you receive the following error message:
Snap-in failed to initialize.
Name: - not available -
CLSID:{00100100-1816-11D0-8EF5-00AA0062C58F}

CAUSE

This problem occurs because the following changes are made to the system after you uninstall the SQL Server 2005 Backward Compatibility Components:
  • The SqlPath registry subkey is removed from the registry.
  • The registration for the Sqlmmc.dll file is broken.

WORKAROUND

To work around this problem, use one of the following methods.

Method 1

  1. Reinstall the SQL Server 2005 Backward Compatibility Components.

    To download the SQL Server 2005 Backward Compatibility Components, search for "SQL Server 2005 Backward Compatibility Components" on the following Microsoft Download Center Web site:

    http://www.microsoft.com/downloads/details.aspx?familyid=d09c1d60-a13c-4479-9b91-9e8b9d835cdc&displaylang=en

  2. Click Start, click Run, type regsvr32 "Drive:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqlmmc.dll", and then click OK.

    Note Drive is a placeholder for the drive where you installed SQL Server 2000.

Method 2

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate the following registry subkey:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\80\Tools\ClientSetup

  3. Right-click the ClientSetup registry subkey, point to New, and then click String Value.
  4. Rename the registry subkey that you just created SqlPath, and then press ENTER.
  5. Double-click the SqlPath registry subkey, and then type Drive:\Program Files\Microsoft SQL Server\80\Tools in the Value data box.
  6. Click OK, and then close Registry Editor.
  7. Click Start, click Run, type regsvr32 "Drive:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqlmmc.dll", and then click OK.

STATUS

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

MORE INFORMATION

The SQL Server 2005 Backward Compatibility Components package includes the latest versions of the Data Transformation Services (DTS) 2000 runtime, SQL-DMO, Decision Support Objects (DSO), and SQL Virtual Device Interface (SQLVDI). These versions have been updated for compatibility with SQL Server 2005 and include all fixes through SQL Server 2000 Service Pack 4 (SP4).
Modification Type:MajorLast Reviewed:2/23/2006
Keywords:kbsql2005tool kbExpertiseAdvanced kbtshoot kbprb KB914157 kbAudDeveloper kbAudITPRO
©2004 Microsoft Corporation. All rights reserved.