Sign in
 
Home20122008 R2200820052000LibraryForums
SQL Server >
> 
> 
SQLDUMPER ERROR while running SSIS package through DTEXEC

Answered SQLDUMPER ERROR while running SSIS package through DTEXEC

  • Wednesday, January 23, 2013 9:55 PM
     
     
    Sign In to Vote
    0


    I am running an SSIS package through DTEXEC command in a bat file. The SQLDUMPER popup kicks in randomly during the package execution and the package execution fails abruptly. I have no clue how to resolve the error.

    I get the following error in SQLDUMPER_ERRORLOG file;

    (B60:27DC) 01/23/13 12:19:52, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
    (B60:27DC) 01/23/13 12:19:52, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 1: 3604
    (B60:27DC) 01/23/13 12:19:52, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 2: 0
    (B60:27DC) 01/23/13 12:19:52, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 3: 0:0
    (B60:27DC) 01/23/13 12:19:52, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parameter 4: 00B3B568
    (B60:27DC) 01/23/13 12:19:52, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
    (B60:27DC) 01/23/13 12:19:52, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ProcessID = 3604
    (B60:27DC) 01/23/13 12:19:52, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ThreadId = 0
    (B60:27DC) 01/23/13 12:19:52, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Flags = 0x0
    (B60:27DC) 01/23/13 12:19:52, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     MiniDumpFlags = 0x0
    (B60:27DC) 01/23/13 12:19:52, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     SqlInfoPtr = 0x00B3B568
    (B60:27DC) 01/23/13 12:19:52, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     DumpDir = <NULL>
    (B60:27DC) 01/23/13 12:19:52, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExceptionRecordPtr = 0x00000000
    (B60:27DC) 01/23/13 12:19:52, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ContextPtr = 0x00000000
    (B60:27DC) 01/23/13 12:19:52, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExtraFile = <NULL>
    (B60:27DC) 01/23/13 12:19:52, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     InstanceName = <NULL>
    (B60:27DC) 01/23/13 12:19:52, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ServiceName = <NULL>
    (B60:27DC) 01/23/13 12:19:52, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
    (B60:27DC) 01/23/13 12:19:52, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
    (B60:27DC) 01/23/13 12:19:53, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
    (B60:27DC) 01/23/13 12:19:53, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files (x86)\Microsoft SQL Server\100\Shared\ErrorDumps\SQLDmpr0171.mdmp
    (B60:27DC) 01/23/13 12:19:53, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files (x86)\Microsoft SQL Server\100\Shared\dbghelp.dll'
    (B60:27DC) 01/23/13 12:19:53, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\100\Shared\dbghelp.dll' : '6.8:4.0'
    (B60:27DC) 01/23/13 12:19:53, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\100\Shared\dbghelp.dll' : '6.8:4.0'
    (B60:27DC) 01/23/13 12:19:53, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files (x86)\Microsoft SQL Server\100\Shared\SQLDUMPER.EXE'
    (B60:27DC) 01/23/13 12:19:53, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\100\Shared\SQLDUMPER.EXE' : '2009.100:1600.1'
    (B60:27DC) 01/23/13 12:19:53, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\100\Shared\SQLDUMPER.EXE' : '10.50:1600.1'
    (B60:27DC) 01/23/13 12:19:53, ACTION,                DTExec.exe, Watson Invoke: Yes
    (B60:27DC) 01/23/13 12:19:53, ERROR ,                DTExec.exe, Registry read /DW0200/ failed 0x80070002 - The system cannot find the file specified.

     

All Replies

  • Wednesday, January 23, 2013 10:02 PM
    Moderator
     
     
    Sign In to Vote
    0
    It is typically due to bitness e.g. you have a Fuzzy Lookup component and it cannot run under 64 bit or vise versa, then you need to run the package in the non-default bit space with the /X86 flag that causes the package to run in 32-bit mode on a 64-bit computer.

    Arthur My Blog

     
  • Wednesday, January 23, 2013 10:13 PM
     
     
    Sign In to Vote
    0

    I am running the package from batch file with the following code but the error persists. 

    "D:\Program Files (x86)\Microsoft SQL Server\100\DTS\binn\dtexec.exe" /f "D:\Visual Studio\Projects\SSIS Projects\Package.dtsx" /X86

    Also, I don't understand why this error is random.

     
  • Wednesday, January 23, 2013 10:17 PM
     
     
    Sign In to Vote
    0
    Also I set the Run64BitRuntime property for the project to FALSE. Still, I get the SQL Dumper ERROR pasted above
     
  • Wednesday, January 23, 2013 10:21 PM
    Moderator
     
     
    Sign In to Vote
    0

    What is in the package is the question? What task fails?

    Sometimes the "dumper" comes only once at all and any subsequent executions just end with an error.

    It is a low level crash inside some of the non-managed components of SQL Server [engine].

    Arthur My Blog

     
  • Wednesday, January 23, 2013 10:26 PM
     
     
    Sign In to Vote
    0
    In the package,  I have 23 data flow tasks which are running in parallel. Each data flow task loads data from an EXCEL File(.xlsx), does some data conversions and loads into SQL Server table. I do not have any fuzzy lookups at all in the package. 
    • Edited by Karteek Peri Wednesday, January 23, 2013 10:28 PM
    •  
     
  • Thursday, January 24, 2013 3:42 PM
    Moderator
     
     
    Sign In to Vote
    1
    Make it a sequential run, this must help fix this issue.

    Arthur My Blog

     
  • Thursday, January 24, 2013 4:30 PM
     
     
    Sign In to Vote
    0
    You are right. It works when I make it sequential. I tried this a few days back and it sure worked. But I want it to run in parallel cos I'm dealing with 450 million records and running in parallel would speed up the execution process. I do not understand why it fails when I do it in parallel. Any thoughts on this? Is this a bug in SSIS? Would installing SP2 make a difference?
     
  • Thursday, January 24, 2013 4:51 PM
    Moderator
     
     Answered
    Sign In to Vote
    1

    It is not a bug IMO, you simply cause deadlocking or prolonged locking that times the connection out.

    You need a re-design I think, e.g. look into using cache or staging/temp tables also make sure you implement good design;

    Matt Masson has good postings in his blog or even consider a book

    Re what can go wrong with parallel execution, what is happening with you is probably http://www.mattmasson.com/index.php/2012/01/too-many-sources-in-a-data-flow/

    Arthur My Blog