none
There was no endpoint listening - WCF error RRS feed

  • Question

  • Hi, 

    We developed a windows service, which access the external webservice.

    We are receiving below error from service hosted on one particular customer PC(whereas it works fine in other PC for same customer). 

    Error: There was no endpoint listening at https://externalservice.svc that could accept the message. This is often caused by an incorrect address or SOAP action

    Stack Trace: at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream() at System.ServiceModel.Channels.HttpOutput.Send(TimeSpan timeout) at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.SendRequest(Message message, TimeSpan timeout) at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout) at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation) at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message) 

    Note: When fiddler running in background, We are not observing the same error message. 

    Please do needful. 

    Monday, June 20, 2016 9:07 AM

Answers

  • Rebuild the machine or replace it, because otherwise, you are looking for a needle in a haystack.

    Tuesday, June 21, 2016 2:18 PM
  • Hello,

    Based on your decription, I know that this error only happens on the particular machine, but it works fine in the others machine. So this issue is related with environment of this particular machine, then as @DA924x said, the most easy way is to replace this machine. Or you may need to compare the IIS setting on this particular machine with the IIS setting in others machines which can host the Service successful to see if you have done something wrong or different on this particular machine.

    Besides, you can also try to enable the WCF trace to see if there is any others clues.

    Best Regards,
    Amy Peng


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Tuesday, July 5, 2016 6:06 AM
    Moderator

All replies

  • Hi Gunarathinam,

    >> There was no endpoint listening at https://externalservice.svc that could accept the message. This is often caused by an incorrect address or SOAP action

    This error means the request URL is not the right URL or the service did not start. Do you mean this error only happened in one particular pc and the request works correct in fiddler? If you open the https://externalservice.svc in web browser, will you get the correct result?

    I would suggest you check the firewall whether the port is blocked. It would be helpful if you could share your service web.config and app.config for us.

    Best Regards,

    Edward


    Help each other

    Tuesday, June 21, 2016 2:14 AM
  • Hi Edward,

    Thanks for your reply. 

    Yes, I can able to browse the service successfully from the web browser(IE). 

    Yes, Error is only on one particular machine, and works fine in other machine. Even in that particular machine if we run fiddler in background there is no error and works as expected. 

    Below is the service app.config

    <?xml version="1.0"?>
    <configuration>
      <appSettings>
        <add key="ReleaseVersion" value="1.2"/>
        <add key="AppType" value="Windows"/> 
      </appSettings>
      <system.serviceModel>
        <bindings>
          <basicHttpBinding>
            <binding name="BasicHttpBinding_ICorridorDataService" />
     </basicHttpBinding>
        </bindings>
        <client>
          <endpoint address="http://60.234.30.70/Corridor/CorridorDataService.svc"
              binding="basicHttpBinding" bindingConfiguration="BasicHttpBinding_ICorridorDataService"
              contract="WinscribeService.ICorridorDataService" name="BasicHttpBinding_ICorridorDataService" />

        </client>
      </system.serviceModel>
    <startup><supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5"/></startup>
    </configuration>

    Hope this helps. 


    Regards, Gunarathinam.M

    Tuesday, June 21, 2016 12:01 PM
  • Rebuild the machine or replace it, because otherwise, you are looking for a needle in a haystack.

    Tuesday, June 21, 2016 2:18 PM
  • Hello,

    Based on your decription, I know that this error only happens on the particular machine, but it works fine in the others machine. So this issue is related with environment of this particular machine, then as @DA924x said, the most easy way is to replace this machine. Or you may need to compare the IIS setting on this particular machine with the IIS setting in others machines which can host the Service successful to see if you have done something wrong or different on this particular machine.

    Besides, you can also try to enable the WCF trace to see if there is any others clues.

    Best Regards,
    Amy Peng


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Tuesday, July 5, 2016 6:06 AM
    Moderator