Issue with the MySQL ODBC Driver for Microsoft Excel

Hello.

Did you set up the DSN in windows (see MySQL :: MySQL Connector/ODBC Developer Guide :: 5.3.1 Configuring a Connector/ODBC DSN on Windows with the ODBC Data Source Administrator GUI)

To set up DSN for 32-bit on 32-bit machine or 64-bit on 64-bit machine use C:\WINDOWS\SYSTEM32\odbcad32.exe

To set up DSN for 32-bit on 64-bit machine use C:\WINDOWS\SYSWOW64\odbcad32.exe

Which version you need depends on which version of office you are using (32-bit or 64-bit), but you may set up both ...

See also MySQL :: MySQL Connector/ODBC Developer Guide :: 6.5 Using Connector/ODBC with Microsoft Word or Excel.

Kind Regards

Gerhard

Same problem for me.

I have windows 10 machine, Microsoft 365 Applications for Enterprise 32bit.

Exact same error. I've been using MySQL ODBC connectors for ten years without issue. My PC was recently reimaged and I haven't been able to restore this functionality since.

I've tried the 5.3 and latest 8.0 ODBC connectors, both 32 and 64 bit versions..

Hi,

you tried both - 32 bit and 64 bit - means you installed the drivers AND set up the ODBC for 32-bit in C:\WINDOWS\SYSWOW64\odbcad32.exe?

Kind Regards

Gerhard

I'm also having this problem, running Microsoft® Excel® for Microsoft 365 MSO (Version 2206 Build 16.0.15330.20260) 64-bit under Windows 11.

The MS docs don't say anything about needing to create a DSN after installing the drivers. That said, I've tried it, and get the same result.

@Gerhard, I notice that when regardless of whether I install the 32- or 64-bit connector, the MySQL ODBC Connector only appears in the `Add` list for `C:\WINDOWS\SYSTEM32\odbcad32.exe`, not `C:\WINDOWS\SYSWOW64\odbcad32.exe`.

I also notice that under `C:\WINDOWS\SYSTEM32\odbcad32.exe`, I am given the option to user either the ANSI and Unicode driver. Should it matter?

Hello,

Perhaps you need to install https://dev.mysql.com/downloads/connector/net/ in addition to the odbc driver.

Kind Regards

Gerhard

I have come to learn more about my situation. This had been working, without need for me to create DSN files. Then there were changes made by IT on Cyberark that coincide with the introduction of the problem.

I worked with out IT folks to see if they could tweak Cyberark to make it work. They couldn't figure it out.

Then another person in the group found that he could do

Data--> Get Data --> From Other Source (DO NOT USE FROM DATABASE) --> From ODBC and create a DSN file.

This means the existing functionality is broken and spread sheets with such data pulls cannot be shared without sharing the DSN file.

So it works but it is very kludgy.

Of course Microsoft will say not their problem and IT /CyberArk folks will say not their problem and there is little to look at to debug exactly what is going on.

I installed and restarted Excel. Same problem. <Learn more> message that loops me back to installing ODBS connectors that are already loaded.

You already narrowed down your problem to changes in IT security (privileged access)?

Maybe the earlier working connection to your database is now blocked by access restrictions and you are forced to use another way to connect.

Yes, I've tried this based on this post here. No change.

Yeah, I also discovered that the old way of doing things via "other source" and DSN file still works.

It seems to be a MySQL-specific problem.