| Bug #62722 | Get -2147467259 [Microsoft][ODBC Driver Manager] Data source name not found ... | ||
|---|---|---|---|
| Submitted: | 13 Oct 2011 17:12 | Modified: | 13 Oct 2011 19:36 |
| Reporter: | Jack Charrette | Email Updates: | |
| Status: | Not a Bug | Impact on me: | |
| Category: | Connector / ODBC | Severity: | S3 (Non-critical) |
| Version: | 5.1.9 64bit MSI | OS: | Windows (Windows 7/64 bit) |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | 5.1.9, Data source name, MyODBC, regression, windows | ||
[13 Oct 2011 17:54]
Lawrenty Novitsky
Jack, thank you for your report. Are you sure that your application is 64bit? Starting from 5.1.9 64 bit installer does not install 32bit driver along with 64bit one. That is the only thing that comes on my mind given your error description. Unless you sure that application is 64bit, could you please download and install 32bit c/odbc and see if that fixes your problem.
[13 Oct 2011 18:30]
Jack Charrette
No, I am sure that our app is NOT 64 bit (it is 32) but is running on Win 7/64. We cannot be 64 bit due to other dependencies. Are you saying that the version of myODBC is dependent on an app not the OS?
[13 Oct 2011 18:43]
Peter Laursen
This is my experience (with our own - SQLyog - application) as regards 32 bit apps, 64 bit OS and ODBC drivers: http://webyog.com/faq/content/17/187/en/problems-creating-a-functional-dsn-on-64-bit-windo... .. so I think you should try to install the 32 bit driver (though I am not sure if a 'DSN-less connection' will pick the 32 bit driver even if it is installed. If not you will have to create a DSN). Peter (not a MySQL person .. and I hope it is OK to publish such link here)
[13 Oct 2011 18:59]
Lawrenty Novitsky
Yes, it is. 32bit applications cannot use functions from 64bit library. And that is basically what happens in odbc application - it calls functions from a library, that we usually call odbc driver. i am closing the bug.
[13 Oct 2011 19:13]
Jack Charrette
The 5.1.6 64 bit version works but the 5.1.9 version does not. My client says that the 5.1.8 64 bit works. 5.1.9 32 bit works. So it is not the app unless this driver now requires it. I am not sure about that link to experiences. Out app is DSNLess. I am just finding this a whole lot more confusing and our non-IT customers are not going to know either just causing us to get more support calls. The 5.1.9 64 bit should work of 64 bit OSes especially since there can be a MIX of 32 and 64 bit programs.
[13 Oct 2011 19:29]
Peter Laursen
@Jack You write "The 5.1.6 64 bit version works but the 5.1.9 version does not." Lawrin wrote: "Starting from 5.1.9 64 bit installer does not install 32bit driver along with 64bit one." .. so isn't this expected, consistent and explained? And I think you should blame the confusion on Microsoft primarily - though maybe it was not a wise decision by MySQL/Oracle to remove the 32 bit driver from the 64 bit installer.
[13 Oct 2011 19:36]
Jack Charrette
So know I know that the myOdbc 64 installer was actually 2 installers. Yes, microsoft make a mess with their handling of 64 bit (especially with the Wow64 folders, etc.) but now what use to work with myODBC does not and now it appears that MySQL is joining them in the confusion.
[13 Oct 2011 19:45]
Peter Laursen
@Jack .. I think you can do one thing here. I think *you* can reopen this report (*I* cannot as I am not the original reporter here), and make it a *feature request* that the 32 bit version should be put back into the 64 bit installer (both the 'standalone' and the 'unified' installer). I agree that most users have no clue about the mixed-bit conflicts arising with 64 bit systems and 32 bit applications/drivers - and if both 32 an 64 bit drivers were installed on 64 bit systems it would solve the issue for many. In our support we have explained quite a lot of times to our users. That was why I wrote the FAQ I linked to actually.
Description: myODBC windows Driver 5.1.9 64 Bit (msi) does not work (5.1.8 does) Our program (Shopping Cart Integrator for QuickBooks) connects to mySQL database using the myODBC driver. Using a DSNless connection from a windows 7/64 bit machine. Database is remote on a web server. 2 clients have just installed the 64 bit windows driver (msi) and it does NOT work. 5.1.8 and earlier versions do work. Connection String DRIVER={MySQL ODBC 5.1 Driver};DESC=;DB=dbdbdb;SERVER=nn.nn.nn.nn;UID=uuuu;PASSWORD=xxxx VB code ODBCCon.Open ConnString Get error -2147467259 [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified Tried connection string MySQL ODBC 5.1.9 also. Perhaps the connection string changed???? How to repeat: Just do the above. Install the drive and run a program using the above connection string. Fails immedicately at the .open Suggested fix: Do not use 5.1.9 use an earler version if you can find one.