Easysoft ODBC-ODBC Bridge

Why does my second connection to Microsoft Access hang?

Last Reviewed:
4th January 2024

Easysoft have seen problems making more than one simultaneous connection from UNIX through the Easysoft ODBC-ODBC Bridge to the Microsoft Access ODBC driver (specifically hanging). We think that the Microsoft Access ODBC driver DLL may contain some shared data that is incompatible with a multi-threaded ODBC-ODBC Bridge server (which is the default configuration). You can work around this problem by changing the ODBC-ODBC Bridge Server to run multi-process instead of multi-threaded.

According to Microsoft's web site:

Known Issue: ODBC Jet driver in multithreaded environments
Component: ODBC Jet driver
When running in a multithreaded or stress environment such as IIS, it is recommended not to use ODBC because
of issues with threading in the driver as well as the Jet engine. The recommendation for this situation
is to work with the OLE DB provider for Jet.

To make the ODBC-ODBC Bridge Server run multi-process instead of multi-threaded, use the ODBC-ODBC Bridge Server administration interface (http://mywindowsmachine:8890). Select Configuration > Change and then choose the MultiProcess checkbox. Click on Submit. If the ODBC-ODBC Bridge Server configuration page has an "AutoUpdateConfiguration" checkbox and it is not checked, you will need to restart the ODBC-ODBC Bridge Server Service. Versions of the ODBC-ODBC Bridge Server administration interface without the "AutoUpdateConfiguration" checkbox do not need the service restarting.

Update to this According to Microsoft's web site, JET 4 is now thread-safe.

You can ascertain if you have JET 4 by clicking on the Drivers tab in ODBC Administrator and examining "Microsoft Access Driver". If it says 4.xxxx then you should not need to switch the ODBC-ODBC Bridge Server in to MultiProcess mode (as detailed above).

Applies To

Knowledge Base Feedback

* Did this content help you?
* Please select one option based on your first choice:

(* Required Fields)