Symptoms
Assume that you use a Transact-SQL statement to set database mirroring in SQL Server 2016. After this is configured, you see continuous errors that resemble the following in the SQL Server error log:
<Principal>
date time spid47s Error: 1479, Severity: 16, State: 1.
date time spid47s The mirroring connection to "TCP://Node02.contoso.com:5022" has timed out for database "MirrorDB" after 10 seconds without a response. Check the service and network connections.
date time spid47s Database mirroring is inactive for database 'MirrorDB'. This is an informational message only. No user action is required.
date time spid47s Database mirroring is active with database 'MirrorDB' as the principal copy. This is an informational message only. No user action is required.
</Principal>
<MIRROR>
date time spid53s Error: 1474, Severity: 16, State: 1.
date time spid53s Database mirroring connection error 4 'An error occurred while receiving data: '10054(An existing connection was forcibly closed by the remote host.)'.' for 'TCP://Node01.contoso.com:5022'.
date time spid44s Database mirroring is inactive for database 'MirrorDB'. This is an informational message only. No user action is required.
date time spid44s Database mirroring is active with database 'MirrorDB' as the mirror copy. This is an informational message only. No user action is required.
</MIRROR>
Cause
This error may be logged when the network is functioning correctly but the database has had no activity for 90 seconds. SQL Server checks and then closes the database mirroring connection when there is no database activity for 90 seconds. When database activities resume, a connection is reestablished, and database mirroring starts working again.
Resolution
The update that fixes this issue is included in the following cumulative updates:
-
Cumulative Update 1 for SQL Server 2016 Service Pack 1
-
Cumulative Update 4 for SQL Server 2016
About SQL Server 2016 builds
Each new build for SQL Server 2016 contains all the hotfixes and all the security fixes that were included with the previous build. We recommend that you install the latest build for SQL Server 2016.
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 terminologythat Microsoft uses to describe software updates.
