SCOM 2012 Web Console HttpWebRequest_WebException_RemoteServer

Had an issue today in a test environment with a freshly installed SCOM 2012 all-in-one machine. SCOM was working fine. Started the SCOM Web Console and suddenly got an error. The details of the error looked like this:

System.ServiceModel.CommunicationException: [HttpWebRequest_WebException_RemoteServer]
Arguments: NotFound

The rest is here in a screenshot:

Web Cons Error

So clicked around a little bit and came to the conclusion that I must have missed something during prerequisite installation or installation of the SCOM Web Console had some issue. Not wanting to loose too much time I went for removing the Web Console feature and re-doing some prerequisite installation stuff.

  1. Start SCOM 2012 installation and select to remove a feature. Remove Web Console feature.
  2. Run some powershell commands to install the prerequisites:
    Import-Module ServerManager
    Add-WindowsFeature NET-Framework-Core,Web-Static-Content,Web-Default-Doc,Web-Dir-Browsing,Web-Http-Errors,Web-Http-Logging,Web-Request-Monitor,Web-Filtering,Web-Stat-Compression,AS-Web-Support,Web-Metabase,Web-Asp-Net,Web-Windows-Auth –restart
  3. Run the following command from elevated command prompt to register the ASP .NET 4 with IIS.
    c:windowsMicrosoft.NETFramework64v4.0.30319aspnet_regiis.exe -r
  4. Next the command to allow the Asp .Net 4 ISAPI/CGI.
    c:windowssystem32inetsrvappcmd set config /section:isapiCgiRestriction /[path=`’C:WindowsMicrosoft.NETFramework64v4.0.30319aspnet_isapi.dll`’].allowed:True
  5. Restart the server
  6. Run SCOM 2012 setup and select to add a feature and add the Web Console feature.

Started up the web console link again from internet explorer and got a logon prompt and a few seconds later had a working Web Console.

I guess the principle of “when in doubt why it is not working -> re-install the Web Console” still works.

Enjoy!
Bob Cornelissen

Comments are closed.