MySQL Bugs: #25259: MyODBC Will not work with Vista x64 AMD

Bug #25259	MyODBC Will not work with Vista x64 AMD - Final Release
Submitted:	23 Dec 2006 18:27	Modified:	28 Apr 2007 22:02
Reporter:	Bill Daugherty II	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	Connector / ODBC	Severity:	S1 (Critical)
Version:	3.51	OS:	Windows (Windows Vista x64 AMD)
Assigned to:		CPU Architecture:	Any
Tags:	MyODBC, ODBC, Vista x64

Description:
I do not show any drivers in the ODBC DSN area in Vista.  I have installed MyODBC, but still does not come up.

Connection open error: ERROR [IM002][Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

I have even tried this: http://forums.mysql.com/read.php?37,92637,123542#msg-123542  but still does not work.

How to repeat:
Just install MyODBC, Reboot, Still Nothing in MyODBC

Has your binary file been built as 32 bit or 64 bit executable?

Workaround for MyODBC x32 on Vista x64:
Run: C:\Windows\SysWOW64\odbcad32.exe
This will show the drivers normally and open possibility to create ODBC sources as normal.

Please do not submit the same bug more than once. An existing bug report already describes this very problem. Even if you feel that your issue is somewhat different, the resolution is likely
to be the same. Because of this, we hope you add your comments to the original bug instead.

Thank you for your interest in MySQL.

Explanation: This is not a bug.
MyODBC 3.51 is 32bit application which, by default, goes into
%SystemRoot%\sysWOW64 folder on 64bit windows. The DataSources(ODBC) link in
control panel searches for 64bit drivers in %SystemRoot%\system32 folder (silly
naming I know...). 
What you have to do is:
  Locate odbcad32.exe in *%SystemRoot%\sysWOW64 folder* (DO NOT use the one in
%SystemRoot%\system32 folder pointed to in control panel!)
  Use this program instead of default 64bit version to access MyODBC
  Start it and add MyODBC driver from the list of available drivers

This note is in our documentation.

Duplicate of Bug#20301.

See, im not sure if it is a duplicate..  I did try loading the ODBC Mgr, i do see it is in the list of drivers.  However i still get a failure in connecting to it from my .NET application by using the same connection string that I did in 32bit os.

Opening Bug Report again.

OK Bill. I'll probably have that environment this week so I'll do some more tests.

Thank you!

Hello, any luck yet?

Bill, thanks for your patience. I have set up Vista x64 on my AMD box and this report will be tested till the end of the week.

No problem, thanks for your assistance.  if you need further help, let me know!

Bill, finally I got things working...

 - Vista x64 Ultimate (released version) on AMD x64
 - MyODBC 3.51.14GA msi and connector/ODBC 5.0.11-beta msi from our site
 - Using odbcad32.exe from SysWOW folder

Both connectors are shown as you can see in attached image, so I have no problems...

Screen capture

Attachment: bug25259.jpg (image/jpeg, text), 47.02 KiB.

It looks like you used the 32 bit drivers.  I can get them to work, but the x64 driver which isn't available in a msi doesn't seem to work.  It installs OK, but then seems to be not available to Access when one looks for it in the ODBC dialog you get from exporting a table to an ODBC database.  I went back to the 32 bit drivers.

WB, you have not followed on entire report. Access is 32bit application regardless of OS or Office version and it can *not* use x64 ODBC driver...

Hi I have problem when i install ODBC driver 3.51 in Windows Vista 

[IM002] [Microsoft][ODBC Driver Manager] Data Source name not found and no default driver specified.

Vipu, if it's x64 OS then this is expected as Microsoft removed default OleDB provider from it's x64 OS's (MSDASQL.x). They *might* get it back in W2k8.

Thankyou For your prompt replay

But what i do regarding this on my problem should i remove Vista from my computer or is there any way to solve this problem in Vista

Thankyou again

Vipul, I will need more info from you....

 1) Are you using 64bit Windows?
 2) Are you running some VBS in scripting host? Or better, what is it you're trying to do?
 3) What do you need MyODBC for? Is it standalone program or 3rd party client (like Access)?

Here We are giving all your questions answers:

1) Are you using 64bit Windows?
Ans: Yes we are using Windows Vista x64 Business.

2) Are you running some VBS in scripting host? Or better, what is it
you're trying to do?
Ans: We are using Visual Basic .Net 2008 Application as front end with connection of MySQL Server 4.1 using MySQL ODBC Driver 3.51. 
Note: We have also made application in VB6 with MYSQL and that is running fine on the same windows.

3) What do you need MyODBC for? Is it standalone program or 3rd party
client (like Access)?
Ans: We are trying to make connection beween MySQL to Visual Studio .net 2008 application. It is client server based application. We can run this application in windows xp sp2, but problems finding in Windows Vista x64 Business. For the connection We are using MySQL ODBC Driver 3.51

Respected Sir,

I havem't get any solution or any advice from your side about my problem.

Please give me any replay about my problem so atlist i can find any solution because it stopes my works.

lease do the needfull.

Vipul, as I already said, Microsoft removed default OleDB provider from it's x64 OS's (MSDASQL.x). They *might* get it back in W2k8. *That* is what is causing your problem! There are many mechanisms to use ODBC driver without OleDB, you should consult your VS documentation and Microsoft announcements. One would be to load MyODBC directly from your application code.

So, you do *not* need to remove Vista but you'll have troubles until Microsoft fully supports everything they used to on x64 platform...