Snap-in failed to initialize: Enterprise Manager

The Snap-in failed to initialize error message as associated with the Enterprise Manager is usually caused by orphaned registry keys. This message is usually associated with the Microsoft Management Console (MMC) and in some cases with Internet Information Services (IIS), but Enterprise Manager is also know to get plagued with it.

In case of Enterprise Manager, the Snap-in failed to initialize is caused by problems with Microsoft SQL Server 2005 Backward Compatibility Components.

What does the Snap-in failed to initialize message mean?

When upgrading from SQL Server 2000 to SQL Server 2005, the first step people usually take is to just upgrade the SQL Server 2000 with the Microsoft SQL Server 2005 Backward Compatibility Components. This allows them to run their SQL 2000 instance with the ability to also use SQL 2005 databases and functionality.

If for any reason the Microsoft SQL Server 2005 Backward Compatibility Components is uninstalled later, on a computer where SQL Server 2000 is installed, and you then go to the Enterprise Manager, you will experience the following error message:

Snap-in failed to initialize.
Name: - not available -
CLSID:{00100100-1816-11D0-8EF5-00AA0062C58F}

This is caused by two possible reasons:

• The SqlPath registry key is missing in registry
• The Sqlmmc.dll library registration is failing

Hopefully, there is an easy way to fix this.

How to fix Snap-in failed to initialize: Reinstall SQL 2005 Compatibility Components

The easiest way to fix this is to probably take the SQL CD and reinstall the SQL Server 2005 Backward Compatibility Components.

After the SQL Server 2005 Backward Compatibility Components is reinstalled, you would also need to re-register the library. You can do so using the following steps:

Go to the Start menu,
click Run,
type regsvr32 C:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqlmmc.dll,
hit ENTER

This should fix the Snap-in failed to initialize error message.

How to fix Snap-in failed to initialize: Fix the SqlPath registry key value

In case you are unable to reinstall the Compatibility Components, you can try to manually fix the registry key.

WARNING: When modifying registry entries, always back up and exercise extreme caution.

If you modify the registry incorrectly, it can leave your computer completely non-functional which can call for reinstallation of your operating system.

Go to the Start menu, click Run, type REGEDIT, and then hit ENTER.

Find the following registry key:

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

Rename the registry key to SqlPath and then hit ENTER.

Double-click the SqlPath registry key and type C:\Program Files\Microsoft SQL Server\80\Tools into the Value data box.

Exit the Registry Editor

After you modify the SqlPath variable, you also need to re-register the library.

Go to the Start menu,
click Run,
type regsvr32 C:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqlmmc.dll,
and then click ENTER

Snap-in failed to initialize: Management Console (MMC)

What does it mean when you get the Snap-in failed to initialize error message when launching the Management Console (MMC)? You can find that here: Snap-in failed to initialize: Management Console (MMC)

Snap-in failed to initialize: Internet Information Services (IIS)

The Snap-in failed to initialize message can happen when opening Internet Information Services (IIS) console too. You can find some details about that here: Snap-in failed to initialize: Internet Information Services (IIS)