Comments posted to this topic are about the item SSIS Custom Error Handling

Cheers
http://twitter.com/widba
http://widba.blogspot.com/

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!

The article references using 2008 - follow the link to Jack's original article, he has the components setup for 2005.

Cheers
http://twitter.com/widba
http://widba.blogspot.com/

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.

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 '<fields />' with a hyperlink to an xml file. The only thing in this file is the same <fields /> text. Any ideas why I wouldn't be getting the field name or is there a trick to getting it?

Thanks in advance.

I figured it out. I forgot to check the individual columns that I wanted to see in the buffer.

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 said

I 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.

Cheers
http://twitter.com/widba
http://widba.blogspot.com/

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>reg.cmd

C:\Documents and Settings\1\My Documents\SSISLogging\bin>copy "C:\Documents and
Settings\1\My Documents\SSISLogging\bin\SSIS.Logging.dll" "C:\Program Files\Micr
osoft SQL Server\90\DTS\PipelineComponents\"
1 file(s) copied.

C:\Documents and Settings\1\My Documents\SSISLogging\bin>"C:\Program Files\Micro
soft Visual Studio 8\SDK\v2.0\Bin\sn.exe" -Vr "C:\Program Files\Microsoft SQL Se
rver\90\DTS\PipelineComponents\SSIS.Logging.dll"

Microsoft (R) .NET Framework Strong Name Utility Version 2.0.50727.42
Copyright (c) Microsoft Corporation. All rights reserved.

Verification entry added for assembly 'SSIS.Logging,55BF2292469930A5'

C:\Documents and Settings\1\My Documents\SSISLogging\bin>"C:\Program Files\Micro
soft Visual Studio 8\SDK\v2.0\Bin\gacutil.exe" /if "C:\Program Files\Microsoft S
QL Server\90\DTS\PipelineComponents\SSIS.Logging.dll"
Microsoft (R) .NET Global Assembly Cache Utility. Version 2.0.50727.42
Copyright (c) Microsoft Corporation. All rights reserved.

Assembly successfully added to the cache

Jack Corbett's article (mine is a derivative of his) talks about SQL/VS 2005 implementation. This article refers to a 2008 version - sorry.

Cheers
http://twitter.com/widba
http://widba.blogspot.com/

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?