%3CLINGO-SUB%20id%3D%22lingo-sub-1855616%22%20slang%3D%22en-US%22%3ECLSID%20failed%20(800700b7)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1855616%22%20slang%3D%22en-US%22%3E%3CP%3EIf%20IIS%20Manager%20doesn%E2%80%99t%20open%20because%20of%20the%20error%20below%2C%20it%20may%20cause%20delays%20in%20maintenance%20and%20migrations.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20error%20message%3A%3C%2FP%3E%0A%3CP%3E%3CEM%3ECreating%20an%20instance%20of%20the%20COM%20component%20with%20CLSID%20from%20the%20IClassFactory%20failed%20due%20to%20the%20following%20error%3A%20800700b7%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Nedim_0-1604542346076.jpeg%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F231564i0B3B326D3F6FFC84%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22Nedim_0-1604542346076.jpeg%22%20alt%3D%22Nedim_0-1604542346076.jpeg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId--1211289964%22%20id%3D%22toc-hId--1211289938%22%3E%26nbsp%3B%3C%2FH2%3E%0A%3CH2%20id%3D%22toc-hId-1276222869%22%20id%3D%22toc-hId-1276222895%22%3ESolution%3C%2FH2%3E%0A%3CP%3EThis%20issue%20may%20happen%20after%20an%20in-place%20upgrade%2C%20migration%2C%20Windows%20updates%20or%20any%20other%20operation%20that%20works%20with%20system%20libraries.%20There%20is%20likely%20a%20corrupted%20or%20missing%20system%20file.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThere%20are%20a%20couple%20things%20to%20check%20if%20you%20run%20into%20this%20issue%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3ECheck%20Event%20Viewer%20to%20find%20out%20information%20about%20the%20root%20cause%3C%2FLI%3E%0A%3CLI%3ECollect%20Process%20Monitor%20trace%20and%20look%20for%20any%20failures.%20Don%E2%80%99t%20be%20surprised%20if%20everything%20looks%20good%20in%20the%20trace%20because%20the%20root%20cause%20may%20hide%20behind%20a%20SUCCESS%20message.%20Take%20another%20trace%20from%20a%20working%20server%20and%20compare%20them%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20logs%20and%20traces%20don%E2%80%99t%20provide%20a%20lead%2C%20here%20are%20a%20few%20things%20to%20try%20(Test%20if%20IIS%20Manager%20opens%20successfully%20after%20each%20step)%3A%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3EUninstall%20IIS%20Management%20Tools%20in%20Server%20Manager%20and%20install%20them%20back%3C%2FLI%3E%0A%3CLI%3ECheck%20if%20IIS%20Admin%20Service%20starts%20in%20Services%20window%3C%2FLI%3E%0A%3CLI%3EPerform%26nbsp%3Biisreset%26nbsp%3B%3C%2FLI%3E%0A%3CLI%3ERun%26nbsp%3Baspnet_regiis%20-I%26nbsp%3B%3C%2FLI%3E%0A%3CLI%3ECheck%20the%20permissions%20on%20this%20folder%3A%26nbsp%3Bc%3A%5CprogramData%5CMicrosoft%5Ccrypto%5CRSA%5CmachineKeys%3CBR%20%2F%3EMake%20sure%20Everyone%20has%20Read%2FWrite%20and%20Administrators%20have%20all%20permissions%3C%2FLI%3E%0A%3CLI%3EReinstall%20.NET%20Framework%3C%2FLI%3E%0A%3CLI%3EIf%20nothing%20works%2C%20uninstall%20IIS%20and%20install%20it%20back%3C%2FLI%3E%0A%3C%2FOL%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1855616%22%20slang%3D%22en-US%22%3E%3CP%3EIf%20IIS%20Manager%20doesn%E2%80%99t%20open%20because%20of%20the%20error%20below%2C%20it%20may%20cause%20delays%20in%20maintenance%20and%20migrations.%3C%2FP%3E%3C%2FLINGO-TEASER%3E
Microsoft

If IIS Manager doesn’t open because of the error below, it may cause delays in maintenance and migrations.

 

The error message:

Creating an instance of the COM component with CLSID from the IClassFactory failed due to the following error: 800700b7

Nedim_0-1604542346076.jpeg

 

 

Solution

This issue may happen after an in-place upgrade, migration, Windows updates or any other operation that works with system libraries. There is likely a corrupted or missing system file.

 

There are a couple things to check if you run into this issue:

  • Check Event Viewer to find out information about the root cause
  • Collect Process Monitor trace and look for any failures. Don’t be surprised if everything looks good in the trace because the root cause may hide behind a SUCCESS message. Take another trace from a working server and compare them

 

If logs and traces don’t provide a lead, here are a few things to try (Test if IIS Manager opens successfully after each step):

  1. Uninstall IIS Management Tools in Server Manager and install them back
  2. Check if IIS Admin Service starts in Services window
  3. Perform iisreset 
  4. Run aspnet_regiis -I 
  5. Check the permissions on this folder: c:\programData\Microsoft\crypto\RSA\machineKeys
    Make sure Everyone has Read/Write and Administrators have all permissions
  6. Reinstall .NET Framework
  7. If nothing works, uninstall IIS and install it back