Lee posted on May 19, 2009 13:12
I had this, and figured it out! Have no idea how I found solution


I mentioned to a work colleague that I got a Pervasive data import to run in SSIS, using an ADO.Net task, only if I had an error rows transformation. Very strange! He looked at me like I was half-crazy.  Turns out today that I find the same fix on the product support blog…cool.  The only thing different than my discovery is that I did not need step c, and I didn’t connect to a text file.  Rather, I just output it to a SQL Server table.

What’s happening here is that the .Net 3.5 Framework sp1 doesn’t like SSIS using 3rd party drivers.  As it goes, I’m currently on a project……………………developing in SSIS using 3rd party drivers.  Such a beautiful thing!

Some of the error messages you might see (in bold the one that I experienced):

[DataReader Source [<number>]] Error: SSIS Error Code
DTS_E_INDUCEDTRANSFORMFAILUREONERROR. The "component "DataReader Source" (<number>)" failed because error code 0x80131937 occurred, and the error row disposition on
"output column "ColumnName" (<number)" specifies failure on error. An error occurred on the
specified object of the specified component. There may be error messages posted
before this with more information about the failure.

The error messages may vary depending on if you are using DataReader Source in Visual Studio 2005 or ADO .Net Source in Visual Studio 2008 –

[ADO NET Source [<number>]] Error: SSIS Error Code DTS_E_INDUCEDTRANSFORMFAILUREONERROR. The "component "ADO NET Source" (<number>)" failed because error code 0x80131937 occurred, and the error row disposition on "output column "ColumnName" (<number>)" specifies failure on error. An error occurred on the specified object of the specified component. There may be error messages posted before this with more information about the failure.

Error 0xc0209029: Data Flow Task: The "component "<ComponentName>" (<number>)" failed because error code 0x80131937 occurred...

[ADO NET Source [<number>] Error: The component "ADO NET Source" (<number>) was unable to process the data. Pipeline component has returned HRESULT error code 0xC0209029 from a method call.

[SSIS.Pipeline] Error: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on component "ADO NET Source" (<number>) returned error code 0xC02090F5. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure.


Check out their fix at the link below.


http://blogs.msdn.com/sqlblog/archive/2009/04/09/after-installation-of-net-framework-3-5-sp1-or-net-framework-2-0-sp2-ssis-packages-using-odbc-3rd-party-drivers-may-fail.aspx


Lee

----------------------------


Rule #1: When using Microsoft SQL Server, expect the unexpected when going to and from a third-party database

 

 


Posted in:   Tags:

Comments

Comments are closed

by Lee Everest, M.S.

Search


Ads

Calendar

«  March 2010  »
MoTuWeThFrSaSu
22232425262728
1234567
891011121314
15161718192021
22232425262728
2930311234
View posts in large calendar

Tags

Disclaimer
The opinions, code, examples, et.al. expressed herein are my own personal opinions and do not represent my employer's view in any way, shape form, or fashion.  All code for demonstration purposes - no guarantees, either written or implied, are made.

© Copyright 2010 Lee Everest's SQL Server, etc. weblog