WSUS 3.0 console fails to open with "MMC could not create the snap-in" error

WSUS 3.0 console fails to open with "MMC could not create the snap-in" error

  • Comments 2
  • Likes

image

We've seen a couple instances of an issue here lately that I wanted to mention just in case anyone else happens to run across it.  The symptoms can vary but include the following:

  1. The WSUS console will not open and may generate the error "MMC could not create the snap-in"
  2. If you check the Update Services service for WSUS, you find that it is stopped.  When you attempt to start the service, it seems to start but stops again with no errors.
  3. You may see the following event in the event log:

Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 6510
Description: Common Language Runtime (CLR) v2.0.50727 not installed properly. The CLR is required to use SQL/CLR features.

What usually turns out to be the cause is a problem with .NET Framework and most of the time you can correct the issue by simply repairing it.  The easiest way to do this is by opening Add/Remove Programs, double-clicking on the version of Microsoft .NET Framework installed and selecting the Repair option.   If the repair cannot find the needed MSI, you can download .NET 2.0 SP1 and use /x to extract the needed MSI files to finish the repair.  You could also probably remove and reinstall it although I've never personally tried that myself so take that one with a grain of salt.

I must also give a special thanks to Justin Luyt and Mike Johnson for originally documenting this.  Thanks guys!

J.C. Hornbeck | Manageability Knowledge Engineer

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment