Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

FIX: DBCC STACKDUMP doesn't generate dump file for SQL Server 2017 on Linux starting from SQL Server 2017 CU9 to CU13


View products that this article applies to.

Symptoms

Assume that you have SQL Server 2017 on Linux installed. When you use DBCC STACKDUMP command to generate a SQLDUMPER.EXE initiated dump starting from Cumulative Update 9 (CU 9) for SQL Server 2017 to Cumulative Update 13 (CU 13) for SQL Server 2017, you may notice that it doesn't work.

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. 

↑ Back to the top


Resolution

This issue is fixed in the following cumulative update for SQL Server:

About cumulative updates for SQL Server:

Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:

↑ Back to the top


More Information

For more information, see How to use DBCC STACKDUMP.

↑ Back to the top


References

Learn about the terminology that Microsoft uses to describe software updates.

↑ Back to the top


Keywords: DBCC STACKDUMP cannot generate SQLDUMPER.EXE, kb, kbfix, kbqfe, kbHotfixAuto, CI98046

↑ Back to the top

Article Info
Article ID : 4490799
Revision : 8
Created on : 3/25/2019
Published on : 3/25/2019
Exists online : False
Views : 134