Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 9189143
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 17, 20262026-06-17T20:10:43+00:00 2026-06-17T20:10:43+00:00

I have an SSIS package that is using a Lookup: Target and Source use

  • 0

I have an SSIS package that is using a Lookup:

  • Target and Source use OLE DB connections, looking at SQL Server 2008 R2.
  • Lookup is using Full cache, and an OLE DB connection manager (defaults).
  • The Lookup looks for a key of 13 columns. One of them is of type Date, which fails validation later.

It all works well from my machine, naturally.
I can install the package on production, but when running it it quickly fails on validation of the Lookup:

input column [ColumnName] (238) and reference column named [ColumnName] have incompatible data types

This is clearly a lie – they have the same types. It looks like this is a known problem of the Lookup component:

  • Lookup claims incompatible data types
  • SSIS Lookup Component Error: output column ‘x’ and reference column named ‘y’ have incompatible data types

In both cases, some people suggested running the package in 32 bits solved their problem. However, my package fails connection to the server when running in 32 bits…

What am I missing? Should I install additional x86 providers?
Is there a good way of fixing the Lookup?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-17T20:10:44+00:00Added an answer on June 17, 2026 at 8:10 pm

    As a workaround, I was able to open the Microsoft Visual Studio 2008 Shell on the production server, and run the package through there. Since this is a one-time migration job, I don’t really mind.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have an SSIS package that queries data from a view using an SQL
I have a [SQL 2008] SSIS package that takes a CSV text file and
I have an SSIS package deployed to Sql Server 2008. This package runs fine
I have a SSIS package that reads from a flat file source. The target
We have an SSIS package that ran in production on a SQL 2008 box
I am running a SSIS package using SQL Server 2008 Job. The package crash
I have an OLE DB Command component in an SSIS Package that runs an
I have a package that is developed in SSIS 2012 using Visual Studio 2010.
I have an SSIS package that takes data from Tables in an SQL database
I have a SSIS package that I saved using the import wizard in SSMS.

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.