Symptoms

When you try to create an ODBC DSN for drivers that are provided by Microsoft Access in the Data Sources ODBC Administrator, the attempt fails. This problem occurs if you're using a Click-to-Run (C2R) installation of Office. Depending on the version of Office, you may encounter any of the following issues when you try this operation:

• The ODBC drivers provided by ACEODBC.DLL are not listed in the Select a driver dialog box.
• You receive a "The operating system is not presently configured to run this application" error message.
• You receive an "Unable to load odbcji32.dll" error message.
• You receive a "The driver of this User DSN does not exist. It can only be removed" error message together with the platform showing N/A.

Affected drivers:

• Microsoft Access Driver (*.mdb, *.accdb)
• Microsoft Access Text Driver (*.txt, *.csv)
• Microsoft Excel Driver (*.xls, *.xlsx, *.xlsm, *.xlsb)

Resolution

Microsoft suggests installing Microsoft Access 2013 Runtime (ref: https://docs.microsoft.com/en-US/office/troubleshoot/access/cannot-use-odbc-or-oledb).

You should download the 32-bit version of that runtime (AccessRuntime_x86_en-us.exe) because our software is 32 bit.

The standard installation procedure may fail and report that you've already installed the 64-bit version of Microsoft Office components. In this case, you should start a command prompt and execute the following command:

AccessRuntime_x86_en-us.exe   /passive

This command only installs the 32-bit version of ODBC drivers. Now, you can add ODBC DSN for Access, Excel, or CSV files.

Note: You should use the 32-bit version of ODBC Administrator for that.

Possible problems

The installation package (AccessRuntime_x86_en-us.exe) may report installed incompatible packages like "Microsoft Access Database Engine 2010". In this case, you should uninstall this package using the standard Windows control panel.