0

I have a WCF Service hosted on Azure. I can reach the service with WcfTestClient, but when I open the *.svc file in the browser it says "Server Not Found" and when I use the service from an MVC site it says "There was no endpoint listening at (url) that could accept the message". Both WcfTestClient and the MVC site are using BasicHttpBinding.

What does WcfTestClient do differently?

Without Haste
  • 507
  • 2
  • 6
  • Today, the browser is able to reach the svc and wsdl pages. I'm comparing the three lookup methods in Fiddler. The mvc site is complaining that the DNS lookup failed. – Without Haste Nov 08 '20 at 14:27
  • The DNS lookup failure was only because I have Fiddler open while running the site locally. I'm back to the System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at (url) that could accept the message. Inner exception System.Net.WebException: The remote name could not be resolved – Without Haste Nov 08 '20 at 14:32
  • This looks similar: https://stackoverflow.com/questions/25014110/system-net-webexception-the-remote-name-could-not-be-resolved – Without Haste Nov 08 '20 at 14:36
  • WcfTestClient is a GUI tool that enables users to input test parameters, submit that input to the service, and view the response that the service sends back. It provides a seamless service testing experience when combined with WCF Service Host. If other applications need to call WCF services, they need to generate proxy classes based on WSDL documents to call WCF services. – Ding Peng Nov 10 '20 at 03:08
  • WcfTestClient is nothing special, it is also a client. – Ding Peng Nov 10 '20 at 03:09
  • Once I added domain names to the Azure service and site, the site was able to access the service. So that's working now. But I still don't understand why the WcfTestClient could access the service at the default Azure url when the site couldn't. – Without Haste Nov 28 '20 at 14:04
  • I suspect it may be caused by the network failure. – Ding Peng Dec 03 '20 at 05:35

0 Answers0