nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Oracle ODBC Error 1114: A dynamic link library (DLL) initialization routine failed.

gpuckett

I am receiving this error when using the Database Open Table dialog in JMP Pro 9.0.3 64bit. I am able to use this ODBC connection in other applications without issue and the "test connection" feature also works without issue in the ODBC interface.

The full error is:

Specified driver could not be loaded due to system error 1114: A dynamic link library (DLL) initialization routine failed. (Oracle in Oracle_11gR2_x64_1, C:\Oracle11gR2_x64\product\11.2.0\client_1\BIN\SQORA32.DLL).

Accepted answers

Jeff_Perkinson

This question is probably best handled by Tech Support, but I may be able to point in some good directions.

You're running JMP in 64-bits which means that you must have a 64-bit ODBC driver for it to work. I'm concerned that the error message references a dll with 32 in the name.

Can you see if that DLL exists in the location in the error message? Also, can you confirm that you have a 64-bit driver?

-Jeff

All comments

Jeff_Perkinson

This question is probably best handled by Tech Support, but I may be able to point in some good directions.

You're running JMP in 64-bits which means that you must have a 64-bit ODBC driver for it to work. I'm concerned that the error message references a dll with 32 in the name.

Can you see if that DLL exists in the location in the error message? Also, can you confirm that you have a 64-bit driver?

-Jeff

gpuckett

The driver in this location is the 64 bit driver and the file does exist.

pmroz

Was a solution found for this error? I'm encountering it on one of my PCs. The Oracle driver is 64-bit, and JMP 14 is 64-bit.

Jeff_Perkinson

I looked at the tech support track that was created by the original poster. Unfortunately, what resolved the problem isn't entirely clear. There was some uninstallation/reinstallation of older and newer versions of JMP and ODBC drivers and it started working. We wouldn't expect uninstalling and reinstalling any version of JMP would affect any other. It's a bit of mystery.

Contact Tech Support if you want some help trying to track it down in your instance.