BUG: Removing one instance of the .NET Framework configuration snap-in from MMC causes the other instance not to initialize (834534)



The information in this article applies to:

  • Microsoft .NET Framework 1.0

SYMPTOMS

One of two instances of the .NET Framework configuration snap-in that you added to Microsoft Management Console (MMC) may not initialize. Specifically, if you add two instances of the .NET Framework configuration snap-in to MMC, and then you remove one instance, the other instance does not initialize, and you receive the following error message:

Snap-in failed to initialize

STATUS

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

WORKAROUND

If you want to use two instances of the .NET Framework Configuration snap-in at the same time, follow these steps:
  1. Click Start, click Run, type mmc, and then press ENTER.
  2. On the File menu, click Add/Remove Snap-in, and then click Add.
  3. Double-click .NET Framework Configuration.
  4. Click Close, and then click OK.
  5. Repeat steps 1 through 4 to add another instance of the .NET Framework Configuration snap-in.

MORE INFORMATION

Steps to reproduce the behavior

  1. Click Start, click Run, type mmc, and then press ENTER.
  2. On the File menu, click Add/Remove Snap-in.
  3. Click the Add button.
  4. To add two instances of the .NET Framework Configuration snap-in, double-click .NET Framework Configuration two times.
  5. Click Close, and then click OK.

    You receive the following error message:

    Only one instance of the .NET Framework Configuration tool may run at a time.

  6. Click OK to dismiss the message.

    Notice that two instances of .NET Framework Configuration snap-in appear in the scope pane in MMC.
  7. Try to expand the two nodes by double-clicking the nodes. Notice that only one instance of the snap-in works correctly.
  8. On the File menu, click Add/Remove Snap-in, select the instance that does work correctly, and then click Remove.
  9. Click OK to go back to MMC scope pane.
  10. Try to access the remaining instance of the .NET Framework Configuration snap-in.

    You receive the error message that is listed in the "Symptoms" section.

Modification Type:MajorLast Reviewed:2/24/2004
Keywords:kberrmsg kbbug KB834534 kbAudDeveloper