September 18, 2020 at 8:36 am
SQL Version
Microsoft SQL Server 2017 (RTM-CU21) (KB4557397) - 14.0.3335.7 (X64) Jun 12 2020 20:39:00 Copyright (C) 2017 Microsoft Corporation Standard Edition (64-bit) on Windows Server 2016 Datacenter 10.0 <X64> (Build 14393: ) (Hypervisor)
Key SQL log entries
2020-09-11 12:12:18.25 spid247 **Dump thread - spid = 0, EC = 0x0000024F7D188040
2020-09-11 12:12:18.25 spid247 ***Stack Dump being sent to E:\PROD\MSSQL14.PROD\MSSQL\LOG\SQLDump0007.txt
2020-09-11 12:12:18.27 spid247 * *******************************************************************************
2020-09-11 12:12:18.27 spid247 *
2020-09-11 12:12:18.27 spid247 * BEGIN STACK DUMP:
2020-09-11 12:12:18.27 spid247 * 09/11/20 12:12:18 spid 247
2020-09-11 12:12:18.27 spid247 *
2020-09-11 12:12:18.27 spid247 * Location: tmpilb.cpp:2650
2020-09-11 12:12:18.27 spid247 * Expression: fFalse
2020-09-11 12:12:18.27 spid247 * SPID: 247
2020-09-11 12:12:18.27 spid247 * Process ID: 3576
2020-09-11 12:12:18.27 spid247 * Description: Attempt to access expired blob handle (1)
2020-09-11 12:12:18.27 spid247 *
2020-09-11 12:12:18.27 spid247 * Input Buffer 255 bytes -
2020-09-11 12:12:18.27 spid247 * X ÷ 16 00 00 00 12 00 00 00 02 00 58 01 00 00 f7 00 00 00
2020-09-11 12:12:18.27 spid247 * ÿÿ ç@ Ð 01 00 00 00 ff ff 0a 00 00 00 00 00 e7 40 1f 09 04 d0
2020-09-11 12:12:18.27 spid247 * 4Ö S E L E C T 00 34 d6 00 53 00 45 00 4c 00 45 00 43 00 54 00 20 00
2020-09-11 12:12:18.27 spid247 * o u _ i d F R O 6f 00 75 00 5f 00 69 00 64 00 20 00 46 00 52 00 4f 00
2020-09-11 12:12:18.27 spid247 * M f i r s t c a 4d 00 20 00 66 00 69 00 72 00 73 00 74 00 63 00 61 00
2020-09-11 12:12:18.27 spid247 * r e . o r g a n i 72 00 65 00 2e 00 6f 00 72 00 67 00 61 00 6e 00 69 00
2020-09-11 12:12:18.27 spid247 * s a t i o n a l _ 73 00 61 00 74 00 69 00 6f 00 6e 00 61 00 6c 00 5f 00
2020-09-11 12:12:18.27 spid247 * u n i t _ h i e r 75 00 6e 00 69 00 74 00 5f 00 68 00 69 00 65 00 72 00
2020-09-11 12:12:18.27 spid247 * a r c h y _ t r e 61 00 72 00 63 00 68 00 79 00 5f 00 74 00 72 00 65 00
2020-09-11 12:12:18.27 spid247 * e _ f i l t e r ( 65 00 5f 00 66 00 69 00 6c 00 74 00 65 00 72 00 28 00
2020-09-11 12:12:18.27 spid247 * @ P 0 , @ P 1 , 40 00 50 00 30 00 2c 00 20 00 40 00 50 00 31 00 2c 00
2020-09-11 12:12:18.27 spid247 * @ P 2 , @ P 3 20 00 40 00 50 00 32 00 2c 00 20 00 40 00 50 00 33 00
2020-09-11 12:12:18.27 spid247 * ) o r d e r b 29 00 20 00 6f 00 72 00 64 00 65 00 72 00 20 00 62 00
2020-09-11 12:12:18.27 spid247 * y h i d d e s 79 00 20 00 68 00 69 00 64 00 20 00 64 00 65 00 73 00
2020-09-11 12:12:18.27 spid247 * c ç@ Ð 4v @ P 63 00 00 00 e7 40 1f 09 04 d0 00 34 76 00 40 00 50 00
2020-09-11 12:12:18.27 spid247 * 0 b i g i n t , 30 00 20 00 62 00 69 00 67 00 69 00 6e 00 74 00 2c 00
2020-09-11 12:12:18.27 spid247 * @ P 1 n v a r c 40 00 50 00 31 00 20 00 6e 00 76 00 61 00 72 00 63 00
2020-09-11 12:12:18.27 spid247 * h a r ( 4 0 0 0 ) 68 00 61 00 72 00 28 00 34 00 30 00 30 00 30 00 29 00
2020-09-11 12:12:18.27 spid247 * , @ P 2 n v a r 2c 00 40 00 50 00 32 00 20 00 6e 00 76 00 61 00 72 00
2020-09-11 12:12:18.27 spid247 * c h a r ( 4 0 0 0 63 00 68 00 61 00 72 00 28 00 34 00 30 00 30 00 30 00
2020-09-11 12:12:18.27 spid247 * ) , @ P 3 b i g 29 00 2c 00 40 00 50 00 33 00 20 00 62 00 69 00 67 00
2020-09-11 12:12:18.27 spid247 * i n t & Ã 69 00 6e 00 74 00 00 00 26 08 08 c3 00 00 00 00 00 00
2020-09-11 12:12:18.27 spid247 * ç@ Ð 4 2 2 1 00 00 00 e7 40 1f 09 04 d0 00 34 0a 00 32 00 32 00 31
2020-09-11 12:12:18.27 spid247 * 8 1 ç@ Ð 4 2 00 38 00 31 00 00 00 e7 40 1f 09 04 d0 00 34 16 00 32
2020-09-11 12:12:18.27 spid247 * 2 2 7 9 , 2 2 2 8 00 32 00 32 00 37 00 39 00 2c 00 32 00 32 00 32 00 38
2020-09-11 12:12:18.27 spid247 * 7 & 4 00 37 00 00 00 26 08 08 34 02 00 00 00 00 00 00
2020-09-11 12:12:36.83 spid247 Error: 17065, Severity: 16, State: 1.
2020-09-11 12:12:36.83 spid247 SQL Server Assertion: File: <tmpilb.cpp>, line = 2650 Failed Assertion = 'fFalse' Attempt to access expired blob handle (1). 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.
Research
FOR XML clause together with the TYPE is NOT being used so not a cause (as suggested cause by other SQL posts).
SQL 2017 should already have this fix in it as seen articles this being fixed in earlier release of SQL.
A few days before this exception SQL 2017 Cumulative Update Package 21 was installed. Has this patch re-introduced this fault?
This error happened again (17th Sept) with the same tabular function (organisational_unit_hierarchy_tree_filter) with same error (Attempt to access expired blob handle) in same place (tmpilb.cpp:2650).
We have done tests on function passing in all NULLs to IN parameters and no SQL exception occurs.
DBCC DROPCLEANBUFFERS has been suggested to try but we do not feel this will help and will not run it.
DBCC CLEANTABLE has been suggested to try but we do not feel this will help and will not run it. Even if we did we would not know which table to run this command on.
DBCC CHECKDB has been suggested. We run this daily overnight. The night after this SQL exception showed no errors from running this command.
Does anyone have any ideas?
September 18, 2020 at 3:08 pm
My approach to this - what changed since this was working 100% of the time? If this was always working until you installed CU21, then it is likely a bug in CU21 OR in your tabular function.
Might not hurt to reach out to Microsoft on this for support as they will likely be the best suited to help you.
Are there any commonalities when it fails? Like does it always fail when a specific user runs that query OR always fail when you run it on Monday's between 6:00 and 6:15 AM? What I am thinking is that it could be some user specific thing (like if they are using SSMS 2008 to connect to the 2017 instance and it is a bug in SSMS 2008) OR there is some scheduled process running that is causing the blob handle to expire.
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply