20 thoughts on “SSIS: How to get name of ErrorColumn from Error Output?

    1. Using the new approach, the SQL destination component returns me ErrorColumn as 0. Does someone has any idea why is this so and what is the solution for this. I really need to know which column is causing the issue. Thanks@

  1. Hi Benny,

    I am using VS and SQL Server 2012 and have been able to get the DFLD executable working on my SSIS Development environment. I am deploying my SSIS project to the Integration Services Catalog for execution on my Production environment. Seeing as how the DFLD executable requires the package file path as an input, how would I go about running the executable on my Production environment when the packages are stored in the Integration Services Catalog?


    1. Mark, at the moment DFLD can extract SSIS metadata only from file path. Future releases might include this option to extract from SSIS catalog. For now, you might have to point the metadata database to production or export the metadata from an existing environment.

      1. I used the below bcp command to generate the .dtsx files from msdb, then loop thorugh all of them on a daily basis to refresh the meta data and use DFLD to push package information

        bcp “select cast(cast(packagedata as varbinary(max)) as varchar(max)) from MSDBrestore.dbo.sysssispackages where name = ‘MIPODS'” queryout c:\temp\PackageNameMIPODS.dtsx -Slocalhost -T -c

  2. Hi Benny,

    Using SSIS 2012. I removed all references > readded them again. Built the sln with no issue. As soon as I debug it in VS 2012, console window opens and closes immediately…nothing else happens. What might be the issue?

    1. Jason, DFLD does work for SSIS 2012 packages as it is. One thing I did notice was that if there are multiple versions of SQL Server on the same server, then you have to edit the path environment variable and re-arrange SQL Server 2012 paths (\Microsoft SQL Server\110) to be ahead of earlier versions like SQL 2008 (\Microsoft SQL Server\100). And also the 64-bit path must be ahead of the x86 path, if you are using a 64 bit version. In this way the correct version of SSIS Application will be executed by DFLD. Otherwise you might get the following exception

      “The package failed to load due to error 0xC0011008 “Error loading from XML. No further detailed error information can be specified for this problem because no Events object was passed where detailed error information can be stored.”. This occurs when CPackage::LoadFromXML fails.”

      1. We have a fresh install of sqlserver 2012 and ssis 2012(no prior versions). I was getting errors trying to run the dfld executable. I did get it to work today though. I downloaded the source. Then I had to remove the references in visual studio and reattach them. It seems it was looking for an old version somewhere. But it works now. Thanks you.

  3. Thanks Benny, this worked for me! FYI, when I configured my Derived Columns, for PackageID and DataflowID, and added the corresponding System variables, the Data Type for each automatically was defined as “Unicode string [DT_WSTR]” which later caused a ‘Type Mismatch” error when matching up the PackageID and DataflowID columns in my Lookup. As you might guess, this was because the data types in the database for these fields were varchar, not nvarchar. Switching these columns to nvarchar(38) fixed the problem. Hope this helps someone and thanks again.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s