SSIS package error: ERROR [IM014] [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application

Question

SSIS package error: ERROR [IM014] [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application

Marvin Xu 1

Hi,
Please help me solve the below issue,

I use SSMS v17.8.1 to build a package; it runs successfully on SSMS, but fails when I create a SQL job to run it. It also fails when I use MS data tools to build a similar package.

My testing:
I used SQL 2017 Execute package Utility to run the package; there is no issue. I checked the ODBC drive, I use the 32-bit tool, and it works on MS Excel and Access, but not SS data tools "recently".
However, the package runs with no problem on my Win10 PC. but not MS 2019 server.

Environment,
data source: ODBC 32-bit driver

Data destination: MS server 2019, MS SQL 2019 Std, SSMS v 17.8.1, Visual Studio 15.9.50

Marvin Xu 1 Reputation point

2022-11-04T15:46:34.827+00:00

Another hint:
I assume the issue is what code Microsoft uses to call the ODBC driver.
Here is why:
if use .Net Framework Data Provider for Odbc, it works with no issue

But, I am not sure what provider SS Agent and SSDT use. it doesn't work on the MS 2019 server, but it works on my Win10 PC.
Yitzhak Khabinsky 26,586 Reputation points

2022-11-06T14:23:44.45+00:00

@Marvin Xu ,

A couple of questions to ask.

I use SSMS v17.8.1 to build a package;

SSIS projects and packages are built in Visual Studio.

And now is a real question.
What is the reason to use ODBC driver?
What is your source database?
If it is SQL Server, why not to use Microsoft OLEDB driver?
Marvin Xu 1 Reputation point

2022-11-09T23:29:43.053+00:00

okay, here is my answer to your questions,
first, to access that data I only have one option which uses a third-party build interface to access the data; it is 32-bit ODBC driver.
the source data isn't a database but a data file system.
hope this would answer your questions,
thanks for your time.

1 answer

Your answer

Marvin Xu 1 Reputation point

2022-11-04T15:46:34.827+00:00

Another hint:
I assume the issue is what code Microsoft uses to call the ODBC driver.
Here is why:
if use .Net Framework Data Provider for Odbc, it works with no issue

But, I am not sure what provider SS Agent and SSDT use. it doesn't work on the MS 2019 server, but it works on my Win10 PC.
Yitzhak Khabinsky 26,586 Reputation points

2022-11-06T14:23:44.45+00:00

@Marvin Xu ,

A couple of questions to ask.

I use SSMS v17.8.1 to build a package;

SSIS projects and packages are built in Visual Studio.

And now is a real question.
What is the reason to use ODBC driver?
What is your source database?
If it is SQL Server, why not to use Microsoft OLEDB driver?
Marvin Xu 1 Reputation point

2022-11-09T23:29:43.053+00:00

okay, here is my answer to your questions,
first, to access that data I only have one option which uses a third-party build interface to access the data; it is 32-bit ODBC driver.
the source data isn't a database but a data file system.
hope this would answer your questions,
thanks for your time.

Answer 1

ZoeHui-MSFT 41,496

Hi @Marvin Xu ,

fails when I create a SQL job to run it. It also fails when I use MS data tools to build a similar package.

What's the error message?

In the SQL Agent Jobs' configuration, the job step properties dialog: General > Advanced tab there is a checkbox labelled "32-bit runtime".

Have you chosen this to run the package if you are using ODBC 32bit?

There is a Run64bitRuntime property at the Project level in VS that defaulted to TRUE. You may set it to false.
Regards，

Zoe Hui

If the answer is helpful, please click "Accept Answer" and upvote it.

Marvin Xu 1 Reputation point

2022-11-10T18:56:25.72+00:00

Hi Zoe,

I've changed it to 32-bit runtime; please check the below screenshot of the error I got.
Thanks for your time,

Marvin
Marvin Xu 1 Reputation point

2022-11-10T19:06:15.297+00:00

Hi Zoe,

On my Win10 computer, I use Visual Studio to build the same package; it runs with no problem, so I deployed it on the server, which gave me an error when I tried to make it automatically run in SQL jobs.
Then, on the server - (MS 2019 + SQL 2019), I used Visual Studio to open the task and run the test, but it failed too,
It feels like something is mismatched on the server.

Marvin

Share via

SSIS package error: ERROR [IM014] [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application

1 answer

Your answer