Forum Discussion
ODBC Data Source ARM64 version could not create System DSNs
PROBLEM SOLVED! it was even not complicate to find the solution.
The executable odbcad32.exe.mui was missing in the file C:\Windows\SysWOW64 so, I found the file in the C:\Windows\System32 and copied as administrator and pasted in C:\Windows\SysWOW64, and the problem disappear, drivers working find and I could finally connect to the Database to work with BI.
Ludelag I've copied odbcad32.exe.mui to C:\Windows\SysWOW64.
However I could not install the 64-bit version drivers for PostgreSQL (see for example https://www.postgresql.org/ftp/odbc/releases/REL-17_00_0002/), so what did you exactly do, because I need the 64 bit version to connect to a PostgesSQL database using Microsoft Power BI, which is 64 bits, because my Window 11 Pro is 64 bits.
Running on a M3 Pro chip via Parrallels.
- I used the workaround as described in https://learn.microsoft.com/en-us/answers/questions/1059343/odbc-64-bit-error-193To summarize the workaround: configure with the 32-bits version first and then copy over the registry setting to the 64-bits version
- You should be able to have read that only a 32bit ODBC Driver could be installed and used on the Win 11 for Arm System 21H2.
There seems to be a possibility to build / compile an 32bit Version from postgres ODBC Driver but that is not my field, so you may have to make some additional homework.
I have now updated to 24H2 win11 for ARM Pro at UTM on MBA M2 and use still the 32Bit MariaDB ODBC driver with the VB6 Programm running via the registered VB6 dll reading from XAMPP MariaDB Database edited via HeidiSQL since Fall 2022.
They have updated the Emulator Prism in 24H2.
So you could try to Update to 24H2 and try the 64bit again.
If that not works you have to go 32bit as we had to.
