none
System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive. ---> System.ComponentModel.Win32Exception: The client and server cannot communicate, because they do not possess a common algorithm RRS feed

  • Question

  • We recently added a WFE to our SharePoint farm and we see that we are getting errors with Workflows running on BDC lists and using Secure store.On checking the logs in the WFE which looks like a communication error when requesting to the Securestoreservice WCF in the application server. On checking the registry, we see that TLS 1.2 is enabled in the new WFE but do not see similar registry structure for TLS 1.2 in the App Server to which the request is sent. We do not see the TLS 1.2 registry directory in the other existing WFE Servers as well

    Would help if somebody can provide a solution to the problem.

    Error Logs:

    Logging unknown/unexpected client side exception: CommunicationException. This will cause this application server to be removed from the load balancer queue. Exception: System.ServiceModel.CommunicationException: An error occurred while receiving the HTTP response to https://appspserver:32844/4c2988eb0b7b4f41bc2c3c5be3d31797/SecureStoreService.svc/https. This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details. ---> System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive. ---> System.ComponentModel.Win32Exception: The client and server cannot communicate, because they do not possess a common algorithm    

    Monday, September 16, 2019 5:07 PM

All replies

  • Sounds like TLS 1.2 is enforced and downlevel versions may be disabled. Have you applied the same keys to the other servers?

    Trevor Seward

    Office Apps and Services MVP



    Author, Deploying SharePoint 2019

    Author, Deploying SharePoint 2016

    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

    • Proposed as answer by Michael Han6 Wednesday, September 18, 2019 9:42 AM
    Monday, September 16, 2019 5:21 PM
    Moderator
  • Hi,

    If Trevor's reply is helpful to you, you could mark it as an answer.

    Best Regards,

    Michael Han


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    SharePoint Server 2019 has been released, you can click here to download it.
    Click here to learn new features. Visit the dedicated forum to share, explore and talk to experts about SharePoint Server 2019.

    Friday, September 20, 2019 9:24 AM