Lineage ID Errors


  • I am running an SSIS package and I keep getting this error when it gets to a the dataflow task.  I have a bit of an idea of what it means, but I can't figure out how to fix it.  IF anybody could explain this error and fixes for it that would be of immense help.  Thank you.

    0xC004701C at Load Server Security, DTS.Pipeline: input column "Server" (1434) has lineage ID 1421 that was not previously used in the Data Flow task.
    Error: 0xC004706B at Load Server Security, DTS.Pipeline: "component "OLE DB Destination 1" (1420)" failed validation and returned validation status "VS_NEEDSNEWMETADATA".
    Error: 0xC004700C at Load Server Security, DTS.Pipeline: One or more component failed validation.
    Error: 0xC0024107 at Load Server Security: There were errors during task validation.
    Wednesday, August 15, 2007 3:22 PM


All replies

  • The first error simply says that you have a column in the data flow, Server, that isn't used.

    The second error looks to me like there were database changes to that table and now the OLE DB destination needs to be updated.  Double click on the OLE DB destination and select the mappings tab.  If no changes need to be made, simply click OK.
    Wednesday, August 15, 2007 3:32 PM
  • Possible reason could be if your destination table structure or the column data type changed.


    Wednesday, August 15, 2007 3:37 PM
  • You should have a triangle with an exclaimation mark on it.  Double click on that component and then mappings, if applicable, to fix it.
    Wednesday, August 15, 2007 3:48 PM
  • I have the same issue and I know proposed solution. Nevertheless if I want to change source xml file I have to use the  "Restore Invalid Column References Editor" for all related OLE DB dastinations for tables extracted from xml source. Do somebody know about more flexibile solution?


    Friday, October 26, 2007 4:21 PM
  • I have not seen a good solution for this problem. Changing the metadata of the source system after the data flow is built requires a manual review of the data flow, and simply removing invalid references in that editor can often lead to changed data being omitted.


    I realize that this is not particularly helpful since you are in this situation already, but "Get your metadata right first, not later" is one of the SSIS best practices that I've come up with over the years and finally got around to blogging on:

    Friday, November 02, 2007 2:50 AM