Error: 'MMC Snap-in failed to initialize' when opening Exchange Migrator. (NETIQKB1861)

  • Document ID:7701861
  • Creation Date:02-Feb-2007
  • Modified Date:14-Jan-2008
    • Micro Focus Products:
      Exchange Migrator

Resolution

fact
Exchange Migrator 2.x

fact
Exchange Migrator 1.x

symptom
Error: 'MMC Snap-in failed to initialize' when opening Exchange Migrator.

symptom
When opening Exchange Migrator (EM) you get a SQL error in the background behind the EM window. Upon clicking OK to the SQL error you will get an error from EM that states, 'MMC Snap-in failed to initialize. Name: Exchange Migrator (EM) CLSID:{21407BBA-6C29-4AA8-BE44-48C166EE68A3}.' Following this, EM opens with a greyed out window in the right pane and you are unable to create a project.

fix

There are a few things that can be done to resolve this issue.

Note:  If the SQL Server front end is installed on another machine, it may be possible to connect to the MSDE database on the Console (machine running EM) to see if the EMA database actually exists.

If you have installed MSDE, then perform the following steps:

  1. First make sure that the MSSQLServer service is running.
  2. If step one does not resolve the problem, uninstall EM (choosing to delete the database) then MSDE from Add/Remove Programs.
  3. Go to the Exchange Migrator directory (%root%\Program files\NetIQ\Exchange Migrator) and delete the entire contents of the Exchange Migrator folder.
  4. Reinstall EM along with MSDE.
  5. If a SQL Server front-end is available, connect to the MSDE database to ensure the EMA database exists and is not corrupt.

If you have installed SQL Server 7.0 perform the following steps:

  1. First make sure that the MSSQLServer service is running.
  2. If step one does not resolve the problem, uninstall EM from Add/Remove Programs (choosing to delete the database).
  3. Go to the Exchange Migrator directory (%root%\Program files\NetIQ\Exchange Migrator) and delete the entire contents of the Exchange Migrator folder.
  4. Reinstall Exchange Migrator.
  5. Check the integrity of the EMA database within the SQL Enterprise Manager.
  6. Reinstalling SQL Server 7.0 along with EM may be necessary if this problem persists.

 



note
NetIQ will update this article with any new development.

Please contact Technical Support to create a Support Request for any issues you encounter that are not addressed by the User Guide, any Knowledge Base articles found on the website, or current hotfixes available for download.



Additional Information

Formerly known as NETIQKB1861