October 25, 2018 at 3:46 pm
Hi all,
I'm on Microsoft SQL Server 2016 (SP1) (KB3182545) - 13.0.4001.0 (X64) and received the following SQL Server Stack Dumps. Needed to reboot the sql server service. Can someone advise how to avoid this going forward and what the root cause is for such exceptions? Sadly, I'm not an engineer at MS so there's not a lot I understand reading these dumps and error logs. Thank you very much!
2018-09-11 16:55:05.02 spid01 ***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\LOG\SQLDump0001.txt
2018-09-11 16:55:05.02 spid01 SqlDumpExceptionHandler: Process 59 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
2018-09-11 16:55:05.02 spid01 * *******************************************************************************
2018-09-11 16:55:05.02 spid01 * BEGIN STACK DUMP:2018-09-11 16:55:05.12 spid01 Stack Signature for the dump is 0x0000000149992398
2018-09-11 16:55:06.48 spid01 DumpCallbackHk::CreateCabFile: at 2059 g_CabDdfFile file is null, normally because nocollectors added any files, exiting
2018-09-11 16:55:06.48 spid01 DumpCallbackHk::CollectFiles: at 480 failed at CreateCabFile with error: 0x800040052018-09-11 16:55:06.48 spid01 DumpCallbackHk::CreateCabFile: at 2059 g_CabDdfFile file is null, normally because nocollectors added any files, exiting
2018-09-11 16:55:06.48 spid01 DumpCallbackHk::CollectFiles: at 480 failed at CreateCabFile with error: 0x80004005
2018-09-11 16:55:07.41 spid01 External dump process return code 0x20000001.
External dump process returned no errors.2018-09-11 16:55:07.42 Server Error: 17310, Severity: 20, State: 1.
2018-09-11 16:55:07.42 Server A user request from the session with SPID 01 generated a fatal exception. SQL Server is terminating this session. Contact Product Support Services with the dump produced in the log directory.2018-09-11 17:01:27.02 Server ***Unable to get thread context for spid 0
2018-09-11 17:01:27.02 Server * *******************************************************************************
2018-09-11 17:01:27.02 Server *
2018-09-11 17:01:27.02 Server * BEGIN STACK DUMP:
2018-09-11 17:01:27.02 Server * 09/11/18 17:01:27 spid 1800
2018-09-11 17:01:27.02 Server *
2018-09-11 17:01:27.02 Server * Non-yielding Scheduler
2018-09-11 17:01:27.02 Server *
2018-09-11 17:01:27.02 Server * *******************************************************************************
2018-09-11 17:01:27.02 Server Stack Signature for the dump is 0x0000000000000313
__________________________
Allzu viel ist ungesund...
October 25, 2018 at 8:29 pm
Mr. Holio - Thursday, October 25, 2018 3:46 PMHi all,I'm on Microsoft SQL Server 2016 (SP1) (KB3182545) - 13.0.4001.0 (X64) and received the following SQL Server Stack Dumps. Needed to reboot the sql server service. Can someone advise how to avoid this going forward and what the root cause is for such exceptions? Sadly, I'm not an engineer at MS so there's not a lot I understand reading these dumps and error logs. Thank you very much!
2018-09-11 16:55:05.02 spid01 ***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\LOG\SQLDump0001.txt
2018-09-11 16:55:05.02 spid01 SqlDumpExceptionHandler: Process 59 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
2018-09-11 16:55:05.02 spid01 * *******************************************************************************
2018-09-11 16:55:05.02 spid01 * BEGIN STACK DUMP:2018-09-11 16:55:05.12 spid01 Stack Signature for the dump is 0x0000000149992398
2018-09-11 16:55:06.48 spid01 DumpCallbackHk::CreateCabFile: at 2059 g_CabDdfFile file is null, normally because nocollectors added any files, exiting
2018-09-11 16:55:06.48 spid01 DumpCallbackHk::CollectFiles: at 480 failed at CreateCabFile with error: 0x800040052018-09-11 16:55:06.48 spid01 DumpCallbackHk::CreateCabFile: at 2059 g_CabDdfFile file is null, normally because nocollectors added any files, exiting
2018-09-11 16:55:06.48 spid01 DumpCallbackHk::CollectFiles: at 480 failed at CreateCabFile with error: 0x80004005
2018-09-11 16:55:07.41 spid01 External dump process return code 0x20000001.
External dump process returned no errors.2018-09-11 16:55:07.42 Server Error: 17310, Severity: 20, State: 1.
2018-09-11 16:55:07.42 Server A user request from the session with SPID 01 generated a fatal exception. SQL Server is terminating this session. Contact Product Support Services with the dump produced in the log directory.2018-09-11 17:01:27.02 Server ***Unable to get thread context for spid 0
2018-09-11 17:01:27.02 Server * *******************************************************************************
2018-09-11 17:01:27.02 Server *
2018-09-11 17:01:27.02 Server * BEGIN STACK DUMP:
2018-09-11 17:01:27.02 Server * 09/11/18 17:01:27 spid 1800
2018-09-11 17:01:27.02 Server *
2018-09-11 17:01:27.02 Server * Non-yielding Scheduler
2018-09-11 17:01:27.02 Server *
2018-09-11 17:01:27.02 Server * *******************************************************************************
2018-09-11 17:01:27.02 Server Stack Signature for the dump is 0x0000000000000313
There probably isn't enough information there for anyone to be able to offer much. Opening a case with Microsoft would be a good idea. They would probably first want the instance up to date with patches, updates as there have been fixes for different non-yielding scheduler issues.
You usually need to open the dump file using Windbg to get a good idea of what is going on. If you did want to try, this article has a good walk through for those particular issues:
How to analyze Non-Yielding scheduler or Non-yielding IOCP Listener dumps
He goes pretty in depth on walking through it but using Windbg and reading dump files is usually easier. Often times, you can open a dump file and just put: !analyze -v
in the command window and that will lead you to the file, driver, etc leading to the dump. Going through one for the non-yielding schedulers to figure out what happened is a bit different.
Sue
November 2, 2018 at 11:51 am
Thank you for your input!!
__________________________
Allzu viel ist ungesund...
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply