Communicationexception: Error in client making HTTP (HTTP.SYS) request to third party Webservice

Question

I’m developing for the eSocial for more than a year now, and, I am finding the following error in some customers, when trying to send to the service:

System.ServiceModel.Communicationexception:
Error making HTTP request to https://webservices.producaorestrita.esocial.gov.br/servicos/empregador/enviarloteeventos/WsEnviarLoteEventos.svc. This may be related to the fact that the server certificate is not properly configured with HTTP.SYS in the HTTPS case. This may also have been caused by an incompatibility of the security association between the client and the server.

  ---> System.Net.Webexception: The underlying connection was closed: Unexpected error in an upload.
    ---> System.IO.Ioexception: Unable to read transport connection data: Forced cancellation of an existing connection by remote host.
      ---> System.Net.Sockets.Socketexception: It was forced to cancel an existing connection by the remote host in System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, Socketflags socketFlags)...

On most computers the program is working perfectly, only on some computers this problem happens. My target platform is the . NET Framework 4.7.

I’ve answered two questions myself about this mistake here in the O.R.:

(1) Communication problems with the government-provided web service
(2) https communication error with Webservice

And from the research I’ve done, there are two solutions to the problem:

1. Set the property ServicePointManager.SecurityProtocol (https://stackoverflow.com/a/33084791/8133067);
2. Install Windows Update updates (https://stackoverflow.com/a/45494549).

In the case of the first solution: The eSocial service uses the security protocol TLS 1.2, but not always this is the default configuration of the machine. I’ve done this in the code and nay solved in most cases:

 ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls |
                                        SecurityProtocolType.Tls11 |
                                        SecurityProtocolType.Tls12;

In the case of the second solution: In the searches I did the problem could happen on outdated Windows 7 computers, and theoretically the update via Windows Update would solve, but in most cases did not solve, and I have already picked up some cases of this error in Windows 10.

I even did a test program, with the message log and the log of trace linked, to see if I could get some more information, but the only other thing I discovered (because of the tracing) is that the error occurs when the message is sent by the channel (communication with Webservice).

Follow the code I’m using to instantiate and call the service:

 const string UrlSvcBase = @"https://webservices.{0}.esocial.gov.br/servicos/empregador/{1}";
 string urlServico = String.Format(UrlSvcBase, "producaorestrita", @"enviarloteeventos/WsEnviarLoteEventos.svc");

 var address = new EndpointAddress(urlServico);
 //var binding = new BasicHttpBinding(BasicHttpsSecurityMode.Transport);
 var binding = new BasicHttpsBinding();  //Disponível desde .NET Framework 4.5
 binding.Security.Transport.ClientCredentialType = HttpClientCredentialType.Certificate;
 // Manual de Orientação do Desenvolvedor v1.4, página 39, item '5.4.5. Validações aplicadas':
 // "O tamanho limite da mensagem SOAP é 750 kbytes."
 // O valor padrão da propriedade MaxReceivedMessageSize é 65.536,
 // que é alterado então para 750 KB * 1024 = 768.000 bytes.
 // Caso contrário, ocorre a exceção:
 //   Exception: System.ServiceModel.CommunicationException
 //   InnerException: System.Exception {System.ServiceModel.QuotaExceededException}
 //   "The maximum message size quota for incoming messages (65536) has been exceeded.
 //    To increase the quota, use the MaxReceivedMessageSize property on the appropriate binding element."  
 //   HResult: -2146233087 (0x80131501)
 binding.MaxReceivedMessageSize = 768000;

 ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls |
                                        SecurityProtocolType.Tls11 |
                                        SecurityProtocolType.Tls12;

 var wsClient = new WsEnviar.ServicoEnviarLoteEventosClient(binding, address);
 // Variável 'certificado' é do tipo X509Certificate2.
 wsClient.ClientCredentials.ClientCertificate.Certificate = certificado;

 wsClient.Open();
 // Variavel 'lote' é do tipo XElement.
 var retorno = wsClient.EnviarLoteEventos(lote);
 wsClient.Close();

Does anyone have any idea what might cause this mistake, or any idea what else I can do to try to figure out the cause of the problem?

Answer 1

According to the @Eprogrammernotfound comment, it seems to be a.NET bug. The same thing happened to me when transmitting E-finance to Webservice SPED on some Windows 7 and Windows 2008 machines.

I ended up creating a routine that creates a Stack with the protocols I want to use (TLS 1.0, TLS 1.1. and TLS 1.2). Then I will unpacking and assigning one protocol at a time and I will try to send. If it fails, step to the next protocol:

ServicePointManager.SecurityProtocol = (SecurityProtocolType) 0;    

// Pilha com protocolos que vou utilizar
Stack<SecurityProtocolType> protocolosDisponiveis = new Stack<SecurityProtocolType>();
protocolosDisponiveis.Push(SecurityProtocolType.Tls);
protocolosDisponiveis.Push((SecurityProtocolType)768); // TLS 1.1
protocolosDisponiveis.Push((SecurityProtocolType)3072); // TLS 1.2.
var TentarNovamente = false;

do
{
    ServicePointManager.SecurityProtocol = this.protocolosDisponiveis.Pop();

    try
    {
        // Tenta chamar o serviço se der certo ok eu saio fora
        ChamarServico();
        TentarNovamente = false;
    }
    catch (CommunicationException ex)
    {
        TentarNovamente = true;

    }
}
while(TentarNovamente && protocolosDisponiveis.Count() > 0);