ODBC conection broke after upgrade

I had an ODBC connection to Denodo which worked perfectly under 2019.1. I recently upgraded to 2019.3 and now I'm getting an error with my connection.

"The specific DSN contains an architecture mismatch between the Driver and Applicaion".

Anyone else receive connection errors after upgrading? If so, how did you resolve. I'm hoping I can roll back to a previous version so I can run my workflow.

Workflow

Accepted answers

afinzerillo

That was on the right track, but reversed. I needed to use the 32-bit driver, but was using the 64-bit. I had to wipe out all my Denodo drivers and Alteryx installs and reapply from the ground up. Got it to work eventually.

All comments

BrandonB

I took a look at their documentation found here:

https://community.denodo.com/kb/view/document/How%20to%20connect%20to%20Denodo%20from%20Alteryx?category=Northbound+Connections

Denodo isn't on the Alteryx list of supported data sources (https://www.alteryx.com/data-sources) but it looks like the Denodo team did a test on functionality for Alteryx Designer 2018.4.5.55178. I think that it would be worth reaching out to the Denodo support team to see if they made any changes to their driver for the update.

I have also seen this happen when people are trying to use a 32bit driver in the 64bit ODBC manager. Is there any chance that you are using a 32bit driver rather than a 64bit?

Rlavelle

I had this issue with DB2. We had to update IBM drivers for 32bit to 64bit ODBC compatibility.

afinzerillo

Quick Links

This months top contributors

atcodedog05 19458

Qiu 15866

binu_acs 15708

MarqueeCrew 13708

apathetichell 13703