Post reply

SSIS Debug Host has stopped working

  • September 13, 2010 at 10:59 am

    #223824

    I've created an SSIS package on a SQL 2008 server. The source connection is an ODBC connection (IBM UniVerse ODBC Driver) and the destination is an ADO.NET SQL connection to a SQL2008 server. Both connections test successfully.

    When I try to execute task on the 1 and only control flow task, everything appears business as usual, but after a minute or so, I get the following error with no rows actually loaded

    SSIS Debug Host has stopped working

    Problem signature:

    Problem Event Name:APPCRASH

    Application Name:DtsDebugHost.exe

    Application Version:2007.100.1600.22

    Application Timestamp:48753d31

    Fault Module Name:StackHash_9cb9

    Fault Module Version:6.0.6002.18005

    Fault Module Timestamp:49e03821

    Exception Code:c0000374

    Exception Offset:000afaf8

    OS Version:6.0.6002.2.2.0.272.36

    Locale ID:1033

    Additional Information 1:9cb9

    Additional Information 2:7d6ff1a72252a7c1c69569fdf100cb8a

    Additional Information 3:bc26

    Additional Information 4:6a1d6833ac97e5e6eee0b472af1c02f7

    Read our privacy statement:

    http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409

    Does anyone know what causes this and how to fix it?

  • September 13, 2010 at 12:07 pm

    #1220233

    Can you try modifying your package and testing it in these configurations, which will tell us which part, or combinations of parts, are causing the problem:

    1. Remove the ADO.Net Destination, and replace it with a Row Count

    2. Remove the ADO.Net Destination, replace it with a RAW File Destination

    3. Create a new data flow, using the RAW File generated in the last step as a RAW File Source, and send that to your ADO.Net Destination

    Todd McDermid - SQL Server MVP, MCTS (SQL 08 BI), MCSD.Net
    My Blog - Dimension Merge SCD Component for SSIS - SSIS Community Tasks and Components

  • September 16, 2010 at 10:07 am

    #1222320

    I'm not sure how, but this stopped being a problem. I do however have a new one, so I'll create a new thread.

  • March 22, 2012 at 6:40 am

    #1462658

    Hi

    I am as well facing the similar issue. While accessing data from UniData into a SSIS package am receiving same error.

    please advise.

    Thanks

Viewing 4 posts - 1 through 3 (of 3 total)

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