IM002: The driver isn't found

A connection fails with SQLSTATE IM002, for example “[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified”, even though the driver seems to be installed.

Windows, any ODBC application; especially with 64-bit Office on a workstation on which only the 32-bit driver is registered, or vice versa.

IM002 is reported by the Driver Manager: for the bitness of the application, it finds no Wkl OData driver or no data source with the given name. The driver list and the system data sources exist separately for each bitness: a 32-bit application sees only the 32-bit entries, a 64-bit application only the 64-bit entries. The Driver Manager looks up a driver name only under HKEY_LOCAL_MACHINE. User data sources (under HKEY_CURRENT_USER), by contrast, apply to both bitnesses; such a data source points to exactly one DLL and can therefore be loaded only in that DLL's bitness.

Up to version 0.6.0, the driver itself also reported an invalid connection string with IM002, recognizable by the prefix [Wkl][OData] and the keyword named. As of version 0.7.0, it reports it with 08001 or 28000 (see Exceptions).

1. Read the message. If it starts with [Wkl][OData] and names a reason from the connection (URL, PWD, ROLE …), you're working with driver version 0.6.0 or older: correct the connection string.
2. Otherwise, check the bitness of the application (Access: File > Account > About Access) and open the ODBC Data Source Administrator of the same bitness. If Wkl OData doesn't appear on the Drivers tab, reinstall the package; see Deploy the driver.
3. If the connection names DSN=…, create the data source in the administrator of the same bitness – as a system data source, or as a user data source, which is then visible to both bitnesses.

The ODBC Data Source Administrator for the application's bitness shows Wkl OData on the Drivers tab, and Test in the driver's dialog reports the connection.

• Deploy the driver to workstations
• Link a table in Access