none
Random EndpointNotFoundException RRS feed

  • Question

  • Hello,

    I am developing a WCF 4.5 application were the domain server of the business is running the WCF service and 4 clients in the domain connecting to those service. The service that’s running on the server has quite a lot of endpoints published (more then 100). The service is hosted as a Windows Service, and the clients are communicating via net.tcp.

    At the moment I am receiving randomly a EndpointNotFoundException, sometimes it runs with no problems for a couple of hours, but usually the users are seeing this exception at least once a day.

    There is no particular endpoint that is causing this, its completely random.

     

    When the exception happens usually the user can’t login anymore because it will throw the EndpointNotFoundException again. The workaround that we have found that usually works is to disconnected the network adapter and reconnect again.

    This solves most of the time the problem for a couple of hours or a day.

     

    I studied the log files and the WCF tracing but can only see that the Endpoint was not found.

    I already enabled port sharing on the server and this caused less of these exceptions but they still exist.

     

    Can anyone suggest what might be the problem here, or how can I debug this to find the root cause?

     

    Thanks in advance.

     

    Marcel

    Thursday, August 10, 2017 11:32 AM

All replies

  • hello Marcel,

    I am guessing you have scoured the web and have found that others have encountered this:

    https://stackoverflow.com/questions/10125973/wcf-endpointnotfoundexception-after-running-for-a-couple-of-seconds

    https://stackoverflow.com/questions/24274187/how-do-i-resolve-a-wcf-random-endpoint-not-found-exception

    In combination with handling the underlying issue, I suggest you detect this error and perform a retry.  Here is an example,

    https://codereview.stackexchange.com/questions/41692/consistent-way-to-handle-transient-timeouts-with-wcf-calls-timeouts-unreliable

    You might find that this is sufficient (though not ideal).


    Cheers, Jeff

    Thursday, August 10, 2017 8:27 PM