﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / Discuss Content Posted by Zach Mattson / Article Discussions / Article Discussions by Author  / SSIS Custom Error Handling / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Sat, 25 May 2013 01:09:39 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: SSIS Custom Error Handling</title><link>http://www.sqlservercentral.com/Forums/Topic677208-297-1.aspx</link><description>I have done Error Handling by getting the Error Column name from the lineageId and forming custom error message.http://www.nkannan.com/2012/02/error-handling-in-ssis-dft.html Thanks,Nk</description><pubDate>Tue, 07 Feb 2012 10:56:00 GMT</pubDate><dc:creator>nakkeeran.kannan</dc:creator></item><item><title>RE: SSIS Custom Error Handling</title><link>http://www.sqlservercentral.com/Forums/Topic677208-297-1.aspx</link><description>This is good stuff. Thanks a ton for sharing this.</description><pubDate>Wed, 14 Jul 2010 07:20:35 GMT</pubDate><dc:creator>haridasabhavana</dc:creator></item><item><title>RE: SSIS Custom Error Handling</title><link>http://www.sqlservercentral.com/Forums/Topic677208-297-1.aspx</link><description>I have come up with a query to dynamically crosstab your xml fields, I posted it on Jack's discussion, the link is below. Thanks[url=http://www.sqlservercentral.com/Forums/Topic487637-1254-11.aspx]http://www.sqlservercentral.com/Forums/Topic487637-1254-11.aspx[/url]</description><pubDate>Tue, 04 May 2010 11:55:37 GMT</pubDate><dc:creator>Stringzz</dc:creator></item><item><title>RE: SSIS Custom Error Handling</title><link>http://www.sqlservercentral.com/Forums/Topic677208-297-1.aspx</link><description>I only tested it in 2008 -&amp;gt; I can't say that it doesn't work since I jumped over the 2005 versions.</description><pubDate>Thu, 22 Apr 2010 13:28:48 GMT</pubDate><dc:creator>WI-DBA</dc:creator></item><item><title>RE: SSIS Custom Error Handling</title><link>http://www.sqlservercentral.com/Forums/Topic677208-297-1.aspx</link><description>Yes, I was able to successfuly implement Jack's version, however, I really wanted to add the script to the toolbox, for ease of developement. So, this version will only work in 2008?</description><pubDate>Thu, 22 Apr 2010 13:01:04 GMT</pubDate><dc:creator>Stringzz</dc:creator></item><item><title>RE: SSIS Custom Error Handling</title><link>http://www.sqlservercentral.com/Forums/Topic677208-297-1.aspx</link><description>Jack Corbett's article (mine is a derivative of his) talks about SQL/VS 2005 implementation.  This article refers to a 2008 version - sorry.</description><pubDate>Thu, 22 Apr 2010 12:57:25 GMT</pubDate><dc:creator>WI-DBA</dc:creator></item><item><title>RE: SSIS Custom Error Handling</title><link>http://www.sqlservercentral.com/Forums/Topic677208-297-1.aspx</link><description>I have registered the component successfully to add to the BIDS Toolbox, however, I do not see the custom component listed. I am using Visual Studio 2005 with SQL Server 2005.C:\Documents and Settings\1\My Documents\SSISLogging\bin&amp;gt;reg.cmdC:\Documents and Settings\1\My Documents\SSISLogging\bin&amp;gt;copy "C:\Documents andSettings\1\My Documents\SSISLogging\bin\SSIS.Logging.dll" "C:\Program Files\Microsoft SQL Server\90\DTS\PipelineComponents\"        1 file(s) copied.C:\Documents and Settings\1\My Documents\SSISLogging\bin&amp;gt;"C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\Bin\sn.exe" -Vr "C:\Program Files\Microsoft SQL Server\90\DTS\PipelineComponents\SSIS.Logging.dll"Microsoft (R) .NET Framework Strong Name Utility  Version 2.0.50727.42Copyright (c) Microsoft Corporation.  All rights reserved.Verification entry added for assembly 'SSIS.Logging,55BF2292469930A5'C:\Documents and Settings\1\My Documents\SSISLogging\bin&amp;gt;"C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\Bin\gacutil.exe" /if "C:\Program Files\Microsoft SQL Server\90\DTS\PipelineComponents\SSIS.Logging.dll"Microsoft (R) .NET Global Assembly Cache Utility.  Version 2.0.50727.42Copyright (c) Microsoft Corporation.  All rights reserved.Assembly successfully added to the cache</description><pubDate>Thu, 22 Apr 2010 12:51:52 GMT</pubDate><dc:creator>Stringzz</dc:creator></item><item><title>RE: SSIS Custom Error Handling</title><link>http://www.sqlservercentral.com/Forums/Topic677208-297-1.aspx</link><description>sorry - had the message 1/2 typed out and got pulled away.  you need to select the columns you want persisted into the XML- as you saidI need to open the code up and see why the error messages are generic.  I focused more on the data gathering than the actual error, but that was the narrow focus that I was going after.</description><pubDate>Wed, 24 Feb 2010 10:09:22 GMT</pubDate><dc:creator>WI-DBA</dc:creator></item><item><title>RE: SSIS Custom Error Handling</title><link>http://www.sqlservercentral.com/Forums/Topic677208-297-1.aspx</link><description>I figured it out.  I forgot to check the individual columns that I wanted to see in the buffer.</description><pubDate>Wed, 24 Feb 2010 09:36:09 GMT</pubDate><dc:creator>Jeremy Rooks</dc:creator></item><item><title>RE: SSIS Custom Error Handling</title><link>http://www.sqlservercentral.com/Forums/Topic677208-297-1.aspx</link><description>It seems like anytime there is an error with the entire row, such as a PK constraint, you get that same message.  I have tried a couple of other scripts and they return the same information.I have a question about the field name column.  Within my table I get '&amp;lt;fields /&amp;gt;' with a hyperlink to an xml file.  The only thing in this file is the same &amp;lt;fields /&amp;gt; text.  Any ideas why I wouldn't be getting the field name or is there a trick to getting it?Thanks in advance.</description><pubDate>Wed, 24 Feb 2010 08:44:44 GMT</pubDate><dc:creator>Jeremy Rooks</dc:creator></item><item><title>RE: SSIS Custom Error Handling</title><link>http://www.sqlservercentral.com/Forums/Topic677208-297-1.aspx</link><description>First, I really want to thank you for this component. It really made my life lots of easier. But somehow, I SSIS_LOG_ERROR table, all the ErrorDesc contains "No status is available.  ". When I know the error id caused by FK constrain. Do I miss anything? Any help is greatly appreciated.</description><pubDate>Sun, 03 May 2009 11:59:50 GMT</pubDate><dc:creator>chunshahab</dc:creator></item><item><title>RE: SSIS Custom Error Handling</title><link>http://www.sqlservercentral.com/Forums/Topic677208-297-1.aspx</link><description>The article references using 2008 - follow the link to Jack's original article, he has the components setup for 2005. </description><pubDate>Wed, 18 Mar 2009 07:48:12 GMT</pubDate><dc:creator>WI-DBA</dc:creator></item><item><title>RE: SSIS Custom Error Handling</title><link>http://www.sqlservercentral.com/Forums/Topic677208-297-1.aspx</link><description>I would like to give this a try.  However, I've never added a custom component and I'm struggling with registering it.   I'm using Visual Studio 2005.  I'm not finding a gacutil.exe that I obviously need so I can register it.    Any help is appreciated.   Thanks!</description><pubDate>Wed, 18 Mar 2009 07:41:10 GMT</pubDate><dc:creator>sford-721104</dc:creator></item><item><title>SSIS Custom Error Handling</title><link>http://www.sqlservercentral.com/Forums/Topic677208-297-1.aspx</link><description>Comments posted to this topic are about the item [B]&lt;A HREF="/articles/SSIS/65758/"&gt;SSIS Custom Error Handling&lt;/A&gt;[/B]</description><pubDate>Tue, 17 Mar 2009 00:23:57 GMT</pubDate><dc:creator>WI-DBA</dc:creator></item></channel></rss>