When Availability Group (AG) is failed over manually to another replica in Microsoft SQL Server 2016, an assertion occurs. The failover may succeed, but the databases from the earlier primary (now the secondary) where the AG was failed from, don't come online and generate the assertion dumps.
File: <"FilePath\FileName">, line=LineNumber Failed Assertion = 'inCorrectOrder'.
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:
To work around this issue, you may do the following:
Restart the SQL Server to mitigate the issue.
Drop the secondary replica and re-add it.
Learn about the terminology that Microsoft uses to describe software updates.