MySQL Bugs: #66499: ODBC Connector 64 Bit

Bug #66499	ODBC Connector 64 Bit
Submitted:	22 Aug 2012 15:07	Modified:	1 Jul 2013 6:39
Reporter:	Thomas Lee	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Connector / ODBC	Severity:	S1 (Critical)
Version:	5.1.11	OS:	Windows (Win 7 Home Premium 64 Bit)
Assigned to:	Bogdan Degtyariov	CPU Architecture:	Any
Tags:	No driver found, No error when install

Description:
Installed ODBC 5.1.11 connector 64 Bit, no error occurred , but find no ODBC driver in the list when added DSN

How to repeat:
Just install as instruction

This is not a bug. 
Windows 64-bit has two ODBC Administrator applications: 

 - 32 bit odbcad32.exe in \Windows\SysWow64\odbcad32.exe 
   for 32 bit ODBC drivers

 - 64 bit odbcad32.exe in \Windows\System32\odbcad32.exe 
   for 64 bit ODBC drivers

Make sure you are running the correct version of the administrator

after I extract the download file, there is "install" file which I executed it
The screen flash with no error. I have checked both admins which hace no mysql driver found

Such issues might occur if the registry key for ODBC drivers list contains the wrong entry, which prevents the driver manager from reading this list correctly.

Please run regedit32 and export the following key into a text file (click the
right mouse button and select "Export" from the pop-up menu):

[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI]

You can choose the privacy option in the file upload form, so only 
MySQL Developers could access your file.

Installed at win 2003 server 64 Bit successful, this is what I want not Win 7

Thanks for sending the ODBCINST.INI registry branch.
Unfortunately, you exported it in txt format, which might not show logical errors in the registry structure for ODBC drivers. Exporting as .reg file is much more informative and easy to read.

Nevertheless, I was able to spot a few issues there.

1. In a 64-bit windows environment this key would correspond to a 64-bit
   ODBC Driver, but it is labeled as 32-bit:

Key Name: HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\Client Access ODBC Driver (32-bit)

The facts are 
   - the registry contains a 32-bit driver.
   - MySQL 64-bit driver does not install in that environment.

To me it looks very much like 32-bit Windows.
Are you sure your Win7 Home Premium is a 64-bit OS?

2. This is the minor issue, but two keys point to the same DLL library:

Key Name: HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\Client Access ODBC Driver (32-bit)
....
Data: C:\Windows\system32\cwbodbc.dll

Key Name: HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\iSeries Access ODBC Driver
Data: C:\Windows\system32\cwbodbc.dll

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

Hi, I'm having the same issue reported here. I have Windows Vista 64. I install a 64 bit ODBC. ODBCINST.INI says 

[MySQL ODBC 5.2w Driver (32 bit)]
Driver=C:\Program Files\MySQL\Connector ODBC 5.2\Unicode\myodbc5w.dll
Setup=C:\Program Files\MySQL\Connector ODBC 5.2\Unicode\myodbc5S.dll
32Bit=1

I reinstalled mysql-connector-odbc-5.2.4-winx64.msi, but when I open 
C:\Windows\SysWOW64\odbcad32.exe I see no MySql driver (I guess because of the issue on the ODBCINST.INI)

Please, help,

An M

I see the inconsistency in the last message from An R.

The driver section clearly suggests 32-bit ODBC driver: 
[MySQL ODBC 5.2w Driver (32 bit)]

However, the location of the .dll files points to the "Program Files" directory, which in 64-bit systems contains 64-bit applications and libraries:

Driver=C:\Program Files\MySQL\Connector ODBC 5.2\Unicode\myodbc5w.dll
Setup=C:\Program Files\MySQL\Connector ODBC 5.2\Unicode\myodbc5S.dll

The 32-bit directory is "Program Files (x86)".

Next, the package name says it is 64-bit one:

mysql-connector-odbc-5.2.4-winx64.msi

However, the ODBC Administrator is 32-bit from C:\Windows\SysWOW64\odbcad32.exe

It is confusing in Windows, but 32-bit directory's name is SysWow64 and 64-bit one is System32! So, please keep that in mind.

Just run the 64-bit ODBC Administrator from here and it will show the driver:
C:\Windows\System32\odbcad32.exe

And the last, but not least: you should never look into ODBC.INI or ODBCINST.INI files. The ODBC driver manager uses the windows registry for storing information about installed drivers, data sources, connection parameters etc:

For 32-bits:
HKEY_LOCAL_MACHINE\SOFTWARE\WOW64NODE\ODBC\

For 64-bits:
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\

System data sources are located in HKEY_LOCAL_MACHINE.
User data sources are in HKEY_LOCAL_USER.

Hi, Thanks for the answer.

I'm receiving this error: 'ERROR [HY010] [MySQL][ODBC 5.2(w) Driver][mysqld-5.5.27-log]'

Do you have any idea what does it mean?

I get the error while using the ODBC to connect MS Excel's PowerPivot to MySql hosted on a remote server. I get this error when issuing an SQL command to select records from a table.

If I let Excel to do the query, in the log file myodbc.log, I see Excel is doing, which is not valid syntax: 

SELECT   [users].* FROM [users];

I don't know if it's ODBC issue or Excel's... can you help me with this?

Thanks,

An M

The problem you are experiencing now is completely different from the initial issue with the missing ODBC driver. In order to keep our bug records clean and accurate I would like to ask you to report a new MySQL Connector/ODBC (MyODBC) bug.
Also, in the "how to repeat" section provide a step-by-step instructions in Excel how to repeat the error along with the version of MS Excel.

HY010 is sqlstate indicating the function sequence error.
This is somehow related to the query with invalid syntax:

SELECT   [users].* FROM [users];

When the new bug is reported I will gladly assist you in resolving it.

Meanwhile I am setting "No Feedback" status as the original bug reporter never came back with the details requested.

Please note that this bug report is waiting on your reply. It will be automatically closed if you do not provide us any feedback.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

No feedback was provided. The bug is being suspended because we assume that you are no longer experiencing the problem. If this is not the case and you are able to provide the information that was requested earlier, please do so and change the status of the bug back to "Open". Thank you.