Possible bug in SQL Server 2019 with a workaround

Question

Hi Microsoft Support,

Symptoms : We have SQL server 2019 Enterprise Edition with Cumulative Update 16. During execution of a very simple stored procedure which just runs a simple select query, we got the error message “Attempt to access expired blob handle (1)”

Status: According to KB4540346 It happens in SQL 2019 when a merge statement is executed and the issue is fixed in CU4

Scenario : In our case we were running a simple select statement from one table and we have CU16 installed

Workaround : Restart the SQL services resolved the issue

Please advise

Regards

Qamar

Answer 1

This is not the place to open support tickets. This is a peer-to-peer forum for help with SQL Server. What we can do here is evaluate if it really is a bug, or if you may be doing something wrong. I would say in this, you most likely have encountered a bug in SQL Server. Although, run DBCC CHECKDB, as it could be token of corruption.

If you only want Microsoft know about the issue (because you have a workaround), you can report it on https://feedback.azure.com/forums/908035-sql-server. But the information you included is useless for a bug report. Microsoft would need a full repro that demonstrates the issue.

If this is a blocking isse for you and you need a fix, you must open a support case. Most likely you will be charged initially, but if it is confirmed to be a bug, you will be refunded.

Answer 2

Hi @Qamar Jamal - IT ,
Like you said and according to this official article, the problem can be fixed by upgrading.And here is the link: https://support.microsoft.com/en-us/topic/kb4540346-fix-merge-statement-fails-with-assert-attempt-to-access-expired-blob-handle-1-in-sql-server-2016-2017-and-2019-63c74917-1bc4-838d-5cb5-05b7e5a8340d.
Actullay im not sure if you have already solved the problem. If you just want to give advise to Microsoft you can try and follow the step of the @Erland Sommarskog 's answer.

Answer 3

Hi @Qamar Jamal - IT ,
How about the problem? :)

Answer 4

Thank you guys for the reply. I haven't encountered the issue after I restart the SQL services. I was looking to report it to Microsoft but didn't find a forum where I can report. I don't want to spend $499 just to report it :(

Answer 5

Hi @Qamar Jamal - IT
Here is the link: https://feedback.azure.com/forums/908035-sql-server
You can feed back in this link. And SQL test team can see it and help to deal with. If the requirement mentioned by customers for many times, the product team may consider to add this feature in the next SQL Server version. Your feedback is valuable for us to improve our products and increase the level of service provided.

And if you think my answer is helpful you can mark it, which can be helpful for both community and other users! ^_~