Bug #34826 | hanging odbc program | ||
---|---|---|---|
Submitted: | 26 Feb 2008 11:17 | Modified: | 3 Apr 2008 10:33 |
Reporter: | Homauoon mahboobi | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | Connector / ODBC | Severity: | S3 (Non-critical) |
Version: | OS: | Windows | |
Assigned to: | CPU Architecture: | Any |
[26 Feb 2008 11:17]
Homauoon mahboobi
[26 Feb 2008 11:23]
Tonci Grgin
Hi Homauoon and thanks for your report. As the error say, "Cannot find driver", you do not have MyODBC properly installed... There is a problem in your computers configuration which you'll have to find and fix. Did you check MD for setup you downloaded?
[27 Feb 2008 10:34]
Homauoon mahboobi
Hi Thanks for your response, My download is ok, because I run that installer file in 64 bit system and its works. I test this problem with three other Win XP SP2 systems and this problem was occurred.
[27 Feb 2008 11:11]
Tonci Grgin
Homauoon, we are all unable to repeat this problem... Tell me one thing, is the "Test" button on the left or on the right of your configuration screen? Do you have "Details >>" button at bottom left corner?
[27 Feb 2008 11:58]
Homauoon mahboobi
Hi The Test button is on the right of Database combo box, above Help and cancel button!
[27 Feb 2008 11:58]
Homauoon mahboobi
my computer's screen shots
Attachment: bugs.zip (application/unknown, text), 42.35 KiB.
[27 Feb 2008 12:27]
Tonci Grgin
Homauoon, images show you are truly using 5.1 config library... Now we need to check registry entries for 5.1 driver. Search your registry for "myodbc" string and see if there is anything suspicious there. For example, HKEY_CURRENT_USER\Software\ODBC\ODBC.INI, your_5.1_dsn_name should show where windows search for driver in "Driver" key. It should be "ProgramFilesDir"\Mysql... and not "winsysdir\myodbc5.dll". If it's "winsysdir\myodbc5.dll" then copy driver from "programfilesdir"\Mysql... to "winsysdir\myodbc5.dll" and test again.
[27 Feb 2008 13:23]
Homauoon mahboobi
This is my odbc5 driver location: C:\WINDOWS\system32\myodbc5.dll but, there isn't any myodbc5.dll in my program files\mysql folder!
[27 Feb 2008 13:48]
Tonci Grgin
Homauoon, you are not following me... There could be two scenarios: 1) You do *not* have driver on your system at all (false, it's in winsysdir) 2) ODBC registry entries point to wrong place for driver (ie. to program files and not to winsysdir) Now, you can either change registry entries to point to place where myodbc5.dll *is* or copy myodbc5.dll to a place where registry *expects* it to be... Please do apply one of workarounds and inform me of result.
[1 Mar 2008 6:15]
Homauoon mahboobi
Hi It seems that odbc5.dll is in the right place and its path on registry appears right.
[1 Mar 2008 6:16]
Homauoon mahboobi
windows registry for myodbc
Attachment: bug4.zip (application/unknown, text), 74.82 KiB.
[3 Mar 2008 8:29]
Tonci Grgin
Homauoon, I am not at liberty to inspect your computers configuration etc, for that you need support contract... I would suggest you to uninstall and then manually remove all traces of c/ODBC from your machine. Then install latest snapshot from http://downloads.mysql.com/snapshots/mysql-connector-odbc-5.1/ or latest released version from downloads. There might be a relation to Bug#34522 which should have been fixed in source trees.
[3 Apr 2008 9:57]
Adam Smith
It doesn't work for me either. Repro is valid. I've scrubbed every reference to mysql from my registry, and reinstalled mysql-connector-odbc-5.1.3-win32.msi. All dll refs are to C:\Program Files\MySQL\Connector ODBC 5.1\myodbc5.dll but I get the driver not found/config translator failed. 3.5.1 ODBC drivers were previously installed, on XP box that can't use 5.1.3 drivers. On clean XP box, 5.1.3 drivers install and work. This is a critical bug S2 bug because when it happens--NOTHING WORKS. Thanks, Adam totallyfracked@spamex.com
[3 Apr 2008 9:58]
Adam Smith
Oh, and my drivers are all where they're supposed to be in C:\Program Files\MySQL\Connector ODBC 5.1\
[3 Apr 2008 10:33]
Tonci Grgin
Homauoon, Adam. Seems Bogdan was able to find the problem. I'm setting this report to duplicate of Bug#35776 now.