Change in OBDC Error 182 from MYSQL
Posted: Wed Nov 07, 2018 2:57 am
I have Open Office 3.4 (but this problem is happening with 4.1.5 as wll.
I have a MYSQL 5.4 database running on a Windows 2008 File Server and accessed with a Windows 2008 Terminal Server. I use Open Office 3.4 to manage the data in a single ODB database. i also have a number of Forms (ODT files). The OBDC I used is the 5.4 Beta which has worked fine for years.
We are trying to migrate the servers to Windows 16 server. We have the MySQL 8.0 OBDC running on a Windows 2016 Terminal Server connected to the Mysql database that is still on Windows 2008 File Server. With this configuration, I can click on the ODB database and all is good. However, when i click on the ODT files I get the following error from Open Office:
SQL Status: IM003
Error code: 160
Specified driver could not be loaded due to system error 182: (MySQL ODBC 8.0 ANSI Driver,
C:\Program Files (x86)\MySQL\Connector ODBC 8.0\myodbc8a.dll).
I seem to get the same error on both OO 3.4 and OO 4.1.5. I'm assuming that the ODT files somehow don't know about the MYSQL ODBC. Can you give me an idea what the problem can be and what I could do to fix this?
Thanks,
Steve F
I have a MYSQL 5.4 database running on a Windows 2008 File Server and accessed with a Windows 2008 Terminal Server. I use Open Office 3.4 to manage the data in a single ODB database. i also have a number of Forms (ODT files). The OBDC I used is the 5.4 Beta which has worked fine for years.
We are trying to migrate the servers to Windows 16 server. We have the MySQL 8.0 OBDC running on a Windows 2016 Terminal Server connected to the Mysql database that is still on Windows 2008 File Server. With this configuration, I can click on the ODB database and all is good. However, when i click on the ODT files I get the following error from Open Office:
SQL Status: IM003
Error code: 160
Specified driver could not be loaded due to system error 182: (MySQL ODBC 8.0 ANSI Driver,
C:\Program Files (x86)\MySQL\Connector ODBC 8.0\myodbc8a.dll).
I seem to get the same error on both OO 3.4 and OO 4.1.5. I'm assuming that the ODT files somehow don't know about the MYSQL ODBC. Can you give me an idea what the problem can be and what I could do to fix this?
Thanks,
Steve F