search

kenakamu / UCWA2.0-CS

C# library for UCWA 2.0
MIT License
24 stars 13 forks source link

stop working after message received #65

Closed Valerii-Poliakov closed 5 years ago

Valerii-Poliakov commented 5 years ago

Hello

The client is unable to respond to the incoming message because of System.Net.Http.HttpRequestException. The issue was reported on Dec 12 in the customer environment. I reproduced this issue easily with our corporate S4B on-premise server. So seems it's a common problem for on-premise configuration. Until end of November 2018 everything worked perfectly. I asked about possible updates or patches and answer is: only latest Windows security patches were applied. Steps to reproduce:

  1. Client successfully signed in to the S4B on-premise and auto accept messages.
  2. User sends message to the client The last successful request is message.GetParticipant() in the MessageReceived handler: Client_MessageReceived(Message message). Any subsequent request fails with

System.Net.Http.HttpRequestException HResult=0x80131500 Message=An error occurred while sending the request. Source=Microsoft.Rest.ClientRuntime

Inner Exception 1: WebException: The underlying connection was closed: An unexpected error occurred on a send.

Inner Exception 2: IOException: Authentication failed because the remote party has closed the transport stream.

I'll appreciate any advice how to fix it.

Best Regards Valerii

Valerii-Poliakov commented 5 years ago

Resolved by changing .NET Framework version to 4.6.2