"Invalid column type from bcp client for colid xx."

• Duran

  SSChampion

  Points: 13259

  More actions

  November 22, 2017 at 9:44 pm

  #409789

  Hello,

  I have an issue with transferring some data from prod to uat, the two tables are identical. I first thought this might have something to do with a view that used the table, but having taken that out of the equation, I am still facing the same issue. I have tried all the combinations of nulls, constraints, etc., that are available in the ole db destination, but I am stuck. I configured an error output to a flat file, and all the rows ended up going into it. I'm stuck, can anybody point me in the right direction? I'd really appreciate it.
  Here are the errors I am getting...

  [UAT tablename Destination [221]] Error: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
  An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80004005 Description: "Invalid column type from bcp client for colid 54.".

  [UAT tablename Destination [221]] Error: SSIS Error Code DTS_E_INDUCEDTRANSFORMFAILUREONERROR. The "UAT tablename Destination.Inputs[OLE DB Destination Input]" failed because error code 0xC020907B occurred, and the error row disposition on "UAT tablename Destination.Inputs[OLE DB Destination Input]" specifies failure on error. An error occurred on the specified object of the specified component. There may be error messages posted before this with more information about the failure.

  [SSIS.Pipeline] Error: SSIS Error Code DTS_E_PROCESSINPUTFAILED. The ProcessInput method on component "UAT tablename Destination" (221) failed with error code 0xC0209029 while processing input "OLE DB Destination Input" (234). 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.

  How can I use the (221) and (234), to help me track the issue down? If in fact, I can.
  Regards,
  D.

• John Mitchell-245523

  SSC Guru

  Points: 148809

  More actions

  November 23, 2017 at 3:55 am

  #1969337

  As far as I know, those numbers identify the components of the package.  Since the error message provides the respective names of those components (UAT tablename Destination.Inputs[OLE DB Destination Input] and OLE DB Destination Input), I don't think the numbers are really going to help in your investigation.

  John

• Phil Parkin

  SSC Guru

  Points: 247109

  More actions

  November 23, 2017 at 7:36 am

  #1969346

  They look like lineage Ids to me. You should be able to track down the columns they belong to by opening the package in SSDT. Have a read here, for example.

  ---