Use the search feature to view Kepware's repository of more than 500 Knowledge Base articles. Narrow your results or type your query into the search field below.

Alternatively, if you are unable to find a solution, we have an additional resource - our PTC eSupport Portal . If you are prompted to log into the eSupport Portal, you can use your My Kepware credentials. Need a My Kepware account? Create one here .

Search Solution Results By:
View All Solutions

Kepware Knowledge Base: Solution

Using DataLogger, Advanced Simulator, and the ODBC Client Driver with MySQL 3.51 in a 64-Bit Environment

Last Update: 11/7/2018


Users cannot connect on or from 64-bit operating systems.

DataLogger, Advanced Simulator driver, and ODBC Client driver all use ODBC to interface with data sources that are ODBC-compliant. Connectors are used to access those data sources via a Data Source Name (DSN) created in the Microsoft Data Access Components (MDAC) interface. Those connectors are included for Microsoft data sources. For MySQL 3.51, a connector from the development organization is required and may be downloaded at Download Connector/ODBC. Users should make sure to download the x86 64-bit connector.

Connections are made via DSNs in the MDAC, which can be opened for one of the KEPServerEX ODBC-capable plug-ins or drivers (or for the operating system). Typing "ODBCAD32.exe" into the Run command line will launch the 64-bit MDAC, whereas the server will open the 32-bit MDAC. The 32-bit version is located in SysWOW64; however, because Microsoft wanted to give the same name to both the 32 and 64-bit versions (and the operating system always checks the System folder first for applications), users must provide the full path to the 32-bit version in order to launch it from the desktop. The full path should be C:Windows\syswow64\odbcad32.exe.

Because the server is a 32-bit application, it looks for 32-bit DSNs to use when connecting to ODBC data sources. For more information on the creation and use of 32 and 64-bit DSNs, refer to Unable to View a DSN Created by the ODBC Administrator.