FIX: Resolving state occurs when an assertion occurs in SQL Server 2017

Applies to: SQL Server 2017 on Windows


Assume that you use SQL Server 2017. You may receive the following assertion at random times which is added to protect the transaction against a race condition betweena running procedure and a concurrent modification of the same procedure. When the assertion occurs, you may notice the side effects of lease time-out. In addition, Always On availability group (AG) and the primary database go into resolving state. After the fix, you receive error 41305 (Thecurrent transaction failed to commit due to a repeatable read validationfailure) instead of the assertion. As the error suggests, in this case, you should rerun the failed query.

CurrentTime spid SpidId 
Location:          "LocationPath":LocationId
Expression:       HK_E_ALTERED_TABLE_IS_MODIFIED != hr


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


This issue is fixed in the following cumulative update for SQL Server:
About cumulative updates for SQL Server:
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:


Learn about the terminology that Microsoft uses to describe software updates.