MySQL Bugs: #55495: Connector-ODBC 5.1.6 32-bit version won't install on Win Server 2008 R2 Enterpri

Bug #55495	Connector-ODBC 5.1.6 32-bit version won't install on Win Server 2008 R2 Enterpri
Submitted:	23 Jul 2010 2:19	Modified:	23 Jul 2010 16:14
Reporter:	Barry Lake	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	Connector / ODBC	Severity:	S3 (Non-critical)
Version:	5.1.6	OS:	Windows (Windows Server 2008 R2 Enterprise)
Assigned to:		CPU Architecture:	Any
Tags:	32-bit, ODBC, Windows Server 2008 R2 Enterprise

Description:
On a Windows Server 2008 R2 Enterprise system I attempted to install the 32-bit version of the MySQL Connector-OCBC 5.1.6 package using both the MSI Installer and the ZIP archive. In both cases the installation appeared to complete without any problem, but in NEITHER case does the MySQL driver appear in the list of available drivers within the ODBC Data Source Administrator utility when I try to create a new DSN.

I'm installing the 32-bit version because my goal is to connect to mysql data sources using Filemaker, whose documentation clearly states that 64-bit versions of ODBC drivers are not supported.

When I install the 64-bit version of the Connector on the same system I do see the MySQL driver listed in the ODBC Data Source Administrator. I am also able create a DSN and run a successful connection test to the external MySQL database. But, that DSN is inaccessible from with FileMaker, as expected (and as documented). Yes, FileMaker should fix their software so that it works with the 64-bit driver, which would resolve the problem.

But you should fix your 32-bit connector so that it can be installed in Windows Server 2008 R2 Enterprise.

At the moment I'm dead in the water... I can't access the external MySQL database from within Filemaker on this system due to this problem.

How to repeat:
Install the 32-bit version of the Connector on a Windows Server 2008 Enterprise R2 system. Then look for the MySQL driver in the ODBC Data Source Administrator utility. I bet you won't find it.

Suggested fix:
Figure out why the 32-bit installer appears to execute without error, but the driver doesn't show up in the ODBC Administrator utility.

x64 and 32bit DSN's in their respective DM's on 2K8R2 server

Attachment: Bug55495.png (image/png, text), 69.81 KiB.

Hi Barry and thanks for your report.

As it appears to me, you are mixing things... The default ODBC datasources administrator on Winx64 is the *64bit* one. So, going to Control Panel/Administrative tools/Datasources ODBC will invoke 64bit version of odbcad (%windir%\system32\odbcad32.exe) while DM for 32bit drivers is %windir%\SysWOW64\odbcad32.exe. This is a common mistake in 64bit environment and well described in BugsDB as well as in our manuals. Invoking proper DM will create proper DSN; 32bit ones will be saved in HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBC.INI.

Further more, c/ODBC 5.1 installs *both* 32bit and 64bit versions when in x64 environment, there are no options to install this or that architecture! So, if you're running x64 OS do install x64 c/ODBC.

Finally, there are known problems with Filemaker you can check on in BugsDB.

Closing the bug as, apart from doing stuff in FileMaker, I can not repeat it on my 2K8R2 x64 Enterprise.

Thanks very much for your clarification. I was able to get it to work using the "hidden" version of the ODBC Administrator, as you described. I sincerely apologize for wasting your time.

Thank you very much for your clarification.... :)