Error "Cannot load client library: <path libs>" in Products: IBDAC, UniDAC (InterBase, FireBird), ODBC (InterBase, FireBird)
Issue
When working with IBDAC, UniDAC, or the Devart ODBC Driver for InterBase or Firebird, you may encounter the error:
"Cannot load client library: <path libs>"
This error typically indicates one of the following issues:
- The specified client library is missing or not found at the given path.
- There is a bitness mismatch between the client library and the application (e.g., 32-bit vs. 64-bit).
Explanation
Each of the listed products interacts with the InterBase or FireBird server via a client library, using a special API. However, the client libraries themselves are not bundled with IBDAC, UniDAC, or the ODBC driver.
- The InterBase client library is provided with InterBase.
- The FireBird client library can be downloaded from the official FireBird website.
Product-Specific Instructions
ODBC
- You need to deploy the InterBase library and then specify its path in the DSN settings, following the guidance at Connecting ODBC Driver for InterBase.
- Ensure you have the appropriate client library to interact with your InterBase server.
- You may install the InterBase Developer Edition and extract the required library from it; you may also reach out to InterBase technical support for details on downloading and installing the InterBase client.
IBDAC
- You need to deploy the InterBase client library file and define its path in the TIBCConnection.ClientLibrary property.
- Ensure you have the appropriate client library to interact with your InterBase server.
- You may download the FireBird server archive from the official FireBird site and retrieve the necessary library from there; feel free to consult FireBird technical support for advice on downloading and installing the FireBird client.
UniDAC
- You need to deploy the InterBase client library file and define its path in the TUniConnection.SpecificOptions.Values['ClientLibrary'] property.
- Ensure you have the appropriate client library to interact with your InterBase server.
- You may download the FireBird server archive from the official FireBird site and extract the required library from there; feel free to contact FireBird technical support for guidance on downloading and installing the FireBird client.

Note: Acquiring and installing the InterBase or FireBird client libraries is not part of the Devart product functionality. For assistance, please contact InterBase or FireBird support.
Related Articles
"Cannot obtain Oracle Client information from registry" Error
The error message "Cannot obtain Oracle Client information from registry" when working with Oracle typically indicates that either the Oracle Client is not installed on your system, or there is a mismatch in the bitness between your application and ...
ODBC Data Sources (64-bit) Data Source config error
If you are encountering the "GDS Function not linked" error, this is because the Client Library field currently points to our Devart InterBase ODBC Driver library (DevartODBCInterBase.dll) instead of the InterBase client library (ibclient64.dll for ...
The error "Cannot obtain Oracle Client information from registry"
The error "Cannot obtain Oracle Client information from registry" means that you don’t have Oracle client installed or the bitness of your application doesn't match the bitness of your Oracle Client. ...
Error 193 While Creating ODBC Connection in ODBC Administration
If you encounter Error 193 while creating an ODBC connection, it's important to note that our ODBC drivers currently do not support Windows ARM. We are actively working on expanding compatibility and will provide updates on the possibility of ...
[Devart][ODBC][QuickBooks Desktop] Could Not Start QuickBooks
When attempting to test the connection for the Devart ODBC Driver for QuickBooks Desktop, the following error may occur: "[Devart][ODBC][QuickBooks Desktop] Could not start QuickBooks" This issue typically indicates that the connection prerequisites ...