MySQL Bugs: #65009: ODBC Driver Upgrade is not adding new driver to ODBC Data Source Administrator

Bug #65009	ODBC Driver Upgrade is not adding new driver to ODBC Data Source Administrator
Submitted:	17 Apr 2012 15:35	Modified:	29 May 2013 11:45
Reporter:	Norm Bailey	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Connector / ODBC	Severity:	S2 (Serious)
Version:	3.51.30	OS:	Windows (2003)
Assigned to:	Bogdan Degtyariov	CPU Architecture:	Any

Description:
I have run  a the download for a new version of MySQL ODBC driver 3.51.30  to my windows 2003 server running MySql ... the install appears to have worked fine, but the problem is that the driver does not appear available to me in the ODBC Data Source Administrator utility.  The old driver 3.51.27 is still the active driver.   

How to repeat:
Download using link http://dev.mysql.com/downloads/connector/odbc/3.51.html#downloads

Screen shot of odbc data source

Attachment: screen shot 1.docx (application/octet-stream, text), 34.23 KiB.

used the 32 bit Installer program for odbd driver 3.51.30. 
tried both typical install and custom install.  
Tried removing driver and then installing driver.

If the OS is 64 bit this may help:
http://www.webyog.com/faq/content/17/187/en/problems-creating-a-functional-dsn-on-64-bit-w...

Peter
(not a MySQL person)

Operating system is 32 bit....

Norm,

Sometimes 3rd party applications might insert corrupted entries into windows
registry and in such way prevent Windows ODBC Driver Manager from scanning the
complete list of drivers. For instance, it was the case with FileMaker, which created keys named "\@" in Windows registry node [HKLM\SOFTWARE\ODBC\ODBCINST.INI\ODBC Drivers].

Can you export the entire [HKLM\SOFTWARE\ODBC\ODBCINST.INI] node using
regedit.exe?
We need to have a look at this node in order to check if MySQL ODBC driver
3.51.30 has been registered correctly. When uploading the file you can select
the privacy option, so only MySQL Developers could see it.
Thanks.

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".

I'm closing this bug because I can not continue without feedback from the reporter. If you have new info, please reopen the report.