EndpointNotFoundException : There was no endpoint listening?

  • Thread starter Thread starter Yash
  • Start date Start date
When I access the service in IE, using this URLhttps://lap442/WCF/MyService.svc
I get a descriptive page which means the service is working fine.
When I inspect the IIS logs, it shows:
15:11:35 127.0.0.1 GET /WCF/MyService.svc 200

When I access the service through a client app, I get an error in the
client that says:
"There was no endpoint listening athttps://lap442/WCF/MyService.svc"

The Exception is:
"There was no endpoint listening athttps://lap442/WCF/MyService.svc
that could accept the message. This is often caused by an incorrect
address or SOAP action. See InnerException, if present, for more
details."}

The inner exception is:
{"The remote server returned an error: (404) Not Found."}

When I inspect the IIS logs, it shows:
15:26:06 127.0.0.1 POST /WCF/MyService.svc 404

What could be the reason behind such an error. What changes do I need
to make in the config.
Click to expand...

This is probably not much help, but looking at the IIS logs, your
client app is doing a POST where the IE browser is doing a GET.
Probably your endpoint is not configured for POST requests. If you're
not posting any data to the service, you could try and change the
client app so it does a GET instead of a POST. Or you could configure
your service to accept POST requests. This should just be a pretty
simple configuration change (not something I've done though, sorry).
 
I think all requests HAVE to be POSTs as the SOAP request needs to be
POSTed. I have tried this with basicHttpBinding and it works. The logs
show a POST request and the client gets the correct data.
 
Back
Top