Polybase issue about continuous producing of dump files - SQL Server 2019

pmscorca 792 Reputation points
2021-03-27T07:03:45.177+00:00

Hi,

on my machine I've a SQL Server 2019.
Recently, I've noticed that the available storage on the main hard disk is reduced drastically.
I've tried to move more file on an external unit, but after some hours the available space is allocated again.
Investigating about this issue, I've noticed that in the C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\Log\Polybase\dump folder some daily dump files are created,
each file with about 500 MB as dimensions.

Below I put what today it is written in the SQLDUMPER_ERRORLOG.log file (at C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\Log\Polybase\dump folder)

(402C:53D4) 03/27/21 07:25:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, AdjustTokenPrivileges () completed with status (00000514)
(402C:53D4) 03/27/21 07:25:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
(402C:53D4) 03/27/21 07:25:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 1: 6204
(402C:53D4) 03/27/21 07:25:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 2: 0
(402C:53D4) 03/27/21 07:25:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 3: 0:0
(402C:53D4) 03/27/21 07:25:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 4: 00007FF72F82B360
(402C:53D4) 03/27/21 07:25:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
(402C:53D4) 03/27/21 07:25:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID = 6204
(402C:53D4) 03/27/21 07:25:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
(402C:53D4) 03/27/21 07:25:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
(402C:53D4) 03/27/21 07:25:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags = 0x0
(402C:53D4) 03/27/21 07:25:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr = 0x00007FF72F82B360
(402C:53D4) 03/27/21 07:25:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir = <NULL>
(402C:53D4) 03/27/21 07:25:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExceptionRecordPtr = 0x0000000000000000
(402C:53D4) 03/27/21 07:25:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr = 0x0000000000000000
(402C:53D4) 03/27/21 07:25:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile = <NULL>
(402C:53D4) 03/27/21 07:25:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, PatternForExtraFiles = <NULL>
(402C:53D4) 03/27/21 07:25:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName = <NULL>
(402C:53D4) 03/27/21 07:25:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName = <NULL>
(402C:53D4) 03/27/21 07:25:36, ERROR , mpdwsvc.exe, String at 000002941F177110 was not NULL terminated
(402C:53D4) 03/27/21 07:25:36, ACTION, mpdwsvc.exe, Remote process didn't specify a dump file name
(402C:53D4) 03/27/21 07:25:36, ACTION, mpdwsvc.exe, MINIDUMP_TYPE: 0x21966
(402C:53D4) 03/27/21 07:25:36, ACTION, mpdwsvc.exe, Callback type 16 not used
(402C:53D4) 03/27/21 07:25:36, ACTION, mpdwsvc.exe, Callback type 17 not used
(402C:53D4) 03/27/21 07:25:36, ACTION, mpdwsvc.exe, Callback type 11 not used
(402C:53D4) 03/27/21 07:25:36, ACTION, mpdwsvc.exe, Callback type 15 not used
(402C:53D4) 03/27/21 07:25:37, ACTION, mpdwsvc.exe, Callback type 7 not used
(402C:53D4) 03/27/21 07:25:37, ACTION, mpdwsvc.exe, MiniDump completed: C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\Log\Polybase\dump\SQLDmpr.00000000E4719325.GMT-2021-03-27-06-00-00.dmp
(402C:53D4) 03/27/21 07:25:37, ACTION, mpdwsvc.exe, Total Buffer pool data pages filtered out: 0 KB
(402C:53D4) 03/27/21 07:25:37, ACTION, mpdwsvc.exe, Total Hekaton data pages filtered out: 0 KB
(402C:53D4) 03/27/21 07:25:37, ACTION, mpdwsvc.exe, Total Free memory (from non top level allocators) filtered out: 0 KB
(402C:53D4) 03/27/21 07:25:37, ACTION, mpdwsvc.exe, Total top level free memory filtered out: 0 KB
(402C:53D4) 03/27/21 07:25:37, ACTION, mpdwsvc.exe, Total Log pool memory filtered out: 0 KB
(402C:53D4) 03/27/21 07:25:37, ACTION, mpdwsvc.exe, Should columnstore object pool be included in filtered dump= 0
(402C:53D4) 03/27/21 07:25:37, ACTION, mpdwsvc.exe, Should columnstore blob cache be included in filtered dump= 0
(402C:53D4) 03/27/21 07:25:37, ACTION, mpdwsvc.exe, Total columnstore object pool memory filtered out: 0 KB
(402C:53D4) 03/27/21 07:25:37, ACTION, mpdwsvc.exe, Total columnstore blob cache filtered out: 0 KB
(402C:53D4) 03/27/21 07:25:37, ACTION, mpdwsvc.exe, Total pages filtered out by bitmap: 0 KB
(402C:53D4) 03/27/21 07:25:37, ACTION, mpdwsvc.exe, Total file mapped memory filtered out: 0 KB
(402C:53D4) 03/27/21 07:25:37, ACTION, mpdwsvc.exe, Location of module 'dbghelp.dll' : 'C:\Windows\SYSTEM32\dbghelp.dll'
(402C:53D4) 03/27/21 07:25:37, ACTION, mpdwsvc.exe, File version of module 'C:\Windows\SYSTEM32\dbghelp.dll' : '6.2:19041.867'
(402C:53D4) 03/27/21 07:25:37, ACTION, mpdwsvc.exe, Product version of module 'C:\Windows\SYSTEM32\dbghelp.dll' : '10.0:19041.867'
(402C:53D4) 03/27/21 07:25:37, ACTION, mpdwsvc.exe, Location of module 'sqldumper.exe' : 'C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\Binn\Polybase\SQLDUMPER.EXE'
(402C:53D4) 03/27/21 07:25:37, ACTION, mpdwsvc.exe, File version of module 'C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\Binn\Polybase\SQLDUMPER.EXE' : '2019.150:2000.5'
(402C:53D4) 03/27/21 07:25:37, ACTION, mpdwsvc.exe, Product version of module 'C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\Binn\Polybase\SQLDUMPER.EXE' : '15.0:2000.5'
(402C:53D4) 03/27/21 07:25:37, ACTION, mpdwsvc.exe, Send_To_Watson flag is set to true
(402C:53D4) 03/27/21 07:25:37, ACTION, mpdwsvc.exe, Force_Watson flag is set to true
(402C:53D4) 03/27/21 07:25:37, ACTION, mpdwsvc.exe, Watson Invoke: Yes
(402C:53D4) 03/27/21 07:25:37, ACTION, mpdwsvc.exe, Creating WER report...
(402C:53D4) 03/27/21 07:25:37, ACTION, mpdwsvc.exe, Created the report.
(402C:53D4) 03/27/21 07:25:37, ACTION, mpdwsvc.exe, WerReportAddFile Mini Dump succeeded.
(402C:53D4) 03/27/21 07:25:37, ACTION, mpdwsvc.exe, Submitting WER report...
(402C:53D4) 03/27/21 07:25:39, ACTION, mpdwsvc.exe, Submitted report synchronously.

Now, any helps to me in order to solve this severe issue, please? Many thanks

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
12,654 questions
Accepted answer
  1. Vaibhav Chaudhari 38,561 Reputation points
    2021-03-27T08:09:24.517+00:00

    It should be due to some errors with polybase or sql setup.

    See this blog can help in fixing it -

    https://nielsberglund.com/2019/11/20/fix-polybase-in-sql-server-2019-developers-edition/

    https://blog.sqlauthority.com/2017/11/08/sql-server-many-sqldump-files-consuming-lot-disk-space/

    Please don't forget to Accept Answer and Up-vote if the response helped -- Vaibhav

    0 comments

3 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Elias 6 Reputation points
    2021-11-09T08:01:21.747+00:00

    Hi all,

    I solved this by stopping Poly database services via SQL configuration tool, because i dont't use Poly DB functions.

    147568-2021-11-09-08-52-35-sql-server-configuration-manag.png

    1 person found this answer helpful.
  2. Erland Sommarskog 100.8K Reputation points MVP
    2021-03-27T09:47:22.477+00:00

    This is a known issue which has been resolved. Install the latest Cumulative Update, CU9, to resolve this problem. https://www.microsoft.com/en-us/download/details.aspx?id=100809

  3. CathyJi-MSFT 21,081 Reputation points Microsoft Vendor
    2021-03-29T02:58:12.95+00:00

    Hi @pmscorca ,

    Your issue is same as this thread ms sql 2019 community polybase log file filling up disk drive, please try the suggestion from this thread.

    If the response is helpful, please click "Accept Answer" and upvote it, thank you.

    0 comments