[Forum FAQ] “An unexpected error has occurred” in SCOM 2012 Web Console

Symptom

If you use the SCOM web console with HTTPS instead of HTTP, the following error may occur:

An unexpected error has occurred. (Figure 1)

Figure 1

The “show error details” shows the following:

Please provide the following information to the support engineer if you have to contact Microsoft Help and Support:

System.ServiceModel.CommunicationException: [HttpWebRequest_WebException_RemoteServer]

Arguments: NotFound

Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. Seehttp://go.microsoft.com/fwlink/?linkid=106663&Version=5.1.20125.0&File=System.Windows.dll&Key=HttpWebRequest_WebException_RemoteServer---> System.Net.WebException: [HttpWebRequest_WebException_RemoteServer]

Arguments: NotFound

Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. Seehttp://go.microsoft.com/fwlink/?linkid=106663&Version=5.1.20125.0&File=System.Windows.dll&Key=HttpWebRequest_WebException_RemoteServer---> System.Net.WebException: [HttpWebRequest_WebException_RemoteServer]

Arguments: NotFound

Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. Seehttp://go.microsoft.com/fwlink/?linkid=106663&Version=5.1.20125.0&File=System.Windows.dll&Key=HttpWebRequest_WebException_RemoteServer

   at System.Net.Browser.BrowserHttpWebRequest.InternalEndGetResponse(IAsyncResult asyncResult)

   at System.Net.Browser.BrowserHttpWebRequest.<>c__DisplayClassa.<EndGetResponse>b__9(Object sendState)

   at System.Net.Browser.AsyncHelper.<>c__DisplayClass4.<BeginOnUI>b__0(Object sendState)

   --- End of inner exception stack trace ---

   at System.Net.Browser.AsyncHelper.BeginOnUI(SendOrPostCallback beginMethod, Object state)

   at System.Net.Browser.BrowserHttpWebRequest.EndGetResponse(IAsyncResult asyncResult)

   at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelAsyncRequest.CompleteGetResponse(IAsyncResult result)

   --- End of inner exception stack trace ---

   at System.ServiceModel.AsyncResult.End[TAsyncResult](IAsyncResult result)

   at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result)

   at System.ServiceModel.ClientBase`1.ChannelBase`1.EndInvoke(String methodName, Object[] args, IAsyncResult result)

   at Microsoft.EnterpriseManagement.Presentation.Security.ServiceProxies.LogonServiceClient.LogonServiceClientChannel.EndGetConfiguration(IAsyncResult result)

   at Microsoft.EnterpriseManagement.Presentation.Security.ServiceProxies.LogonServiceClient.Microsoft.EnterpriseManagement.Presentation.Security.ServiceProxies.ILogonService.EndGetConfiguration(IAsyncResult result)

   at Microsoft.EnterpriseManagement.Presentation.Security.ServiceProxies.LogonServiceClient.OnEndGetConfiguration(IAsyncResult result)

   at System.ServiceModel.ClientBase`1.OnAsyncCallCompleted(IAsyncResult result)

Resolution

When we use HTTP, the web.config file is below:

    <behaviors>

      <serviceBehaviors>

        <behavior name="DefaultServiceBehavior">

          <serviceMetadata httpGetEnabled="true"/>

          <serviceDebug includeExceptionDetailInFaults="false"/>

          <dataContractSerializer maxItemsInObjectGraph="2147483647"/>

        </behavior>

      </serviceBehaviors>

    </behaviors>

<services>

      <!-- Logon Service -->

      <service behaviorConfiguration="DefaultServiceBehavior" name="Microsoft.EnterpriseManagement.Presentation.Security.Services.LogonService">

        <endpoint address="" binding="customBinding" contract="Microsoft.EnterpriseManagement.Presentation.Security.Services.ILogonService" bindingConfiguration="DefaultHttpBinding"/>

      </service>

      <!-- Data Access service -->

      <service behaviorConfiguration="DefaultServiceBehavior" name="Microsoft.EnterpriseManagement.Presentation.DataAccess.Server.DataAccessService">

        <endpoint address="" binding="customBinding" contract="Microsoft.EnterpriseManagement.Presentation.DataAccess.Server.IDataAccessService" bindingConfiguration="DefaultHttpBinding"/>

      </service>

    </services>

As we are using HTTPS, we need to modify the web.congfig file as below (Red part):

<serviceBehaviors>

        <behavior name="DefaultServiceBehavior">

          <serviceMetadata httpGetEnabled="false"/>

And

<!-- Logon Service -->

      <service behaviorConfiguration="DefaultServiceBehavior" name="Microsoft.EnterpriseManagement.Presentation.Security.Services.LogonService">

        <endpoint address="" binding="customBinding" contract="Microsoft.EnterpriseManagement.Presentation.Security.Services.ILogonService" bindingConfiguration="DefaultHttpsBinding"/>

      </service>

      <!-- Data Access service -->

      <service behaviorConfiguration="DefaultServiceBehavior" name="Microsoft.EnterpriseManagement.Presentation.DataAccess.Server.DataAccessService">

        <endpoint address="" binding="customBinding" contract="Microsoft.EnterpriseManagement.Presentation.DataAccess.Server.IDataAccessService" bindingConfiguration="DefaultHttpsBinding"/>

      </service>

Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.