ODBC Not allowing to add or configure existing sources

[GregWD40]

I have a new MAC M3 max
Running Windows 11 pro
When I search for ODBC the only one that comes up is the 32-bit. I right click and view location and open the 64 bit version. But I cannot add or configure existing connections see screenshot. I am currently trying to add a Cloudera Impala connection: getting error 193 "the setup routines for the Cloudera ODBC driver could not be loaded to to system error code 193. but is a similar message when trying to configure the Excel USER DSN.

 

[shacho]

I was having this problem on my Win 11 64 ARM VM when trying to set up a Snowflake driver. I noticed that the links in the Start Menu for 32 and 64 both point to the same, wrong executable for the ODBC Administrator console. Windows version build fail, perhaps. The right one is C:\Windows\SysWOW64\odbcad32.exe . When I ran that I was able to set up my driver and use it properly. Even though this is the expected path for the 64 bit console, it reports itself to be for 32 and I think it uses 32 bit drivers. You might want to try installing both versions of you driver.

 

[HariprasathM]

I have a new MAC M3 max
Running Windows 11 pro
When I search for ODBC the only one that comes up is the 32-bit. I right click and view location and open the 64 bit version. But I cannot add or configure existing connections see screenshot. I am currently trying to add a Cloudera Impala connection: getting error 193 "the setup routines for the Cloudera ODBC driver could not be loaded to to system error code 193. but is a similar message when trying to configure the Excel USER DSN.
View attachment 22177

I am also having the same issue

 

[shacho]

Try my solution above - it might work.
In short:
1) Install the 32-bit ODBC driver
2) Launch the 32-bit configuration menu directly from C:\Windows\SysWOW64\odbcad32.exe
3) Configure your DSN

 

[Casilaze]

Try my solution above - it might work.
In short:
1) Install the 32-bit ODBC driver
2) Launch the 32-bit configuration menu directly from C:\Windows\SysWOW64\odbcad32.exe
3) Configure your DSN

if use the 32 bits obdcad32 in syswow64 folder to add DSN, then this error will occur.
i deduced the root cause is arm-based windows problem.

 

[shacho]

It looks like the issue might be between your application and the driver. There are three components to consider: the application, the driver, and the ODBC host. By using a 32 bit driver and obdcad32 in syswow64, your driver and ODBC host are aligned. But probably the application you are trying to use is 64 bit and not configured to work with a 32 bit driver. 64 bit Excel, as an example, can work with either a 32 or 64 bit driver, but some applications cannot.

 

[BrunoA6]

Bonjour,
J'ai le même problème avec ACCESS. avez vous trouver une solution ?
Hello,
I have the same problem with ACCESS. Have you found a solution?

 

[EtienneP2]

Same issue