none
SQL Server 2012 SP4 (+hotfixes) TLS 1.2 - The client and server cannot communicate because they do not possess a common algorithm RRS feed

  • Question

  • We have a new server that, for the moment, has to be on W2012R2/SQL2012. I have patched SQL Server right up to the latest levels and the server has been hardened to use TLS1.2 only. Most things are fine, but SCOM is failing to communicate and also the 'syspolicy_purge_history'  job is failing on the 'Erase Phantom System Health Records' step. Both are failing with 'The client and server cannot communicate because they do not possess a common algorithm'.

    As this is such an old version, is this expected? Do we have to accept the fact that we have to enable TLS1.0 for now? Responses appreciated, many thanks.

     
    Wednesday, December 11, 2019 10:24 AM

Answers

  • Resolved. Needed TLS1.2 reg key that hadn't been created automatically.
    • Marked as answer by Birley Wednesday, December 11, 2019 2:21 PM
    Wednesday, December 11, 2019 2:21 PM