Error accessing the SOAP API from a website hosted in IIS

Question

I have an application hosted on IIS in Windows Server 2012. At regular intervals, the site loses its ability to invoke the secure Api SOAP used in the application. This issue is resolved by restarting the website in IIS. But I can not restart the application at all points in time.

I get the following error message in Event Viewer and Application Error Log.

Event Viewer

The TLS protocol that defines the fatal warning code is 80.

Application Error Log

"Failed to establish secure channel for SSL / TLS with 'URL' privileges."

Windows Update did not install the well-known Microsoft SCHI-server SSL updates from Microsoft, which, as you know, generates this error.

Answer 1

If you are looking for the cause of the error:

Warning code 80 in TLS means:

Internal error: An internal error that is not related to the peer or the correctness of the protocol makes it impossible to continue, for example, a memory failure. The error is not related to the protocol. This message is always fatal.

It seems that it is incorrect in setting up the SOAP user interface, what cases might be:

• Memory consumption in the service: Checkout WCF - random client timeout when making several calls

• Something related to Throttling setup (upper limit of service call and optimization): you need to set the maximum simultaneous call for any hosted application. Make sure the value is greater than the required connections. Checkout a detailed study of WCF timeout exceptions

• Something is wrong with the server (memory leak in the application, less memory, other processes): Monitor Server is registered in Eventviewer for errors in the application.

• Waiting options for an application pool . Any managed application hosted on IIS uses an application pool, and the application pool has an Idle timeout. This means that if a hosting application for this AppPool is not used for a certain period of time (Idle time-out for AppPool), AppPool is processed to free resources. New calls after this require bringing AppPool, which takes longer than usual, which can lead to a timeout for some application if its timeout is less. Verify Configure idle wait wait settings for the application pool