MySQL Bugs: #32803: installing odbc connections for mysql

Bug #32803	installing odbc connections for mysql
Submitted:	28 Nov 2007 9:57	Modified:	6 Dec 2007 3:03
Reporter:	Michel Molnar	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	Connector / ODBC	Severity:	S2 (Serious)
Version:	odbc-3.51.22-win32.msi	OS:	Windows
Assigned to:		CPU Architecture:	Any
Tags:	my odbc connection with mysql failed

Description:
Dear all,

I want to connect my database filemaker to mysql, for his, it is ask to create a odbc connection with "odbc data source management" in the "system DSN". 

Every test I made for the configuration failed and give this message;

Connection failed:
SQLState:'01000'
SQL Server Error: 10061
[Microsoft][ODBC SQL Sever Driver][TCP/IP Sockets]ConnectionOpen (Connect())
Connection failed:
SQL State:'8001'
SQL Server Error:17
[Microsoft][ODBC SQL Sever Driver][TCP/IP Sockets]SQL Server does not exist or access denied

but I can connect to mysql server with the software:HeidiSQL. the connection between those works perfectly

I use the mysql-connector-odbc-3.51.22-win32.msi 

I don,t know what to do 
Thanks for the help

How to repeat:
in Start menu>open control panel>administrator tools>odbc data Source administrator

Click on system DSN and I choose the "localhost,sql server driver" and then configuration.

Hi Michel and thanks for your report. From what little info is provided I would say you're using wrong driver (MSSQL):
[Microsoft][ODBC SQL Sever Driver]

Can you confirm that correct MySQL driver has been used for DSN in question? What does "Test" button show?

Hi Toni and thank you for your answer. I'm using the the driver which i have download from mysql site. The version is 'mysql-connector-odbc-3.51.22-win32.msi'

The test button says:

Microsoft SQL Server ODBC Driver Version 03.85.1117

Running connectivity tests...

Attempting connection
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not exist or access denied.

TESTS FAILED!

Or the instalation of mysql was not properly done or my odbc driver is not good.I realy don't know what to do.

Thank you in advance

Michel, the thing is that your DSN is pointing to MyODBC setup and to MSSQL driver seemingly. In order to test this, can you please attach "HKEY_LOCAL_MACHINE\SOFTWARE\ODBC" branch from your registry. Note that under "HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\YOUR_DSN_NAMES" there are "PWD" entries! Feel free to delete those before attaching.

hi, I atteach the reg file 'HKEY_LOCAL_MACHINE\SOFTWARE\ODBC', I had to export it first to be abble to make a attach file. please, let me know if that is possible to use it as it is. Thank you in advance

HKEY_LOCAL_MACHINE\SOFTWARE\ODBC

Attachment: ODBC.reg (application/octet-stream, text), 39.07 KiB.

Michel, someone (you) created new DSN's with wrong *description*, as if you wanted to write MSSQL but you wrote mysql instead:

[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\mysql server]
"Driver"="C:\\WINDOWS\\System32\\SQLSRV32.dll"
"Description"="ceci est ma base de donnees"
"Server"="localhost"
"LastUser"="Administrator"
"Trusted_Connection"="Yes"

[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\ODBC Data Sources]
"CCSInternet"="Microsoft Access Driver (*.mdb)"
"CCSIntranet"="Microsoft Access Driver (*.mdb)"
"mysql server"="SQL Server"

As you can see "mysql server" actually has nothing to do with MySQL nor with MyODBC (which is properly installed):
[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\MySQL ODBC 3.51 Driver]
"UsageCount"=dword:00000001
"Driver"="C:\\WINDOWS\\system32\\myodbc3.dll"
"Setup"="C:\\WINDOWS\\system32\\myodbc3S.dll"

So, please rename "mysql server" DSN to "MSSQL server" and add new DSN for MySQL choosing "MySQL ODBC 3.51 Driver" as a driver.

Thank you  Tonci Grgin for your help, I could easily rename;"MSSQL server" but when I wanted to add a new DSN, the "data source management window" didn't show me the driver:"MySQL ODBC 3.51 Driver" in the list of drivers. So the drivers seems properly installed but doesn't show up in the data source magement window.

Michel, the situation described is only possible when installing 32bit driver on 64bit OS. I can't find a fault in your registry file so I must check the rst of the things:
 1) Make sure there indeed exists myodbc3*.dll files in your WinSysDir
 2) Merge this DSN into your registry (after making necessary modifications) and test:
[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\TestDSN3]
"Driver"="C:\\WINDOWS\\system32\\myodbc3.dll"
"DATABASE"="DBName"
"DESCRIPTION"="bug 32803"
"OPTION"="12075034"
"PWD"="YOURPassword"
"SERVER"="localhost"
"UID"="root"
"CHARSET"="latin1"

If 1) is not present, please reinstall.
If 2) does not work, driver files are either damaged and/or blocked by other SW on your machine.

Please inform me of your result.

Hi Tonci, I have check point 1)the dll myodbc3*.dll is in my WinSysDir. so the problem does not come from there. 

I have also merge a TestDSN3 in my registery, but this DSN doesn't show up in the data source management window when i want to 'add' a new System DSN. Only the driver; SQLSRV32.dll is available.
The driver i have install should be good because we already made the test on a other computer with the same driver.and it was working. So, it can not be the driver who is damaged.

So the last solution should be the last point maybe. What kind of software can blocked a driver. Could it be a antivirus system or is it something different.

Thanks in advance

Michel, I would like to help but I really can't guess now... This all looks like installing 32bit driver on 64 bit OS.

You *may* try to copy %SystemRoot%\system32\odbcad32.exe from working machine to non-working one. Also, compare MDAC versions on both computers (there is MS tool for that).

new version

Attachment: mod_odbc_reg_bk.reg (application/octet-stream, text), 4.15 KiB.

old version

Attachment: odbc_reg_bk.reg (application/octet-stream, text), 4.17 KiB.

Again many hanks for your contribution and for your patience.

Best regards

Hi Tonci,
It seems I forgot to submit one of my last comments. If have found a solution to my problem. In the different mails you ave received, I have join some register file from the [HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\ODBC Drivers]the old version and a new version. Somehow, this key was corrupted and had to be corrected.
Once done, the 'datasource manager' could show the Mysql OBDC driver 3.51 and I could connect Mysql database.

Thanks a lot 
Michel

Michel, thanks for your interest in MySQL.