Devart Forums

I have several commercial applications that as of last week stopped opening and return the error message "Unable to load odbcji32.dll" when launching. Several have not been updated in many months so our code has not changed. We are using UniDAC 6. In several apps specifically 6.2.8 and 6.2.9. We are seeing this error on Windows 10 and also on Windows 7 and 8 when Office 2016/365 is installed and updated. This seems to me to be related to the Windows 10 November update and/or the recent Office 2016/365 updates. Right now I cannot find a work around.

Has anyone else seem this error and have any suggestions?

The first error message is:
Title: "ODBC driver for Microsoft Access installation problem"
Message: "Unable to load odbcji32.dll"

The second error message is:
"[Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle on SQL_HANDLE_ENV failed."

The third error message is:
"The operating system is not presently configured to run this application."

Any ideas?

Found the problem. Hope this helps someone else with the same errors.

It looks like an Office 2016/Office 365 update changes the path for the Access ODBC Driver.

In the registry browse to:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBCINST.INI\Microsoft Access Driver (*.mdb, *.accdb)

The driver and setup values are:
C:\Program Files (x86)\Microsoft Office\root\VFS\ProgramFilesCommonX86\Microsoft Shared\Office16\ACEODBC.DLL

The values should be:
Driver: %WINDIR%\system32\odbcjt32.dll
Setup: %WINDIR%\system32\odbcjt32.dll

Once this change is applied the errors go away.

hello,

We installed both Windows 10 and Office 2016. Nothing changed in the registry, and UniDAC still works with both new and old databases correctly. Please clarify, after which product installation did this record appear in the registry?

I discovered this problem with odbcji32.dll on our Windows 10 workstations today...

Doing a bit of searching there were quite a few reports that a recent Windows 10 update messed up several system files. The recommendation given was to install the Access Database Engine. I did this and our problems were fixed

So not a UniDAC problem - but nice to know a fix - here is the helpful article:

http://www.lucion.com/kb-database-connection-error.html

I have same problem with Windows 8.1 and Office 365. Unfortunately, the solution didn't help me. Connection start working correctly, when I uninstalled Office.

As I wrote earlier, we couldn't reproduce the issue. Try the above solutions.

alexbozhko wrote:I always liked Phallosan Forte and have same problem with Windows 8.1 and Office 365. Unfortunately, the solution didn't help me. Connection start working correctly, when I uninstalled Office.

I had the same problem on Windows 8 recently and I upgraded to Windows 10 finally and that fixed it and it's working fine now.

Glad to see that the issue was resolved. If you have any further questions, feel free to contact us.

We are glad that the issue was rectified. We will add the description of the issue solution to our Knowledge Base.

johnbitner wrote: ↑Tue 22 Dec 2015 14:09 The first error message is:
Title: "ODBC driver for Microsoft Access installation problem"
Message: "Unable to load odbcji32.dll"

The second error message is:
"[Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle on SQL_HANDLE_ENV failed."

The third error message is:
"The operating system is not presently configured to run this application."

Any ideas?

I want to help you out buddy as I too frequently render these kinds of situations in my Access Database. Recently I and my friend got stuck in this type of ODBC error:

Access 1919 – configuring ODBC data source Error
Access Run-time 3146 ODBC Call Failed Error

We both have fixed this error manually and by own. if you want to check the manual steps then you can may be it work for your problem also.

Thank you for the provided information. Perhaps it will be useful if our users have similar problems

You can find the solution to the problem with the download of odbcji32.dll by contacting the Microsoft Office support.

Perhaps the proposed solution will help our users get rid of the issue, however, reinstalling the Microsoft Office package is not always easy to implement, for example, in a corporate environment. Therefore, for accurate explanations, you should contact Microsoft Office support.

We are glad that you found a solution. Please let us know if you need any assistance.