Easysoft ODBC-ODBC Bridge

What does "[Easysoft ODBC][unixODBC][Driver Manager]Can't initiate unicode conversion" mean?

Last Reviewed:
18th January 2024

In older versions of unixODBC, this message might be:

[Easysoft ODBC][unixODBC][Driver Manager]Can't initiate unicode conversion

This ODBC diagnostic is returned by the unixODBC Driver Manager. The diagnostic may be returned by the unixODBC Driver Manager when calling SQLConnect, SQLDriverConnect or SQLBrowseConnect and results in a SQL_SUCCESS_WITH_INFO return value. As SQL_SUCCESS_WITH_INFO is not an error return, you should look at any subsequent diagnostics if your connection fails, as this one does not cause connection failures. It means unixODBC was built with iconv support, but could not find a conversion map in iconv. It is not a matter of concern for most people.

iconv support in unixODBC is used to translate ASCII to UNICODE and vice versa. If your application is not making UNICODE ODBC calls (SQLxxxW functions), and most do not, you are not using iconv in unixODBC anyway.

Some releases of the Easysoft ODBC-ODBC Bridge contain a unixODBC Driver Manager that was built with iconv support unnecessarily. Red Hat distribute unixODBC with iconv support. If you build unixODBC yourself, you will probably get iconv support by default. You can disable iconv support when configuring a unixODBC build using the configure option --enable-iconv=no.

Applies To

Knowledge Base Feedback

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

(* Required Fields)