Description:
Bug report #5678 is exactly what I am experiencing; namely, I have downloaded and installed ODBC driver 3.51 without any evidence of a problem; yet, the driver is not available (not displayed in drivers list) in Control Panel>Administrative Tools>Data Sources>Drivers.
The old bug report is marked closed or addressed, but I do not see a solution.  A couple of people have suggested editing the Registry which I am reluctant to do.

How to repeat:
Download and install the ODBC driver under Windows XP Pro, SP2

I tried both downloads (the MSI and the Zip/exe).  I did not download any of the Windows Source/Samples listed much further down the page.

Are you using mysql-connector-3.51.12? Are you using Windows XP Pro 64bit? Perhaps an older, improperly uninstalled version of MyODBC was on the system?

Hi Peter,
I'm running Windows XP Professional Version 2002, Service Pack 2.
This is the ODBC file I downloaded and installed:  MyODBC-3.51.11-2-win.exe

I do not think I've ever had MySQL on this machine.  I just started getting into it the 1st week in October.  It was suggeted to me that I download the latest "stable" version of MySQL and driver.

Thanks,

Lou

Whoops - I misspoke about the latest ODBC driver.  The one cited in my prior email was attempted on Oct. 10.  On October 21 I tried this one:
mysql-connector-odbc-3.51.12-win32.zip

I think this is the one you suggested.

Could you please try to run myodbcinst.exe and install driver correctly ?

And more - I found the follow comments in sources:

On MS Windows (XP for example) the driver is registered in two places; 
              1) \windows\system32\odbcinst.ini
              2) registry
              Fortunately the installer calls will ensure they are both updated.

All ODBC drivers *should* be installed in the standard location (\windows\system32) and this call reflects this as no path is given for the driver file.

Could you check ?

Hooray!!  I'm finally able to get back in to this bug report.  The DeveloperZone/Bugs has been hanging and causing a GPF for about 10 days, now.

Anyway:
(1)  I cannot find the file you suggested I download and install (myodbcinst.exe) anywhere on this website.  Can you point me to it?
(2) the file odbcinst.ini does not exist in my \Windows\system32 folder (or anywhere else on my computer for that matter)  Explorer is set-up to show hidden files, too.

I appreciate any suggestions.

Lou St. Amant
Avon, CT

I'm experiencing the same problem on a 64-bit XP system.  I tried to copy the registry entry from a computer where the ODBC is working to my PC and that failed.  A quick search of  my local drive showed me that myodbc3.dll and a few other files that the registry is looking for in c:\windows\system32 are all installed in c:\windows\sysWOW64.  My guess is that the 64 bit system just assumes that directory is the correct place to put things.  I've tried rebuilding the registry entries to point to the correct drive, and I've tried moving the files to system32, but neither resolves the problem.  Don't know if this helps or not, but thought I'd post it since I don't see this info on any other bug report.

Thanks, John.  I'm not smart enough to mess with the registry, but it's good to know I'm not the only one having the problem.
BTW, I'm having a terrible time getting to Bugs.  It's been hanging/freezing every time I tried to get here, and causing a GPF.  This has been going on for weeks. I've had to notify MySQL via the main "contact" area even 'tho that area is not supposed to be used for bugs.  Bug if the bugs area doesn't work ....?
Also, I don't know if this is related but this a.m. there was another GPF waiting on the screen for me:  "mysqld-nt.exe has encountered a problem and needs to close"
Hopefully, someone will figure out why I can't get a working installation of MySQL.  For now, I'll stick to SQLServer and MS Access.

That's odd.  My installation of MySQL actually works fine for me.  I can run the MySQL admin, query explorer, etc without a hitch.  And the bug area is working fine for me too.  My only issue is that the MyODBC connector doesn't create an entry in the odbc manager for me to connect to.  No GPFs or anything.  I'm using Forefox 1.0.7, fyi.

I was unable to repeat on XP Pro SP2 and latest MyODBC. The issue
on 64 Bit OS there is already another bug reporting that issue. Below
the output using the ODBC tool odbcte32.exe:

Full Connect(Default)

	Env. Attr. SQL_ATTR_ODBC_VERSION set to SQL_OV_ODBC3

	Successfully connected to DSN 'testbug'.
SQLExecDirect:
				In:				hstmt = 0x003B1948, szSqlStr = "select version()", 
										cbSqlStr = -3
				Return:	SQL_SUCCESS=0

Get Data All:
"version()"
"5.0.17-nt-max-log"
1 row fetched from 1 column.

I had the same problem and solved as follow :
Open regedit
Locate HKLM\Software\ODBC\ODBC.INI\ODBC Data Sources
and remove the (default value) with the DEL key

I had this problem with the following configuration. None of the fixes recommended thus far or that I found elsewhere on the web worked, but I did get a datasource to work.

This was using the ODBC connector v5.1.6 for 32 Bit Windoze.

Installation on Windows XP Pro SP2 with local account worked as expected, using the MSI installer.

Installation on SP3 with a domain login account did not.

Installation went fine, the ODBC administrator failed to show the MySQL driver.
The Regedit "delete default" fix had no effect.
Checking the registry and the ODBCINST.INI file, both showed the connector as registered, nonetheless the ODBC administator failed to list the driver.
The Event Viewer showed no events containing mysql, past an INFO entry for the installer, indicating success.

Downgrading the MDAC file as described elsewhere had no effect.

Installing an older connector (3.5.x) had the same results.

HEre is what ended up working
1) Installed using the MySQL command line.
2) Using the command line tool, listing drivers failed to list the MySQL connector.
3) Ignoring the above, installed a DSN using the ODBC driver, using the command line tool.
4) In FileMaker, the defined DSN was available and worked.

So, it looks like the problem is related to the domain login and is actually not a problem in getting the driver installed, registered but rather in including the driver in the list of registered drivers. This does not extend as far as making the connector unavailable to the ODBC client (at least not FileMaker Pro as one).

---Raymond

Dear All,

I have just had this problem installing on Vista 64-bit using mysql-connector-odbc-noinstall-3.51.27-winx64.  HELP!  what do i do to get it to show up?

CD

Ceedee, well, what can I do if you used noinstall zip archive? Please use msi file. Further more, you probably installed 32bit version so x64 odbcad (which is by default the one in Control Panel on x64 OS) will never show it. See if C:\Windows\SysWOW64\odbcad32.exe sees the driver.

Thank you, thank you, thank you Tonci!

I tried that .exe and they show up there no problem.
Went back to control panel and they still don't show!
No idea what the problem was, and it's not really fixed but at least I can get to my database now.

cheers,
Ceedee

Ceedee, this only means you did not install x64 versions. Showing up in control panel is not at all that important because 99.999% of clients are 32bit (like MS Office).

You should use mysql c/odbc 3.51.27-winx64 if you want to see it in x64 control panel for what ever reason.

If you want to see/configure DSN's use C:\Windows\SysWOW64\odbcad32.exe and not the one from control panel.

I was having the same issue with Windows XP SP3. .MSI installer and 32-bit version. Install went as expected, all files and registry entries in the right place for the drivers, but they don't show up in ODBC Drivers and I can't add a DSN.  After reading, suspected that FileMaker Pro was a common theme for these reports.  Uninstalled FileMaker Pro, and voila without a reinstall the driver shows up; added DSN, reinstalled FM Pro.  All is right with the world.