This section contains additional technical information relating to the deployment of the Easysoft XML-ODBC Server.
Invalid characters found in the ODBC diagnostic text or XML result set output from the Easysoft XML-ODBC Server are usually the result of using a version of the unixODBC driver manager prior to 2.2.2, which had some Unicode problems.
These older UnixODBC releases expected big endian input data and converted data to big endian rather than native endian format, a restriction which has now been removed.
All versions of the Easysoft XML-ODBC Server contain at least unixODBC 2.2.2 and should not have this problem, but it is possible that you may have elected to use an existing installation of unixODBC when the Easysoft XML-ODBC Server was installed.
All versions of the Easysoft XML-ODBC Server contain at least unixODBC 2.2.2 and should not have this problem, but it is possible that an existing installation of unixODBC may have been selected for use when the Easysoft XML-ODBC Server was installed.
If this is the case then re-run the the Easysoft XML-ODBC Server installation, choose to install the included unixODBC and then ensure that the dynamic linker picks up this new version of the driver manager, rather than the previous version.