debugsqlMinor
SQL AG flip. SQL 2019 cu14 SQL server Error <"interop.cpp">, line=125 Failed Assertion = 'nullptr != error' ,
Viewed 0 times
interoperrorassertionfliplinesql2019cppnullptrfailed
Problem
Has anyone else has seen this, Or knows anything else i should look for.
I'm getting an error on our sql server, the error will happen, then about 50% of the time the SQL cluster service will fail. Causing the AG to flip to the other server. I've created a case as a suspect it's a bug, but i haven't heard back yet.
I have restarted, and run a checkdb on all the databases.
Error Messages:
Date 1/24/2022 4:21:53 PM
Log SQL Server (Current - 1/24/2022 5:10:00 PM)
Source spid1063
Message
SQL Server Assertion: File: , line=125 Failed Assertion = 'nullptr != error'. This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted.
Date 1/24/2022 4:21:53 PM
Log SQL Server (Current - 1/24/2022 5:10:00 PM)
Source spid1063
Message
A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a Hotfix from Technical Support.
Edit: adding some details. 15.0.4188.2, SQL AG on 3 server, in Asynchronies, Manual failover. Memory optimized Temp DB is on. These two windows events match with the timing of the sql events.
Windows Server Failover Cluster did not receive a process event signal from SQL Server hosting availability group 'AG' within the lease timeout period.
The lease between availability group 'AG' and the Windows Server Failover Cluster has expired. A connectivity issue occurred between the instance of SQL Server and the Windows Server Failover Cluster. To determine whether the availability group is failing over correctly, check the correspo
I'm getting an error on our sql server, the error will happen, then about 50% of the time the SQL cluster service will fail. Causing the AG to flip to the other server. I've created a case as a suspect it's a bug, but i haven't heard back yet.
I have restarted, and run a checkdb on all the databases.
Error Messages:
Date 1/24/2022 4:21:53 PM
Log SQL Server (Current - 1/24/2022 5:10:00 PM)
Source spid1063
Message
SQL Server Assertion: File: , line=125 Failed Assertion = 'nullptr != error'. This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted.
Date 1/24/2022 4:21:53 PM
Log SQL Server (Current - 1/24/2022 5:10:00 PM)
Source spid1063
Message
A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a Hotfix from Technical Support.
Edit: adding some details. 15.0.4188.2, SQL AG on 3 server, in Asynchronies, Manual failover. Memory optimized Temp DB is on. These two windows events match with the timing of the sql events.
Windows Server Failover Cluster did not receive a process event signal from SQL Server hosting availability group 'AG' within the lease timeout period.
The lease between availability group 'AG' and the Windows Server Failover Cluster has expired. A connectivity issue occurred between the instance of SQL Server and the Windows Server Failover Cluster. To determine whether the availability group is failing over correctly, check the correspo
Solution
It's an issue and should be fixed in an upcoming patch. In the interim you can disable in memory optimized TempDB and that should solve the issue (until the patch, then you can turn it back on).
The reason the AG fails is due to the checks failing as the application threads are frozen for the duration of the dump generation, thus they won't respond and either the lease or the *alive checks will fail.
The reason the AG fails is due to the checks failing as the application threads are frozen for the duration of the dump generation, thus they won't respond and either the lease or the *alive checks will fail.
Context
StackExchange Database Administrators Q#306555, answer score: 6
Revisions (0)
No revisions yet.