It may be a shot in the dark (I know little about internal WCF), but here it goes ...
I am currently working with an outdated application on a client site, and we are faced with a constant problem with the WCF service. The application uses Microsoft Sync Framework 2.0 and synchronization using the above service. The server implementation of the service has a lot of custom code in different "mess" states.
In any case, we see an error in the client application most of the time, and the template that we are reducing focuses on different users using the application on the same computer as the same service. It seems that the service and the client are somehow not synchronizing at the authentication level.
The error is discussed in the article here , and we are currently exploring the approach of moving from message-level security to transport-level security, which I hope will solve the problem. However, we can solve it in a less invasive way if this question makes sense.
In a related article, one suggestion was to force the connection to terminate, if a specific exception is caught, try again, and if it does not work again, this was not due to this particular theory. Sounds good and easy to implement. However, I cannot say with certainty that the connection is completed correctly.
, . , , - EndSession() -, EndSession() , .
...
WCF , ?
, EndSession() - , , , ? , , , .
, , EndSession(), -, factory . , - ( WCF ), ?
, . , , / , , , . .