Operational Defect Database

BugZero found this defect 340 days ago.

Microsoft SQL Server | 2346939

Fixes an assertion failure (Location: tmpilb.cpp:3540; Expression: RTL_ASSERTSZ(fFalse, "Attempt to access expired blob handle (1)")) and the following errors that you encounter when you run a common language runtime (CLR) stored procedure twice: Msg 3624, Level 20, State 1, Procedure <ProcedureName>, Line <LineNumber> [Batch Start Line <LineNumber>] 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. Msg 596, Level 21, State 1, Line <LineNumber> Cannot continue the execution because the session is in the kill state. Msg 0, Level 20, State 0, Line <LineNumber> A severe error occurred on the current command.  The results, if any, should be discarded.

Last update date:

6/15/2023

Affected products:

SQL Server 2019 on Linux

SQL Server 2019 on Windows

Affected releases:

build lower than 15.0.4316.3

Fixed releases:

15.0.4316.3

Description:

Fixes an assertion failure (Location: tmpilb.cpp:3540; Expression: RTL_ASSERTSZ(fFalse, "Attempt to access expired blob handle (1)")) and the following errors that you encounter when you run a common language runtime (CLR) stored procedure twice: Msg 3624, Level 20, State 1, Procedure <ProcedureName>, Line <LineNumber> [Batch Start Line <LineNumber>] 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. Msg 596, Level 21, State 1, Line <LineNumber> Cannot continue the execution because the session is in the kill state. Msg 0, Level 20, State 0, Line <LineNumber> A severe error occurred on the current command.  The results, if any, should be discarded.

Additional Resources / Links

Share:

BugZero® Risk Score

What's this?

Coming soon

Status

Unavailable

Learn More

Search:

...