February 18, 2008 at 3:08 pm
Has anyone seen this error message?. I'm using .NET provider\odbc data provider as my connection manager.
[Read fom abc tablename [1]] Error: System.NullReferenceException: Object reference not set to an instance of an object. at Microsoft.SqlServer.Dts.Pipeline.DataReaderSourceAdapter.PrimeOutput(Int32 outputs, Int32[] outputIDs, PipelineBuffer[] buffers) at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostPrimeOutput(IDTSManagedComponentWrapper90 wrapper, Int32 outputs, Int32[] outputIDs, IDTSBuffer90[] buffers, IntPtr ppBufferWirePacket)
[DTS.Pipeline] Error: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on component "Read fom abc tablename" (1) returned error code 0x80004003. 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.
[DTS.Pipeline] Error: SSIS Error Code DTS_E_THREADFAILED. Thread "SourceThread0" has exited with error code 0xC0047038. There may be error messages posted before this with more information on why the thread has exited.
February 20, 2008 at 2:47 pm
Refreshing ADO.NET/ODBC connection manager solved my problem. For more
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1445044&SiteID=1
September 28, 2008 at 11:44 pm
Hi,
This is Kiran, i got same problem. please let me know if u got solution ASAP now.
April 2, 2009 at 10:02 am
Refreshing does not seem to fix my problem. Anymore suggestions?
May 12, 2009 at 1:44 pm
Hi, I have the same problem. Did you solve your problem?
June 4, 2009 at 1:00 am
Hi,
We had this same error in a SSIS package using a third-party ODBC driver - related to .Net Framework and variable length strings.
I had to setup redundant Error Redirections on every task to workaround it.
Useful post to help resolve: http://www.sqlmonster.com/Uwe/Forum.aspx/sql-server-dts/12464/DTS-E-INDUCEDTRANSFORMFAILUREONERROR
Cheers,
Matt
MattF
June 15, 2009 at 5:33 pm
Hi,
I have exactly the same problem. i.e.
[font="Courier New"]Error: 0xC0047062 at Data Flow Task (xxx), DataReader Source (xxx) [1]: System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.SqlServer.Dts.Pipeline.DataReaderSourceAdapter.PrimeOutput(Int32 outputs, Int32[] outputIDs, PipelineBuffer[] buffers)
at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostPrimeOutput(IDTSManagedComponentWrapper90 wrapper, etc, etc ... [/font]
Strangely, the data is successfully written to the destination table, however the task fails because the maximum error count is reached. i.e.
[font="Courier New"]Info: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (3) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.
SSIS package "Portfolio 1.dtsx" finished: Failure.[/font]
I tried the solution suggested by MattF, but it made no difference, as it seems to be a solution for a slightly different error, i.e. "inducedtransformfailureonerror".
Also, I tried refreshing the connection manager in the DataReader Source Editor, but it resulted in a slightly different error, i.e:
[font="Courier New"]Error at Data Flow Task (xxx) [DataReader Source (xxx) [1]]: System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.SqlServer.Dts.Pipeline.DataReaderSourceAdapter.ReinitializeMetaData()
at Micorosoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostReinitializeMetaData(IDTSManagedComponent[/font]
... and then the data flow task does not run at all.
Please help as this is driving me crazy!
March 17, 2011 at 2:39 pm
Hi,
I have a SSIS package which is running fine in BIDS
Source : oracle
Destination : SQL
While running the ssis package from SQL server agent i am getting following error :
Error: 2011-03-17 13:31:37.33 Code: 0xC0202009 SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. End Error Error: 2011-03-17 13:31:37.34 Code: 0xC0047038 Source: DFT - Get SAP Costing data from DW SSIS.Pipeline Description: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on component "OLE_SRC" (1) returned error code 0xC0202009. 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. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 1:29:34 PM Finished: 1:31:38 PM Elapsed: 123.163 seconds. The package execution failed. The step failed.
Any idea on this?
Thanks,
Ruby
June 6, 2011 at 12:32 pm
What fixed my error was I had to make the batch size smaller.
One case I had to go to 100 and another 300.
I'm going through a small VPN tunnel.
August 8, 2011 at 6:49 am
One of the possible reasons for this error is,
Your SSIS package may contain an dataflowtask trying to load data into a table having primary key without cleaningup the unwanted data which will lead to violation of primary key error issue if new data's PK column values matches with the existing data.
I experienced this in my package and cleaningup the unwanted data from the destination table has resolved the issue for me.
August 21, 2011 at 8:52 am
Hi,
I am having the same problem today in a job that has been running successfully for about two week now. I have no primary keys and my table is truncated first as it is a reference table refresh. Any thoughts?
Thanks
November 23, 2011 at 12:00 pm
I'm also having the same problem, but this error started without any changes. We've been running the same code for many months and then yesterday, this error happens. It's like Beej's problem in that the data is successfully written as reported in the following trace:
[font="Courier New"]Error: 0xC0047062 at Data Flow Task, Source - Query [1]: System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.SqlServer.Dts.Pipeline.DataReaderSourceAdapter.PrimeOutput(Int32 outputs, Int32[] outputIDs, PipelineBuffer[] buffers)
at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostPrimeOutput(IDTSManagedComponentWrapper90 wrapper, Int32 outputs, Int32[] outputIDs, IDTSBuffer90[] buffers, IntPtr ppBufferWirePacket)
Error: 0xC0047038 at Data Flow Task, DTS.Pipeline: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on component "Source - Query" (1) returned error code 0x80004003. 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.
Error: 0xC0047021 at Data Flow Task, DTS.Pipeline: SSIS Error Code DTS_E_THREADFAILED. Thread "SourceThread0" has exited with error code 0xC0047038. There may be error messages posted before this with more information on why the thread has exited.
Information: 0x402090DF at Data Flow Task, Destination - tmp_AR_OpenInvoice [121]: The final commit for the data insertion has started.
Information: 0x402090E0 at Data Flow Task, Destination - tmp_AR_OpenInvoice [121]: The final commit for the data insertion has ended.
Information: 0x40043008 at Data Flow Task, DTS.Pipeline: Post Execute phase is beginning.
Information: 0x40043009 at Data Flow Task, DTS.Pipeline: Cleanup phase is beginning.
Information: 0x4004300B at Data Flow Task, DTS.Pipeline: "component "Destination - tmp_AR_OpenInvoice" (121)" wrote 318463 rows.[/font]
It suggests to me that the problem is in the source data (" "Source - Query" (1) returned error code 0x80004003.") so I'm googling that now. The source in this case is a ProvideX ODBC getting data from Sage's MAS.
September 9, 2020 at 8:34 pm
I received this error because a flat file with no column names was received for an import job that expected the first row to have column names. Once the column names were added, the error was resolved.
Viewing 13 posts - 1 through 12 (of 12 total)
You must be logged in to reply to this topic. Login to reply