The buffer type is not valid. Make sure the Pipeline layout and all components

  • Hi guys,

    I am having a really weird issue with sqlserver job. So here is the scenario:

    I have a SSIS package which is using a C# component and inserts in a sql server database. When I run package from SSIS, it runs fine, does the insert and life is good. Now, I deployed this SSIS package to a sql server and then try to run the SSIS from sql server and I get this error:

    OLE DB Destination Input has lineage ID 2000 that was not previously used in the Data Flow task.

    OLE DB Command Input has lineage ID 3281 that was not previously used in the Data Flow task.

    The buffer type is not valid. Make sure the Pipeline layout and all components pass validation.

    INSERT INTO <tablename> failed the pre-execute phase and returned error code 0xC0202020.

    Have been scratching all my hairs out but stillcan't figure out. Package runs completely fine when I run this in visual studio. also, that sql server is ona  different machine.

    I also copied the C# dlls used by SSIS to the sql machine:

    C:\Program Files (x86)\Microsoft SQL Server\110\DTS\PipelineComponents

    C:\Program Files\Microsoft SQL Server\110\DTS\PipelineComponents

    is this a deployment issue? Because Package runs completely fine from visual studio. I seriously need some quick help.

    I really appreciate it guys.

  • Because of my "love" for SSIS and curly-braced languages, I was going to suggest the ever obnoxious "clear the cache" suggestion that so many Windows folks make but, doing just a little bit of research, that obnoxious suggestion might not be that far off.  Here's the shortest post I could find on the subject and, with the understand that I don't use either SSIS or C#, it seems to have strong merit to it especially since I've seen such issues before.  Here's the link.

    https://social.technet.microsoft.com/Forums/sqlserver/en-US/6c74a6c6-2eee-42ac-ac2a-16ca32ac2d55/has-lineage-id-8828-that-was-not-previously-used-in-the-data-flow-task?forum=sqlintegrationservices

     

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • Hi Jeff,

    thanks for your post. I have done this already. code is running fine on visual studio but it is having issue running from sql server.

    has anyone else faced this issue before?

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply