Certifications & Credly badges:
Joost has no Certifications & Credly badges yet.
Global Masters badges:
Joost has no Global Masters badges yet.
Followers:
Joost has no followers yet.
Following:
Joost has not followed anybody yet.
User bio
404 bio not found
Member since Nov 8, 2018
Posts:
Joost has not published any posts yet.
Replies:
Hi Mark Anthony,
My input is a bit late but decided to share my experience anyway.
I was having similar issues. In my situation, I am developing SSIS packages (Visual Studio 2017) which import data from a Cache database via ODBC. The destination is a SQL Server 2016 database. While developing in Visual Studio, the SSIS source points to a 32 bit ODBC connection and that works fine. However , after deploying to the SSIS Catalog the package was supposed to use the ODBC 64 version (which is installed on the server on which the packages are deployed) but I got errors.
However, I noticed my Visual Studio project was targeted at a SQL Server 2017 version (these values can be set in the properties of your Visual Studio project) After changing the SSIS project to a target platform of SQL Server 2016 and deploying again to the SSIS Catalog, the deployed package was able to use to 64 ODBC driver and the package executed without issues.
I know you were using different versions of VS and SQL Server than me, but you also might have target version issues.
Regards,
Joost