none
SCOM 1801: Again and Again Web Console !

    Pregunta

  • Hi,

    we deployed Web Console server in our SCOM 1801 infrastructure with following roles: - SCOM Web Console - SQL Server Reporting Services I tried to access using following URLs: 1) Subsite "AppAdvisor" SUCCESSFUL: http://localhost/AppAdvisor SUCCESSFUL: http://<WEBSERVER>/AppAdvisor SUCCESSFUL: http://FQDN of WEBSERVER/AppAdvisor 2) Subsite "AppDiagnostics" SUCCESSFUL: http://localhost/AppDiagnostics SUCCESSFUL: http://<WEBSERVER>/AppDiagnostics SUCCESSFUL: http://FQDN of WEBSERVER/AppDiagnostics 3) Subsite "Dashboard" FAILED: http://localhost/Dashboard FAILED: http://<WEBSERVER>/Dashboard FAILED: http://FQDN of WEBSERVER/Dashboard

    Error details:

    
    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. See http://go.microsoft.com/fwlink/?linkid=106663&Version=5.1.50907.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. See http://go.microsoft.com/fwlink/?linkid=106663&Version=5.1.50907.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. See http://go.microsoft.com/fwlink/?linkid=106663&Version=5.1.50907.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)

    4) Subsite "OperationsManager" SUCCESSFUL: http://localhost/OperationsManager FAILED: http://<WEBSERVER>/OperationsManager FAILED: http://FQDN of WEBSERVER/OperationsManager 5) ReportServer SUCCESSFUL: http://localhost/ReportServer_<SQL_Instance> SUCCESSFUL: http://<WEBSERVER>/ReportServer_<SQL_Instance> SUCCESSFUL: http://FQDN of WEBSERVER/ReportServer_<SQL_Instance> 6) Reports SUCCESSFUL: http://localhost/Reports_<SQL_Instance> SUCCESSFUL: http://<WEBSERVER>/Reports_<SQL_Instance> SUCCESSFUL: http://FQDN of WEBSERVER/Reports_<SQL_Instance>

    I am wondering when Microsoft will develop a good Web Console? I have again a heavy headache because of Web Console.

    Best Reagrds

    Birdal




    • Editado _Birdal martes, 8 de mayo de 2018 8:54
    martes, 8 de mayo de 2018 8:44

Todas las respuestas

  • Same issue for me!
    miércoles, 9 de mayo de 2018 2:11
  • Hi Nick,

    did you find any solution?

    Best regards

    Birdal

    lunes, 11 de junio de 2018 12:18
  • Hi,

    Have you imported HP OneView Management pack 4.0.0.0 ?

    If imported, suggest delete it for test.

    https://social.technet.microsoft.com/Forums/en-US/cca3b363-3a46-4317-92d3-80fef66fd48d/tasks-missing-scom-console-2016?forum=operationsmanagergeneral

    lunes, 11 de junio de 2018 12:53
  • Please refer to following for troubleshoot
    1) https://social.technet.microsoft.com/Forums/systemcenter/en-US/546fb6f4-76b1-4832-ba95-02721f2bab0f/scom-web-console-not-working?forum=operationsmanagergeneral
    2) Can’t access web console remotely
    http://www.systemcentercentral.com/forums-archive/topic/cant-access-web-console-remotely/
    Roger
    martes, 12 de junio de 2018 3:13
  • That may be a stupid question, buy why are you trying to access the "Dashboard" subsite?

    I don't really know why it's here and I can't test it right now, but it doesn't look like you are supposed to use it...

    Edit : answer to myself : it allows you to access the old SCOM console if you need to use your old dashboards.

    Which means the new web console is not backward compatible with all your old dashboards.

    And of course this is documented absolutely nowhere...

    Is this what they call "removing silverlight dependency"? In my words, I would have said "deprecating silverlight components"... that's not exactly the same thing.

    Thank you so much Microsoft -_-'



    • Editado CyrAz miércoles, 13 de junio de 2018 8:18
    martes, 12 de junio de 2018 15:46
  • Hi,

    the issue is not related to access the old SCOM components.

    The main issue that the access FAILED!

    FAILED: http://localhost/Dashboard FAILED: http://<WEBSERVER>/Dashboard FAILED: http://FQDN of WEBSERVER/Dashboard

    Best regards

    Birdal

    jueves, 21 de junio de 2018 7:33