none
The PrimeOutput method on component "OLE DB Source 1" (1) returned error code 0xC0202009.

    Question

  • Basic Info: Same package on SQL Server 2005 - Was working fine

    Upgraded to 2008. In my Data Flow Task (DFT ), i have OLE DB Source and Desti . In connection manager, my connection is OLE DB too.
    Source is pulling 8000 records and loading in Desti. Simple package.

    My Package is breaking on OLE DB Source. That means there is something wrong with my source Query. Which is not possible as it was working fine in 2005.
    The point to note is : It loads 7814 records very fine. But at the end it breaks on OLE DB Source.

    ERROR:
    Error: 0xC0047038 at Data Flow Task, SSIS.Pipeline: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED.  The PrimeOutput method on component "OLE DB Source 1" (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.

    WORK AROUND I FOUND:
    What i did was, i ran my package with different combinations of source query in OLE DB source . Like out of 20 fields, i first pou 10 only in sourec query and commented out other 10 and package ran fine. That means problem in other 10 fields. THen down to 5 and then came to know that one field is braking the package. BUTTTTTT work around was: Breaking field was nvarchar(MAX) field and i had to trim it down to LEFT (field, 1000)  which is not solution excatly. The reason i am saying it is: i am getting same problem in my another package which used to work fine in 2005. In my Driver package i have this kind of 38 packages. All those worked fine in 2005 but suddenly i am having this problem in 2008 where some of my OLE DB source are breaking with error above .

    Can anybody please help me with this issue?

    Thanks in advance.
    Thursday, April 16, 2009 9:03 PM

Answers

  • Hi jd-fdu,
    could you please file a bug via "Connect" ? It would be great if you attach a small repro (package, database).
    -Alex
    Tuesday, June 02, 2009 9:44 PM

All replies

  • What was the data type of the column in SSIS? DT_NTEXT?
    John Welch | www.mariner-usa.com | www.agilebi.com | ssisUnit.codeplex.com
    Sunday, April 19, 2009 11:37 PM
    Moderator
  • Yes it is DT_NTEXT
    Wednesday, April 22, 2009 5:38 PM
  • do u know the solution to this?
    Tuesday, June 02, 2009 8:40 PM
  • No, unfortunately, I haven't seen this behavior. A NTEXT column should hold a NVARCHAR(MAX) without issue, so I'm not sure where the issue is coming from.
    John Welch | www.mariner-usa.com | www.agilebi.com | ssisUnit.codeplex.com
    Tuesday, June 02, 2009 8:50 PM
    Moderator
  • Hi jd-fdu,
    could you please file a bug via "Connect" ? It would be great if you attach a small repro (package, database).
    -Alex
    Tuesday, June 02, 2009 9:44 PM
  • Hello,

    Which OLEDB provider are you using (what type of database are you connecting to)?

    ~Matt


    This posting is provided "AS IS" with no warranties, and confers no rights
    Tuesday, June 02, 2009 10:39 PM
  • After the package breaks it gives this error: " Warning: Null value is eliminated by an aggregate or other SET operation. "
    Which doesn't make any. BECAUSE it is warning, right? Then why is it failing the package?

    Example:
    In my source query (in OLEDB Source) my query is

    "SELECT MIN(SubmittedDate) from **"

    Now if SubmittedDate is NULL then that warning makes sense. But it should not break the package ( even My Dest column is NULLABLE )..
    Monday, August 17, 2009 9:24 PM
  • Solution to that.

    http://social.msdn.microsoft.com/Forums/en-US/sqlintegrationservices/thread/c5cea9c7-91a3-4754-8acf-6e4dc50029bf

    Thanks all for replying though..
    Wednesday, September 16, 2009 9:55 PM