MySQL Bugs: #64282: Installation location and proper usage is seriously impeded.

Bug #64282	Installation location and proper usage is seriously impeded.
Submitted:	9 Feb 2012 17:52	Modified:	20 Dec 2022 5:38
Reporter:	first last	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	Connector / ODBC	Severity:	S1 (Critical)
Version:	mysql-connector-odbc-5.1.10-win32.msi	OS:	Windows (Windows-7 (64-bit))
Assigned to:	Bogdan Degtyariov	CPU Architecture:	Any
Tags:	Access 2007, mysql-connector-odbc-5.1.10-win32.msi, Windows-7 64-bit

Description:
Short Version:
The installation of mysql-connector-odbc-5.1.10-win32.msi on our 64-bit install of Windows-7 is indeed residing within -- C:\Program Files (x86)\MySQL\Connector ODBC 3.51

END Short Version.

This same connector, when used on/in a 32-bit install of Windows-7 does not exhibit or otherwise behave as you will witness in the images provided with this report.

Please follow our image files accompanying this report:
FDSN-#.png= File DSN
SDSN-#.png= System DSN
UDSN-#.png= User DSN

How to repeat:
Follow the images provided to repeat.

Suggested fix:
I give up. :-)

Create File DSN

Attachment: FDSN-1.png (image/png, text), 174.68 KiB.

Create File DSN

Attachment: FDSN-2.png (image/png, text), 197.23 KiB.

Create File DSN

Attachment: FDSN-3.png (image/png, text), 180.95 KiB.

Create File DSN

Attachment: FDSN-4.png (image/png, text), 195.61 KiB.

Create File DSN

Attachment: FDSN-5.png (image/png, text), 198.18 KiB.

Create File DSN

Attachment: FDSN-6.png (image/png, text), 180.67 KiB.

Create File DSN

Attachment: FDSN-7.png (image/png, text), 176.12 KiB.

Create File DSN

Attachment: FDSN-8.png (image/png, text), 178.55 KiB.

Create System DSN

Attachment: SDSN-1.png (image/png, text), 175.33 KiB.

Create System DSN

Attachment: SDSN-2.png (image/png, text), 197.83 KiB.

Create System DSN

Attachment: SDSN-3.png (image/png, text), 182.27 KiB.

Create System DSN

Attachment: SDSN-4.png (image/png, text), 180.98 KiB.

Create User DSN

Attachment: UDSN-1.png (image/png, text), 178.51 KiB.

Create User DSN

Attachment: UDSN-2.png (image/png, text), 196.86 KiB.

Create User DSN

Attachment: UDSN-3.png (image/png, text), 181.60 KiB.

Create User DSN

Attachment: UDSN-4.png (image/png, text), 180.84 KiB.

Thank you for reporting the problem.
This issue has been resolved a few days ago.
Please try downloading the same package again.

The MD5 checksum for the new MSI has to be: 6f5aff2efa5c62f8b79cff4e5244233a

NOTE: the downloads page still shows the checksum for the old package
      73ef26c8c9e2a8576239b0cc5f091c6a. I notified the developers to get it
      fixed.

Hi,

The problem you have could be the legacy from the previous installation.
Can you try uninstalling the driver, removing all DSNs created before and then installing it again?

The system and user DSN details along with the driver information are stored in Windows registry, so when the new version of the driver is installed it can have problems because the registry holds information from the previous installation:

32-bit:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBCINST.INI\MySQL ODBC 5.1 Driver  <--- driver
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBC.INI\<DSN name>  <--- DSNs

64-bit:
HKEY_LOCAL_MACHINE\SOFTWARE\SYSTEM32\ODBC\ODBCINST.INI\MySQL ODBC 5.1 Driver  <--- driver
HKEY_LOCAL_MACHINE\SOFTWARE\SYSTEM32\ODBC\ODBC.INI  <--- DSNs

When you uninstall the driver it does not remove DSNs previously created.
This is done on purpose: removing a few DSNs is easier than creating them again.
For instance, when upgrading the driver you do not want all your DSNs to be gone.

Removed all DSN's and Drivers, but an unmark listing remains.

Attachment: Removed_all_drivr's_and_dsn's_Listing_remains.png (image/png, text), 229.37 KiB.

In spite of all our efforts we cannot repeat this problem.
Can you send us the windows registry fragment corresponding to odbcinst.ini?

Run regedit32, find [HKLM\Software\Wow6432Node\ODBC\ODBCINST.INI], right-mouse click on it and select "Export" in the pop-up menu.
Thanks.

Thanks for supplying the registry data.
I could not answer your question about the stale listing because I need to analyze the driver entries first.

Your registry key for MySQL ODBC 5.1 Driver looks fine, so the problem with displaying the version information etc might be related to corrupted or damaged DLL file. This information is accessed directly from the file, not from the registry.

Please check myodbc5.dll in Windows Explorer -> Right mouse click -> Properties.
Uploading the screenshot from my Win-7-x64 system.

myodbc5.dll properties dialog

Attachment: myodbc5_dll_properties.png (image/png, text), 15.18 KiB.

Two different dropdown lists on two different client hosts is a privilege-related thing. The user name in MySQL is not only what you type in the "User" input, but also the host name. So, 'my_user'@'host1' and 'my_user'@'host2' are completely different, so their access levels and privileges can be different too.

Now, about the initial problem. I could see in your registry that "MySQL ODBC 5.1 Driver" entry was not removed. This might be related to the ODBC feature called UsageCount. When you install a new driver over the old one the usage count increases, so the corresponding driver entry in ODBCINST.INI will not be removed until UsageCount reaches 0.

http://msdn.microsoft.com/en-us/library/windows/desktop/ms709304%28v=vs.85%29.aspx

Verified

I think this might be related.
This is my comment on page 

http://dev.mysql.com/doc/connector-odbc/en/connector-odbc-installation-binary-windows.html

GMGJ says for Windows 7 Home premium 64 bit and Office 2007.
If you have problem with 64 bit windows and odbc start here:

control panel -> administrative tools -->
data sources(ODBC) --> then right click on that file
--> go to properties
--> in the shortcut tab
-> set the path "c:\windows\SysWOW64\odbcad32.exe" in the Target area :) really it works!!!! :)

Normally you would find drivers on a 32 bit system in registry under
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\ODBC Drivers

On W7 HP 64 they are under
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC

I want to give credit to this post for passing on the above tidbit about changing the path:

http://answers.microsoft.com/en-us/windows/forum/windows_7-hardware/odbc-drivers-missing-i...

Gary,

Thanks for your message.
As I indicated in other bug reports (not less than 20 times already) any 64-bit Windows (XP, Win7, Win8) has two versions of ODBC Administrator:

 - 32-bit version is \Windows\SysWow64\odbcad32.exe
 - 64-bit version is \Windows\System32\odbcad32.exe

It is confusing that 32-bit version is in SysWow64 and 64-bit one is in System32.
You can easily create shortcuts to the both versions and run them corresponding to the driver you need at the moment (e.g. 32-bit or 64-bit).

I think the initial problem was slightly different and not related to various versions of ODBC Administrator.

Thanks for the reply.  I wish I had found one of the many references you made to this problem when I was searching.  But I did not.  I would classify this is a bug or at least an item needing documentation from Microsoft.  I would also call this a royal pain in the ass for anyone trying to use ODBC on Windows 7.  My intention is not to clutter up the mailing lists.  Its to make it easier for other folks to find.  One of my jobs was the developer/maintainer for the Connect * ODBC driver.  An interesting driver in that it had a TCP/IP and Novel Netware 3270 stack to connect to the IBM mainframe Model 204 database.  I ported if from 16 to 32 bit.  If I had problems installing a driver, there are problems with the installation.  I would be happy to help you put in a test in you install that looks for Windows 7 (or any other) affected system and puts a box up that says , on This system, there is a problem ....

Posted by developer:
 
This bug is no longer reproducible with Connector/ODBC version 8.0.
The location of the driver DLLs and the registry information are matching.
Closing the bug.