Select the product you need help with

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

Article ID: 914157 - View products that this article applies to.

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}

Back to the top | Give Feedback

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.

Back to the top | Give Feedback

WORKAROUND

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

Method 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
(http://www.microsoft.com/downloads/details.aspx?familyid=d09c1d60-a13c-4479-9b91-9e8b9d835cdc&displaylang=en)
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

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756

(http://support.microsoft.com/kb/322756/ )

How to back up and restore the registry in Windows

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

Back to the top | Give Feedback

STATUS

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

Back to the top | Give Feedback

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).

Back to the top | Give Feedback