Home/ Questions/Q 8864943
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-14T16:22:49+00:00

I have seen this error before but got around it by entering values manually,

  • 0

I have seen this error before but got around it by entering values manually, but that was for 4 rows, this error occurs for over 100 rows this time.

The problem is, this column called Shipto it will have one of three things in it, a 1 digit number, a 2 digit number, or the word All. The import works perfectly fine for 1 and 2 digit numbers but when it has All it causes this error :

[SSIS.Pipeline] Error: SSIS Error Code DTS_E_PROCESSINPUTFAILED. The
ProcessInput method on component “OLE DB Destination” (162) failed
with error code 0xC0202009 while processing input “OLE DB Destination
Input” (175). The identified component returned an error from the
ProcessInput method. The error is specific to the component, but the
error is fatal and will cause the Data Flow task to stop running.
There may be error messages posted before this with more information
about the failure.

This package takes the values from one table and inserts them into another. I have looked at the table that it would be taking the values from, and the column shipto is not null.

The only difference is see is in the structure of the two tables. The temp table allows nulls on that column, where the real table does not. Both tables have the column as a varchar(20).

I notice in the Data flow for this there is a check box that says check constraints; would unchecking this solve that issue? Because the column is not null.

Thanks for any help you can provide, and I will post any additional info that may be needed. Thank you.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    There are a couple possibilities:

    1. There is a null in your source table. Your target table does not allow null values in that column. There are a couple options. If you’re using a data source straight from a table, use a SQL command instead and in the query, handle the null:

      SELECT field1, field2, isnull(shipto, ”) field3, field4, ….
      FROM Table

      You can use whatever you want in the empty string above to replace null values with a more acceptable value.

      If you don’t want to do this, you will either have to allow nulls in the target database or figure out why there is a null in the source database table and make sure that no longer happens.

    2. Fields are unmapped. You have values in the source that are not mapped into the destination fields.

    3. Other transformations between the source and destination are introducing NULL values.

    • 0