locked
SM2012 - Portal gives 404 error when opening KB article RRS feed

  • Question

  • In my System Center 2012 Service Manager demo environment, the portal bombs out the 404 error below whenever a user tries to open a Knowledge Base article.  This happens with normal end users and administrators, and when done from the Help Articles search page or from a Service Offering page.  So far, everything else is working fine in the portal.

    Does anyone have any ideas for troubleshooting this?

    Server Error in '/ContentHost' Application.

    The remote server returned an error: (404) Not Found.

    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. 
    An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
    [WebException: The remote server returned an error: (404) Not Found.]
       System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult) +3236137
       System.ServiceModel.Channels.HttpChannelAsyncRequest.CompleteGetResponse(IAsyncResult result) +216
    
    [EndpointNotFoundException: There was no endpoint listening at https://MyFQDN.local/ServiceHost/Services/DataAccessService.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.]
       System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) +4728723
       System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) +1725
       Microsoft.EnterpriseManagement.Presentation.DataAccess.Proxy.ServiceReference.IDataAccessService.EndExecute(IAsyncResult result) +0
       Microsoft.EnterpriseManagement.Presentation.DataAccess.Proxy.ServiceReference.DataAccessServiceClient.EndExecute(IAsyncResult result) +323
       Microsoft.EnterpriseManagement.Presentation.DataAccess.ProxyDataGateway.ExecuteScalar(DataCommandScalar`1 command) +654
    
    [DataAccessException: There was no endpoint listening at https://MyFQDN.local/ServiceHost/Services/DataAccessService.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.]
       Microsoft.EnterpriseManagement.ServiceManager.Portal.ContentHost.KnowledgeArticleHandler.GetEndUserContent(HttpContext context) +1291
       Microsoft.EnterpriseManagement.ServiceManager.Portal.ContentHost.KnowledgeArticleHandler.ProcessRequest(HttpContext context) +287
       System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +625
       System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +270
    


    Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.272


    Nash Pherson, Senior Systems Consultant, Now Micro - http://www.nowmicro.com <--- If this post was helpful, please click "Vote as Helpful".


    • Edited by NPherson Tuesday, March 13, 2012 7:13 PM typo
    Tuesday, March 13, 2012 7:12 PM

All replies

  • Can you enter the portal service url in the browser and make sure if its up

    https://MyFQDN.local/ServiceHost/Services/DataAccessService.svc

    Seems like the service endpoint was changed post install. 

     

    Thanks, Paresh

    Monday, March 19, 2012 6:14 AM
    Answerer
  •  

    I have the the same problem, when opening an KB article on the web Portal of SCSM2012R2:

    [WebException: The remote server returned an error: (404) Not Found.]    System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult) +8606675    System.ServiceModel.Channels.HttpChannelAsyncRequest.CompleteGetResponse(IAsyncResult result) +222

    [EndpointNotFoundException: There was no endpoint listening at http://myserver.xyz.corp:81/ServiceHost/Services/DataAccessService.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.]    System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) +14543138    System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) +622    Microsoft.EnterpriseManagement.Presentation.DataAccess.Proxy.ServiceReference.IDataAccessService.EndExecute(IAsyncResult result) +0    Microsoft.EnterpriseManagement.Presentation.DataAccess.Proxy.ServiceReference.DataAccessServiceClient.EndExecute(IAsyncResult result) +323    Microsoft.EnterpriseManagement.Presentation.DataAccess.ProxyDataGateway.ExecuteScalar(DataCommandScalar`1 command) +654

    [DataAccessException: There was no endpoint listening at http://myserver.xyz.corp:81/ServiceHost/Services/DataAccessService.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.]    Microsoft.EnterpriseManagement.ServiceManager.Portal.ContentHost.KnowledgeArticleHandler.GetEndUserContent(HttpContext context) +1292    Microsoft.EnterpriseManagement.ServiceManager.Portal.ContentHost.KnowledgeArticleHandler.ProcessRequest(HttpContext context) +287    System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +913    System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +165

     

     

    But

    http://myserver.xyz.corp:81/ServiceHost/Services/DataAccessService.svc

    is responding fine. So the endpoint is listening, also the webservice is reachable

    this is the actual url which is failing:

    https://myserver.xyz.corp/ContentHost/ClientBin/KnowledgeArticleViewer.aspx?ArticleId=4517f8fb-520b-e2ff-635c-8196583a9a05

     

    a call to

    https://myserver.xyz.corp/ContentHost/ClientBin/KnowledgeArticleViewer.aspx?ArticleId=

    responses with “unrecognized guid format”. so the webservice KnowledgeArticleViewer seems to be reachable. the GUID also is fine (checked with a runbook and this is the proper scobjectid)

    seems to be independend of permissions, even members of the administators role have the same issue

    any ideas?

    regards

    Manfred
    Wednesday, November 27, 2013 8:10 AM
  • ktm628 - sorry, I was able to resolve this way back when, but I have no idea what we needed to do.  We ran into all sorts of issues with permissions and with IIS that had to get worked through.

    Nash Pherson, Senior Systems Consultant
    Now Micro - My Blog Posts
    <-- If this post was helpful, please click "Vote as Helpful".

    Wednesday, November 27, 2013 3:02 PM
  • have you ever found its resolution?

    I am also facing the same error.

    Please help, Making registry entries did not worked for me

    Friday, January 10, 2014 10:51 AM