WCF End point not found error from self-hosted service

Question

i´m getting an "End point not found" when calling a WCF service. It is a Self-hosted service in a console app.

Here is my code:

IService.cs

namespace ClassLibrary
{
[ServiceContract]
public interface IService
{
    [OperationContract]
    [WebGet]
    string GetMessage(string inputMessage);

    [OperationContract]
    [WebInvoke]
    string PostMessage(string inputMessage);
}

}

Service.cs

namespace ClassLibrary
{
public class Service : IService
{
    public string GetMessage(string inputMessage)
    {
        return "En GetMessage llega " + inputMessage;
    }

    public string PostMessage(string inputMessage)
    {
        return "En PostMessage llega " + inputMessage;
    }
}

}

And the console app:

namespace ConsoleHost
{
class Program
{
    static void Main(string[] args)
    {            
        WebServiceHost host = new WebServiceHost(typeof(Service), new Uri("http://localhost:8000"));
        ServiceEndpoint ep = host.AddServiceEndpoint(typeof(IService), new WebHttpBinding(), "");
        ServiceDebugBehavior db = host.Description.Behaviors.Find<ServiceDebugBehavior>();
        db.HttpHelpPageEnabled = false;

        ServiceMetadataBehavior smb = new ServiceMetadataBehavior();
        smb.HttpGetEnabled = true;
        host.Description.Behaviors.Add(smb);

        host.Open();
        Console.WriteLine("Service is up and running");
        Console.WriteLine("Press enter to quit ");
        Console.ReadLine();
        host.Close();
    }
}

}

There is no config file because it is all in the code.

And the call to the service:

http://localhost:8000/

Any help would be much appreciated. Thanks!

It may be helpful to share some config too: WCF errors are notoriously configuration dependent. — Bob Tway, May 12 '14 at 14:15
Can you share client code too? Do you use same endpoint configuration on the client (WebHttpBinding)? — Sasha, May 12 '14 at 14:17
Why are you creating a `ServiceEndpoint ep` and not doing anything with it? It's an unused variable. — Rick S, May 12 '14 at 14:24

score 1 · Accepted Answer · answered May 12 '14 at 15:11

Couple of things. Services hosted with WebServiceHost do not publish metadata, so don't bother trying to get a WSDL with just the service name.

Because its WebGet, you are calling the Get method by default when you enter the service name, so you should supply any needed parameters in the URL. However, this won't work until you declare the form of the request in the contract. Do this by modifying the the WebGet line as follows:

[WebGet(UriTemplate = "{inputMessage}")]

Yes, the attribute property must match the formal parameter of the GetMessage() operation, in this case "inputMessage"

With the service running, enter the following URL into a browser to verify the service works:

http://localhost:8000/hello

You should get something like:

<string xmlns="http://schemas.microsoft.com/2003/10/Serialization/">
En GetMessage llega hello</string>

score 0 · Answer 2 · edited May 23 '17 at 12:21

0

I find this for you WCF REST Self-Hosted 400 Bad Request Effectively you are developping a REST Service, and for this there are two things to know: 1- You don't need to add EndPoint and Behaviors when using WebServiceHost 2- Rest Services don't have wsdl exposed, so you can't add a service refenrence from VS for example.

edited May 23 '17 at 12:21

Community

1
1

answered May 12 '14 at 14:26

DadyFuji

243
1
12

WCF End point not found error from self-hosted service

2 Answers2