Hi. We are getting a very strange error when trying to build a report on a Power BI Report Server, connecting via the ODBC Driver 0.9.7.1195. The driver is installed on the Report Server. On a first report refresh everything works just fine, which means that the driver is installed an configured correctly. But then we get the error “ODBC: ERROR [IM003] Specified driver could not be loaded due to system error 1114: A dynamic link library (DLL) initialization routine failed. (Arrow Flight SQL ODBC Driver, C:\Program Files\Dremio Connector\Arrow Flight SQL ODBC Driver\arrow-flight-sql-odbc.dll)”. What is interesting, eveything works well when running on Windows Server 2019, which implies that there might be some issues with dependencies or so.
We enabled ODBC trace as per driver docs, no additional errors there. Tried to update MSVC to recent version, no luck. Do you have any ideas what might be the root cause of the problem?
@devozerov Seems like an OS mismatch, are you able to validate below?
https://forums.oracle.com/ords/apexds/post/system-error-1114-a-dynamic-link-library-dll-initialization-2931
The error “ODBC: ERROR [IM003] Specified driver could not be loaded due to system error 1114: A dynamic link library (DLL) initialization routine failed” indicates that the ODBC driver’s dynamic link library (DLL) could not be loaded or initialized by the system. This often points to issues with the driver’s installation, configuration, or environment.
Common causes and solutions include:
-
Incorrect Driver Installation or Missing Files:
The necessary DLL files for the ODBC driver might be missing, corrupted, or in a location not accessible to the system or application attempting to load them.
- Solution: Reinstall the ODBC driver, ensuring the installation completes successfully and all required files are placed in the correct directories. Verify the integrity of the installed files.
-
32-bit vs. 64-bit Mismatch:
An application or system expecting a 64-bit ODBC driver might be attempting to load a 32-bit driver (or vice-versa).
- Solution: Ensure that the architecture (32-bit or 64-bit) of the ODBC driver matches the architecture of the application or system attempting to use it. If using a 64-bit application, install the corresponding 64-bit ODBC driver. Use the correct ODBC Data Source Administrator (32-bit or 64-bit) to manage DSNs.
-
Incorrect System PATH Environment Variable:
The system’s PATH environment variable might not include the directory where the ODBC driver’s DLLs are located.
- Solution: Add the path to the directory containing the driver’s DLLs to the system’s PATH environment variable. Restart the application or system for the changes to take effect.
-
Permissions Issues:
The user account or service running the application attempting to load the driver might not have sufficient read or execute permissions on the driver’s DLL files or their containing directory.
- Solution: Grant appropriate read and execute permissions to the relevant user account or service for the driver’s installation directory and DLL files.