SSIS conditional dividing line error
I am trying to run an Excel spreadsheet through SSIS package and 3 nodes, it has conditional split. I am using a previously known worksheet with some data added to it.
The error I am getting is:
Conditional Split.Inputs [Split Input] .Columns [ColumnName] has line ID 147, which was not previously used.
I've tried a couple of spreadsheets to no avail. First I got ID 105.
My specific questions are: what do the IDs match? Where am I trying to fix them?
Some additional magazines.
Output:
Data flow error Task 1 [SSIS.Pipeline]: Conditional split. Inputs [conditional split input]. Column [ColumnName] has line ID 147, which was not previously used in a data flow task.
Dataflow error Task 1 [SSIS.Pipeline]: "Conditional split" failed to validate and returned validation status "VS_NEEDSNEWMETADATA".
Data Flow Error Task 1 [SSIS.Pipeline]: One or more failed component attempts.
Data flow error Task 1: Errors occurred while validating the task.
source to share
"The line identifier is a property of a component or transform used in a data flow task. It contains an integer value that will act as a buffer pointer. Each column of the data flow task will be assigned a line ID." Read about Line ID in this Microsoft TechNet article
LINEAGE ID The error implies that the original metadata has been changed, just re-check the source (connection and component) by double-clicking the Conditional Split section and close it, then check the column metadata (using the advanced editor). (Note that when you double click on the component containing errors, it will ask you to fix it)
Or you can try removing the conditional separator and add it again (if the previous solution doesn't work)
source to share
I believe SSIS assigns unique IDs (line IDs) to every column in every pipe connecting your components. SSIS gets confused when a component expects line id x but cannot find it in the input pipe.
Typically you are trying to find the faulty channel (in BIDS / SSDT using @Wendy method). Double clicking on a channel or connected components sometimes creates a dialog box offering an opportunity to correct the problem. If not, then removing and re-creating the pipe is your best chance.
Changing things upstream can damage the components of the downstream component. Often the only remedy when doing intermediate modifications is to rebuild the entire downstream. SSIS is a little fragile in this area.
source to share