Comments on: SSIS 2012 Script Component Streaming Error (0xC0047020)

By: Michael

Michael — Sun, 02 Apr 2017 06:12:09 +0000

Holy cow, yes, this could’ve been hours. As if SSIS doesn’t give me enough problems, at least this one was resolved without chasing my tail (or a wild goose, for that matter) for hours.

In my case, I was moving 500 columns from the source to the destination. The destination is 2 SQL Server tables. As we all know, a single row in a SQL Server table *cannot* be more than 8060 bytes, so if 250 columns per table has greater than 32 characters per column on average, then the destination blows up. And as a result, it was pointing the finger at my script, just like you said. What a relief.

By: Links Naji

Links Naji — Mon, 11 Nov 2013 09:38:44 +0000

No worries Tom, glad this helped you identify your problem!

By: Tom

Tom — Sun, 10 Nov 2013 22:35:26 +0000

Thankyou! I got the same error in SSIS 2008, and sure enough, truncation was occuring on a downstream derived column task. Once that was resolved, the issue disappeared.

The error I had was System.Runtime.InteropServices.COMException (0xC0047020)

By: Esey

Esey — Tue, 30 Oct 2012 21:05:11 +0000

Thanks for posting – this was helpful. It is really a strange error. A Primary Key Violation error on the destination pops up the exception window.

By: Graham

Graham — Mon, 28 May 2012 16:11:49 +0000

Crazy to think that SSIS is throwing an error downstream without even identifying the component correctly. Even for SSIS, that’s a bad one! Hopefully there’s an issue already open for this on MS Connect.