FIX: Assertion failure on secondary replica when you use AlwaysOn Availability Groups in SQL Server 2014

Applies to: SQL Server 2014 DeveloperSQL Server 2014 DeveloperSQL Server 2014 Enterprise

Symptoms


When you use the AlwaysOn Availability Groups feature in Microsoft SQL Server 2014, an assertion failure occurs on the secondary replica. Also, a dump file is generated in the SQL Server error log. The top of the dump report resembles the following:

* BEGIN STACK DUMP:

* <Date> <Time> spid <ID>

*

* Location: IAMPageRangeCache.cpp:515

* Expression: !m_needRefresh

Resolution


Cumulative update information

The issue was first fixed in the following cumulative update of SQL Server 2014:

Status


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