Unable to use the Access ODBC, OLEDB or DAO interfaces outside Office Click-to-Run applications
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 that doesn’t expose the Access Database Engine outside of the Office virtualization bubble. 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.
- Microsoft Access Driver (*.mdb, *.accdb)
- Microsoft Access Text Driver (*.txt, *.csv)
- Microsoft Excel Driver (*.xls, *.xlsx, *.xlsm, *.xlsb)
Additionally, if you try to define an OLEDB connection from an external application (one that’s running outside of Office) by using the Microsoft.ACE.OLEDB.12.0 or Microsoft.ACE.OLEDB.16.0 OLEDB provider, you encounter a «Provider cannot be found» error when you try to connect to the provider.
Cause
Click-to-Run installations of Office run in an isolated virtual environment on the local operating system. Some applications outside Office may not be aware of where to look for the installation in the isolated environment.
Resolution
Beginning with Microsoft 365 Apps for Enterprise Version 2009, work has been completed to break ACE out of the C2R virtualization bubble so that applications outside of Office are able to locate the ODBC, OLEDB and DAO interfaces provided by the Access Database Engine within the C2R installation.
Use the following table to understand if additional components are necessary to access these interfaces within your environment:
| Current Office Installation | Additional components needed | Recommended Additional Installation |
|---|---|---|
| Microsoft 365 Apps for Enterprise, Office 2016/2019/2021 Consumer Version 2009 or later | No | — |
| Office LTSC 2021 (Volume License) | No | — |
| Office 2016/2019 Pro Plus C2R (Volume License) | Yes | Upgrade to Office LTSC 2021 (Volume License) or install Microsoft Access 2013 Runtime |
| Office 2010/2013/2016 MSI | No | — |
| No Office installation | Yes | Microsoft 365 Access Runtime |
- The Microsoft Access Database Engine 2016 Redistributable is not provided as a recommended installation because both the Access Database Engine 2016 and Microsoft 365 Apps use the same major version identifier (16.0) which may introduce unexpected behaviors. Office side-by-side detection will also prevent the installation from proceeding if this scenario is detected.
More information about creating ODBC connections
All Click-to-Run instances of Office are unable to create Machine/System datasource names from within an Office application or from the Data Sources ODBC Administrator.
Unable to load odbcji32.dll
ODBC driver for Microsoft Access installation problem
This tutorial describes how to solve «Unable to load odbcji32.dll» (ODBC driver for Microsoft Access installation problem):
«The operating system is not presently configured to run this application.»
The easiest way to fix the problem is to «Repair» the installation of the «Microsoft Access database engine 2010» from:
- Windows 10: «Settings > System > Apps & Features«, search for «access» and click on «Change» / «Repair».
- On other systems use «Uninstall or change Program» or «Repair or Remove Programs«, select the driver and click on «Repair».
If you still get the same error, uninstall and re-install the driver as described below:
1. Uninstall «Microsoft Access Database Engine»
On Windows 10 go to «Setttings > System > Apps & Features» and search for «access» .
Uninstall all versions of «Microsoft Access Database Engine» from your system.
On other systems use «Uninstall or change Program» or «Repair or Remove Programs«
Uninstall all versions of «Microsoft Access Database Engine» from your system.
2. Download and Re-install «Microsoft Access Database Engine»
Download the latest version of «Microsoft Access Database Engine (2010)» here:
http://www.microsoft.com/en-us/download/details.aspx?id=13255
Important: download the «AccessDatabaseEngine.exe» (not the _x64 version!)
Install the ODBC driver and retry.
If you cannot install because there is a 64bit component blocking, open a command prompt and run the installation using:
«AccessDatabaseEngine.exe /quiet»
Disclaimer: The information on this page is provided «as is» without warranty of any kind. Further, Arclab Software OHG does not warrant, guarantee, or make any representations regarding the use, or the results of use, in terms of correctness, accuracy, reliability, currentness, or otherwise. See: License Agreement
- ©1997-2024 Arclab®. All other trademarks and brand names are the property of their respective owners.
- info_outline
- fingerprint Cookies & Privacy
Microsoft Access Can’t Load ODBCJI32.dll Error
When accessing a Microsoft Access database, Alpha Anywhere may display an error message, «Can’t Load ODBCJI32.dll Error». To fix this error, install or repair the Microsoft Access Database Engine.
If you have installed Office 365 on your computer, you may find you can no longer connect to a Microsoft Access database.
To fix the error, install the Microsoft Access Database Engine. When prompted, select acessdatabaseengine.exe. Links for the 2016 and 2010 engines are provided below.
- Microsoft Access Database Engine 2016 Redistributable
- Microsoft Access Database Engine 2010 Redistributable
If Microsoft Access Database Engine is already installed, running a ‘Repair’ on the engine should fix the problem. A ‘Repair’ can be run through the uninstall or change a program interface for Programs and Features from the Windows Control Panel for the Microsoft Access Database Engine program.
Unable to load odbcji32 dll что делать
При работе с драйвером ODBC появляется сообщение об ошибке: Unable to load odbcji32.dll. Dll находится в папке \Windows\sysWOW64.
Я пробовал разрегистрировать и зарегистрировать библиотеку снова, но получаю другое сообщение об ошибке: Модуль «odbcji32.dll» загружен, но точка входа DllRegisterServer не найдена.
Я вхожу под учетной записью с правами Администратора, но все операции с файлом odbcji32.dll заблокированы.
Подскажите, пожалуйста, как можно решить проблему?
Изображения
| ODBCerror.png (12.9 Кб, 33 просмотров) | |
| odbcji32error.png (11.0 Кб, 48 просмотров) |
| Похожие темы | ||||
| Тема | Автор | Раздел | Ответов | Последнее сообщение |
| unable to locate file | HTTqp | Общие вопросы Delphi | 2 | 21.05.2015 22:06 |
| [Unable to connect] C# MySQL | Fiesko | C# (си шарп) | 5 | 28.07.2013 18:58 |
| Unable to load dbxora.dll. Хотя библиотека там находится? | demon-sheff | БД в Delphi | 2 | 29.03.2013 09:25 |
| Unable to load dbexpmysql.dll | >>arty | Общие вопросы Delphi | 0 | 05.04.2010 17:50 |
| Запуск Load.dll (бывшая Load.exe) в дереве проц-ов, Как запустить прогой на C# .dll-ку | kapustin | Общие вопросы .NET | 10 | 23.09.2009 22:20 |