question

Biltz avatar image
0 Votes"
Biltz asked SeeyaXi-msft commented

The query processor could not produce a query plan Error: 8624, Severity: 16, State: 21.

Hello,

We are running SQL Server 2019 RTM CU8-GDR. Yesterday, we noticed below error couple of times.

ex_dump_if_requested: Exception raised, major=86, minor=24, state=21, severity=16, attempting to create symptom dump
CImageHelper::Init () Version-specific dbghelp.dll is not used
Using 'dbghelp.dll' version '4.0.5'
Dump thread - spid = 0, EC = 0x00000F91A3B23CA0
Stack Dump being sent to H:\SQLROOT\MSSQL15.\MSSQL\LOG\SQLDump0003.txt
**
BEGIN STACK DUMP:
10/26/21 08:53:50 spid 853
ex_dump_if_requested: Exception raised, major=86, minor=24, state=21, severity=16
Input Buffer 255 bytes -
16 00 00 00 12 00 00 00 02 00 00 00 00 00 00 00 00 00
ÿÿ & ç 01 00 00 00 ff ff 0d 00 00 00 00 01 26 04 00 00 00 e7
ÿÿ þÿÿÿÿÿÿÿ@ ff ff 00 00 00 00 00 fe ff ff ff ff ff ff ff 40 00 00
@ P 1 n v a r c 00 40 00 50 00 31 00 20 00 6e 00 76 00 61 00 72 00 63



  • MODULE BASE END SIZE

  • sqlservr 00007FF70BAF0000 00007FF70BB8DFFF 0009e000

  • ntdll 00007FFCB56E0000 00007FFCB58CBFFF 001ec000

  • KERNEL32 00007FFCB29D0000 00007FFCB2A82FFF 000b3000

* KERNELBASE 00007FFCB1B30000 00007FFCB1DC3FFF 00294000






00007FFC7674755C Module(sqldk+000000000002755C)
00007FFC76747353 Module(sqldk+0000000000027353)
00007FFCB29E7974 Module(KERNEL32+0000000000017974)
00007FFCB573A2D1 Module(ntdll+000000000005A2D1)
Stack Signature for the dump is 0x00000001484DB916
External dump process return code 0x20000001.
External dump process returned no errors.

Error: 8624, Severity: 16, State: 21.
Internal Query Processor Error: The query processor could not produce a query plan. For more information, contact Customer Support Services.

Please suggest..

Thanks


sql-server-general
· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.


Probably you should also contact Customer Support Services.

Is it possible to reproduce the problem?


0 Votes 0 ·

Hi @Biltz ,

We have not received a response from you. Did the reply could help you? If the response helped, do "Accept Answer". If it doesn't work, please let us know the progress. By doing so, it will benefit all community members who are having this similar issue. Your contribution is highly appreciated.

Best regards,
Seeya

0 Votes 0 ·
SeeyaXi-msft avatar image
0 Votes"
SeeyaXi-msft answered ErlandSommarskog commented

Hi @Biltz ,

Error: 8624, Severity: 16, State: 21.

This error may appear in newer versions, so you can try lowering the compatibility level and try again. Compatibility level you can try one by one down.

USE MASTER
GO
ALTER DATABASE [YourDatabase] SET COMPATIBILITY_LEVEL = xxx
GO

Here is an article you can refer to: https://www.mssqltips.com/sqlservertip/5279/sql-server-error-query-processor-ran-out-of-internal-resources-and-could-not-produce-a-query-plan/ , which has other possible solutions.

Best regards,
Seeya

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

This error may appear in newer versions, so you can try lowering the compatibility level and try again. Compatibility level you can try one by one down.

That could help, that's true. But you are really giving this advice on the behalf of Microsoft? I mean, you are suggesting sweeping it all under the carpet.

When you get a stackdump like this, this has the smell of a bug.

I agree with Tom. Applu CU13 and test again. If error persists, open a support case.

0 Votes 0 ·
TomPhillips-1744 avatar image
0 Votes"
TomPhillips-1744 answered

These problems are almost always related to problems in the SQL Server code. I suggest you install the latest CU and retest.

https://support.microsoft.com/en-us/topic/kb4518398-sql-server-2019-build-versions-782ed548-1cd8-b5c3-a566-8b4f9e20293a

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.