SSIS: version of ODBC source is not compatible with this version of the dataflow
<p>I'm using Visual Studio 2015 to create a simple SSIS package.  The data source is a DB2 database, and I'm using an ODBC driver on my workstation to connect to DB2.  The target is SQL Server 2014.</p>

<p>The package runs fine locally, but whenever I run it on the server, I'm having trouble with the ODBC data source.  The driver on the server is the exact same one with the exact same name as the one on my workstation.  </p>

<p>To get the package into the server, I've imported the dtsx file into SSIS in Stored Packages. I've also tried to deploy the project to the Integration Service Catalog, but I get one of these failures related to the ODBC source when doing so --</p>

<ul>
<li><code>The version of ODBC File Source, clsid {xxx} is not compatible with this version of the Data Flow.</code> </li>
<li><code>The component is missing, not registered, not upgradeable, or missing required interfaces. The contact information for this component is "ODBC Source;Connector for Open Database Connectivity (ODBC) by Attunity; Attunity Ltd.; All Rights Reserved; http://www.attunity.com</code></li>
</ul>

<p>I've also tried using a file based ODBC source instead of a system one with that file in a shared folder on the server.  Again, it runs fine in VS but not on the server.</p>

<p>I've looked at the dtsx file (xml based) and I suspect that there is a conflict with the DTSID for the ODBC driver.  I'm not sure how that works but it seems like that ID would be unique for each computer and that SSIS is getting is trying to use the workstation's DTSID on the server.</p>

<p>I'm a bit new to SSIS and Visual Studio so I'm hoping I'm assuming there is a straightforward way to run packages developed on a workstation at the server without these hangups.  I just can't find anything specific to this problem anywhere.</p>

<p>We do not have VS or SSDT installed on the server.</p>

<p>EDIT: I added a second sentence in the 2nd error message above.  It refers a connector provided by Attunity, which is something I don't understand.  The ODBC driver installed on the system is from Data Direct.  The CLSID returned in the error message is also associated with an Attunity connector in the server's registry.</p>

<p>There are no ODBC drivers from Attunity showing up in either of the ODBC managers, so it's possible that these are somehow part of a default install or were installed when our server used to have SSDT and VS installed directly on it and were never uninstalled.  Or, something else?  </p>