SQL Server 2012 will not mirror RRS feed

  • Question

  • We had a SQL 2012 Database on Windows Server 2008 and it was mirrored over to SQL 2012 on another Windows Server 2008.

    We upgrade the destination server to Windows server 2012. We removed TLS 1.0 and TLS 1.1 on the Destination server (to resolve browser issues when accessing our Website on IIS).  In the process the database mirror stopped working. When trying to setup the mirror it will not complete.

    We have applied all the SQL service packs and updates on both servers.

    David Dobson

    Tuesday, May 26, 2020 10:09 PM

All replies

  • When establishing the mirror and connecting to the destination server we get this error”

    Cannot connect to MCSS5.

    Additional information:

    Failed to connect to server MCSS5 ( Microsoft.SQLServer.ConnectionInfo)

    A connection was successfully established with the server, then then an error occurred during the Login process. (Provider SSL:, error: 0 – an existing connection was forcibly close by

    The remote host. Microsoft SQL server, Error:10054)

                    An existing connection was forcibly closed by the remote host:

    David Dobson

    Tuesday, May 26, 2020 10:25 PM
  • Hi David,

    The problem should be caused by disabling TLS1.0 and TLS1.1 after you upgrading the destination server to Windows 2012.

    Can you use SSMS on the source server to connect to this destination server remotely? Or get the same error?

    Since you disable TLS 1.0 and TLS 1.1, do you want to use TLS 1.2 or SSL protocol?

    So you need to check your SSL and TLS settings. The settings between them should be somewhat consistent.
    Updating to a build that supports TLS 1.2 might resolve your issue.

    Also check following articles:
    TLS 1.2 support for Microsoft SQL Server

    How to disable weak versions of SSL/TLS Protocols on Windows Servers

    TLS1.0 missing from Windows 2008 protocols

    Best Regards,

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Wednesday, May 27, 2020 4:00 AM