Problem description: We got some mini memory dump. In side our SQL error log, we can see the error message below
Stack Signature for the dump is 0x00000000950A8E26
External dump process return code 0x20000001.
External dump process returned no errors.Error: 8624, Severity: 16, State: 116.
Internal Query Processor Error: The query processor could not produce a query plan. For more information, contact Customer Support Services.
ex_raise2: Exception raised, major=86, minor=24, state=116,
severity=16, attempting to create symptom dump
ex_raise2: Exception raised, major=86, minor=24, state=116, severity=16
Interesting link: We found out a similar issue. However, I am in SQL Server 2005 SP4 (9.00.5000.00 (X64)), and the issue below was fixed in SQL 2005 SP2. E.G. FIX: Error message when you run a query in Microsoft SQL Server 2005: “Msg 8624, Level 16, State 116 Internal Query Processor Error: The query processor could not produce a query plan”
Cause: We got the query from the dump, but you could also get the query with a profiler trace with the events TSQL SQL:BatchCompleted or Stored procedure RPC:Completed with Error and Waring Exception. We the query we are able to reproduce the issue each time. We saw that the dump was generated by statistics stream corrupted (spotted that in the generation script of the objects)
Resolution: We run an update statitics with fullscan to solve the issue on all objects called by the query.We run again the query and the issue didn’t occur.
Michel Degremont | Premier Field Engineer – SQL Server Core Engineer |