FIX: Cannot connect to a named instance after failover on a mirror server in SQL Server 2014 or 2016

Symptoms

Consider the following scenario:

  • You use the Microsoft ODBC Driver for SQL Server and the Microsoft SQL Server Native Client 11.0 that is installed when you install SQL Server 2014 or 2016.

  • You connect to a named instance of SQL Server 2014 or 2016 that is running database mirroring.

  • Failover of the named instance occurs from the principal server to the mirror server.

In this scenario, when you hide the named instance or you stop using the SQL Server Browser service, you cannot connect to the named instance on the mirror server.

Resolution

To resolve this issue, install the following cumulative updateand ODBC driver for your version of SQL Server.Note Although the driver is included in the cumulative updates forSQL Server 2014, you must install the driver separately for all versions.

Cumulative update

Cumulative Update 4 for SQL Server 2016

Cumulative Update 4 for SQL Server 2014 SP2

Cumulative Update 11 for SQL Server 2014 SP1


ODBC driver

SQL 2016: ODBC Driver 13.1 

SQL 2014: ODBC Driver 11


Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:

Latest cumulative update for SQL Server 2016

Latest cumulative update for SQL Server 2014

Workaround

To work around this issue, restart the SQL Server Browser service.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

References

Learn about the terminology Microsoft uses to describe software updates.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×