none
SSIS package SQL Server 2012 Error 0xC02020C4 RRS feed

  • Question

  • Hi,

    I'm in the middle of upgrading from SQL Server 2005 to SQL Server 2012.  I've migrated all the SSIS packages in BIDS to 2010.  I'm having a problem with one package.

    I receive the following error message:

    SSIS Error Code DTS_E_PRIMEOUTPUTFAILED.  The PrimeOutput method on XXXXXX returned error code 0xC02020C4.  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.

    The attempt to add a row to the Data Flow task buffer failed with error code 0xC0047020.

    The source destination is a SQL Server 2000 database and is loading the data into SQL Server 2012.  There is only 140,000 rows being extracted from source, the package has about 18 lookup's for the different keys on the destination table.   Previously the package would redirect rows on error to a derived column to add default (I've re-written this and it made no difference by using an ISNULL within a derived column).

    If I change the source destination stored procedure to only return the first 5000 rows i.e. TOP 5000 the package is OK, if I run the package within BIDS it is OK.  It will only fail when it is a schedule job.

    • I've tried adjusting the BufferMaxRows and the BufferSize (both up and down) and it makes no difference.
    • I've checked that the server has enough resources available (over 1.0 GB memory, CPU is hardly moving)
    • I've tried changing the provider on the connection to Native Client 10.0

    The annoying thing is that the package works OK on the old version, the only difference is the O/S and it is 64 bit.

    Please help, it is driving me mad!!!

    Jason

    Friday, July 27, 2012 10:29 AM

Answers

  • I've resolved the issue...

    I had a lookup that redirected rows into a multicast i.e. to throw away the rows.  I change the lookup so that it "Redirect rows to no match output" rather than "Redirect rows to error output" which is how it was handled in 2005.

    Jason

    Friday, July 27, 2012 12:19 PM

All replies

  • I've resolved the issue...

    I had a lookup that redirected rows into a multicast i.e. to throw away the rows.  I change the lookup so that it "Redirect rows to no match output" rather than "Redirect rows to error output" which is how it was handled in 2005.

    Jason

    Friday, July 27, 2012 12:19 PM
  • Hi jase74,

    Thank you for sharing your solutions and experience here. It will be very beneficial for other community members who have similar questions.

    Thanks,
    Eileen

    TechNet Subscriber Support

    If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.

    • Proposed as answer by jrimada Friday, February 6, 2015 8:37 AM
    • Unproposed as answer by jrimada Friday, February 6, 2015 8:37 AM
    Tuesday, July 31, 2012 1:41 AM
  • I have the same error on SQL Server 2012 Standard!
    Tuesday, January 23, 2018 12:44 PM