I've deployed SCSM 2012 and have the SSP up and running however whenever you try to access a Knowledge Article I get the following error:

The remote server returned an error: (502) Bad Gateway.

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. Exception Details: System.Net.WebException: The remote server returned an error: (502) Bad Gateway. Source Error:

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.

Stack Trace:

[WebException: The remote server returned an error: (502) Bad Gateway.]    System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult, TransportContext& context) +3236201    System.ServiceModel.Channels.GetOutputStreamAsyncResult.CompleteGetRequestStream(IAsyncResult result) +91 [EndpointNotFoundException: There was no endpoint listening at https://SERVERNAME:444/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) +4729427    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://SERVERNAME:444/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

We've tried re-installing the SSP and SharePoint and configured different ports however the error did not improve.  It does not matter whether you try to access the SSP from a client or the server the result is the same.  This problem only seems to exist when clicking on "Help Articles", searching for a KA, and then clicking the actual KA link.

Has anyone else run into this or might know of a solution?

Thank you.

Hello Ira,

Just out of curiousity, what is the value of the ContentHostAbsoluteUri key in the web.config of the Content Host of the System Center Service Manager Portal?
http://social.technet.microsoft.com/Forums/en-AU/portals/thread/7cd31024-13f9-43c2-86d9-a54c65cf9653

As I understand correctly, everything else works fine. So you are able to create an incident and view your requests?

Can you access the DataAccessService.svc url described above in the error via a browser?

Hello Expiscornovus,

Below are the webconfig settings

<appSettings>
<!-- <add key="ContentHostAbsoluteUri" value="https://SERVERNAME.contoso.com:444/ContentHost" /> -->
<add key="ContentHostAbsoluteUri" value="https://SERVERNAME:444/ContentHost" />
  </appSettings>
</configuration>

You are correct in understanding that everything else works fine including creating incidents and viewing requests.

If I access the DataAccessService.svc URL it takes me the "DataAccessService Service" page where it says "You have created a service" and it all looks OK.

Hello Ira,

I presume you have already tried to add the FQDN of the server seeing the comment in your webconfig settings with the contoso.com url?

Hello,

And Yes, you are correct I have tried that and the result is a certificate error indicating a Web Address Mismatch.

I have been unable to find the solution.  Does anyone have any suggetions?

Hello Ira,

Sounds like you have a certificate issue. Via what url do you access the portal via your browser?

Btw, have you followed the instructions described in this Technet article about SSL certificates:
http://technet.microsoft.com/en-us/library/hh667343

Did you ever find out solution to it? I am facing the same problem, please help.

Thanks in advance

These type of errors usually indicate that the web services are not bound to the proper protocols. Hopefully this will help you.

Make copies of the web.config files before editing!!!!

Take look at the Custom Bindings in the web.config file for the contenthost virtual directory. Make sure that both DefaultHttpBinding and DefaultHttpsBinding are present. See below.

******

<binding name="DefaultHttpBinding">
     <binaryMessageEncoding />
     <httpTransport maxReceivedMessageSize="2147483647" maxBufferSize="2147483647" />
    </binding>
<binding name="DefaultHttpsBinding">
     <binaryMessageEncoding />
     <httpsTransport maxReceivedMessageSize="2147483647" maxBufferSize="2147483647" />
    </binding>

****************

Also look at the endpoint address mappings to make sure that both are there.

************

<endpoint address="ServiceHost/Services/DataAccessService.svc" binding="customBinding" bindingConfiguration="DefaultHttpBinding" ........
<endpoint address="ServiceHost/Services/DataAccessService.svc" binding="customBinding" bindingConfiguration="DefaultHttpsBinding" ................

**********************

Next, look at the ServiceHost virtual director web.config file: Make sure that everything is using HTTPS bindings. See below:

Look at ServiceBehavior Section:

Make sure that HTTPSGetEnabled=true is set.

In the Services Section:

Make sure that endpoint bindingconfiguration=DefaultHttpsBinding is set.

In  the Bindings > CustomBinding Section:

Make sure that the Binding Name is DefaultHttpsBinding

Save the files and reset IIS, see what you get now.

Rick