To work around the issue, you can change the database status to offline and online. Then, you will be able to reconfigure mirroring on the database successfully. Learn about the terminology that Microsoft uses to describe software updates.

Fixes an issue in which automatic failover doesn’t occur after database mirroring hangs.

Fixes a problem in which you receive error code 1456 when you try to add a witness to a database mirroring session in Microsoft SQL Server 2008 and in Microsoft SQL Server 2008 R2. This issue occurs when the database name is the same as an existing database mirroring session.

Assume that you are trying to upgrade a SQL Server 2016 mirrored instance to SQL Server 2017 by performing a rolling upgrade. After you complete upgrading, you may notice that the mirroring session is not able to synchronize. This may prevent you from completing the rolling upgrade.

Fixes an issue that triggers errors if database mirroring is configured by Transact-SQL in SQL Server 2016 and if no database activity occurs for more than 90 seconds.

Fixes some change tracking function issues and DMV issues that occur after an automatic database mirroring failover occurs in SQL Server 2008 R2 or in SQL Server 2008.

Fixes an issue in which the startup of a database that belongs to an availability group times out in SQL Server on Linux.

Fixes an assertion error issue after you establish a database mirroring session in SQL Server 2005 or SQL Server 2008 or SQL Server 2008 R2. The high-performance (asynchronous) mode is enabled in the database mirroring session.

When you add a witness to the new database mirroring session, you receive error 1456, and the witness is not added to the new database mirroring session. The fix for this issue was first released in Cumulative Update 10 for SQL Server 2008 Service Pack 1.

Fixes an issue that causes database mirroring failover to fail with error 3456 in SQL Server 2016 or 2017.