SQLDUMPER_ERRORLOG.log

  • Rajesh.KB

    SSC Veteran

    Points: 283

    Hi everybody, i'm getting one dump file when i run SSIS package. Any idea about how SQLDUMPER_ERRORLOG.log file is creating? Content in the file is given below

    04/02/09 06:04:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied

    04/02/09 06:04:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID = 3180

    04/02/09 06:04:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0

    04/02/09 06:04:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0

    04/02/09 06:04:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags = 0x0

    04/02/09 06:04:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr = 0x0100A530

    04/02/09 06:04:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir =

    04/02/09 06:04:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExceptionRecordPtr = 0x00000000

    04/02/09 06:04:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr = 0x00000000

    04/02/09 06:04:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile =

    04/02/09 06:04:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName =

    04/02/09 06:04:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName =

    04/02/09 06:04:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used

    04/02/09 06:04:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used

    04/02/09 06:04:02, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used

    04/02/09 06:04:02, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files (x86)\Microsoft SQL Server\90\Shared\ErrorDumps\SQLDmpr0002.mdmp

    04/02/09 06:04:02, ACTION, DTExec.exe, Watson Invoke: No

  • nahk.fussuy

    SSC Eights!

    Points: 982

    Hi Raj,

    Did you ever find out an answer to your problem? I'm getting the same thing with a production server. Exact same contents (except for processID and filename of course)

    09/23/09 10:15:35, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied

    09/23/09 10:15:35, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID = 6788

    09/23/09 10:15:35, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0

    09/23/09 10:15:35, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0

    09/23/09 10:15:35, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags = 0x0

    09/23/09 10:15:35, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr = 0x0100A530

    09/23/09 10:15:35, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir =

    09/23/09 10:15:35, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExceptionRecordPtr = 0x00000000

    09/23/09 10:15:35, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr = 0x00000000

    09/23/09 10:15:35, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile =

    09/23/09 10:15:35, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName =

    09/23/09 10:15:35, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName =

    09/23/09 10:15:35, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used

    09/23/09 10:15:35, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used

    09/23/09 10:15:37, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used

    09/23/09 10:15:37, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files\Microsoft SQL Server\90\Shared\ErrorDumps\SQLDmpr0031.mdmp

    09/23/09 10:15:37, ACTION, DTExec.exe, Watson Invoke: Yes

    09/23/09 10:15:38, ACTION, DTExec.exe, Watson Invoked: C:\PROGRA~1\COMMON~1\MICROS~1\DW\DW20.EXE dw20.exe -d "C:\Program Files\Microsoft SQL Server\90\Shared\ErrorDumps\SQLDmpr0002.mft"

    The SSIS package is exiting without outputting any messages, or any entries in the sysdtslog (I also have OnError events enabled and log everthing to sysdtslog). Only the SQLdumper cmd window flashes up for a split second as DTEXEC exits.

    It runs on the same server as the production warehouse (tis only small! 150k load a day).

    So I can't figure out whats going on. Only thing I can say is this problem has been occurring intermittently for last 4 months or so, but rerunning usually works. Since Monday (2009-09-21) its failing every time. But doesn't fail when i run the package from the dev server using production database. So is pointing me to corruption in SSIS runtimes or third party components that I'm using ??

    Only conclusion I can come to just now is that something has changed in the data sources to cause a problem in processing, the problem being so catastrophic (maybe a division by zero somewhere in the SSIS framework?) it causes the DTEXEC util to just completely bog out.

    So short of it, does anyone know how to troubleshoot these kind of problems?? without an actual error I've been totally stumped and for last three days I've just been trying random things to no avail. I know something must have changed, but system is taking data from 7 different sources and applying a host of different manipulations/dedupes/bucketing/cleaning etc to it so don't know where to start. And as its not giving actual errors i don't think the DDL of the sources is changing, just something about the data, but trying to get the business to tell you what there up to is impossible though!!!

    aaaaaaaarrrrrrrrrrrrrgg

  • dharmen.somagani

    SSC Enthusiast

    Points: 126

    Rajesh.kb (4/3/2009)


    Hi everybody, i'm getting one dump file when i run SSIS package. Any idea about how SQLDUMPER_ERRORLOG.log file is creating? Content in the file is given below

    04/02/09 06:04:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied

    04/02/09 06:04:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID = 3180

    04/02/09 06:04:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0

    04/02/09 06:04:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0

    04/02/09 06:04:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags = 0x0

    04/02/09 06:04:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr = 0x0100A530

    04/02/09 06:04:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir =

    04/02/09 06:04:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExceptionRecordPtr = 0x00000000

    04/02/09 06:04:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr = 0x00000000

    04/02/09 06:04:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile =

    04/02/09 06:04:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName =

    04/02/09 06:04:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName =

    04/02/09 06:04:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used

    04/02/09 06:04:01, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used

    04/02/09 06:04:02, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used

    04/02/09 06:04:02, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files (x86)\Microsoft SQL Server\90\Shared\ErrorDumps\SQLDmpr0002.mdmp

    04/02/09 06:04:02, ACTION, DTExec.exe, Watson Invoke: No

    Hey , did you get around this issue ? if so can you please share with us , I'm also getting same error now on Prod.

  • g tapia

    Valued Member

    Points: 71

    Hi,

    I have this problem but it is related to doing BackupExec. We used Brightstore before.

    Difference is that BackupExec makes volume copy and freeze the data but does not resume.

    It fails randomly.

  • winhtut.oo

    SSC Enthusiast

    Points: 185

    Hi

    Any update on this issue?

    Anyone knows how to read and understand these mdmp files?

    thanks

  • Markus Summer

    SSC Veteran

    Points: 200

    I'm also interested in this topic

  • sowmya.authappan

    SSC Enthusiast

    Points: 133

    Hi,

    I get the same problem when I try to execute SSIS which loads a simple excel data into OLE DB destination.

    Please help if anyone have found a solution for this problem.

    Thanks.

    Sowmya

  • sowmya.authappan

    SSC Enthusiast

    Points: 133

    Looks like mine was a 64-bit and excel connection manager is not supported on it. However, i just copied over the records from excel to SQL table directly (it was jus 28 records...).

    If there is any solution or wrk around to this problem, I would like to know.

    Thanks.

    Sowmya

  • gstockfisch

    SSC Enthusiast

    Points: 128

    I know this is an ancient thread, but I was just fighting this issue and finally figured out the cause, at least in my case.

    In my SSIS package, I only wanted to produce a flat file output if there was data to report.

    There was an IF EXISTS in the Stored Proc that someone else had written to grab the data, that would jump out of the Proc if no data was found in "yesterday's"  activity. If there was activity, the Proc would continue on doing the bulk query work getting my final output.

    I added a ROW COUNT task to see if I had zero rows or not,  and a FILE SYSTEM task to delete the garbage text file that was produced if variable RowCount equaled zero. That's when the trouble started with the odd SQLDUMPER_ERRORLOG.log.

    I realized that the ErrorLog would only appear in instances where no data was available to report on, so it seemed that the ROWCOUNT task had to have a table to work with whether it was populated or not. I threw in an ELSE alongside the IF EXISTS that was guaranteed to return an empty table (AND 1=2 in the WHERE clauses) and it ran perfectly.

Viewing 9 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic. Login to reply