MySQL Bugs: #38443: MyODBC Adding a System DSN, Configuration 32bit, on a 64bit OS

Bug #38443	MyODBC Adding a System DSN, Configuration 32bit, on a 64bit OS
Submitted:	29 Jul 2008 22:23	Modified:	6 Aug 2008 9:01
Reporter:	Andrej Pintar	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Connector / ODBC	Severity:	S1 (Critical)
Version:	3.51.04	OS:	Windows (Server 2008 x64)
Assigned to:		CPU Architecture:	Any
Tags:	accessed, library, odbc 3.51.04, setup, windows 2008 x66, x64

Description:
Using a fresh installation of Windows 2008 x64 we installed myODBC 3.51.04 whitch we use on Windows Server 2003 32bit. Software that we use is 32bit. Our application. That's why we need this. Otherwise I would not write this.

Why this old version? Because the software that it uses works just fine and after trying other versions Higher normally and even latest we encountered that it does not work as expected. Problems with some MySQL commands and the results that were returned. That's another long story... Need to ask my programmer.

OK. After installing Windows and all is well working. I installed this version since its important. Now I entered %SYSTEMROOT%\SysWOW64\odbcad32.exe to access 32bit ODBC Subsystem. And also there is a Difference when using c:\windows\system32\odbcad32.exe.
Case 1 : %SYSTEMROOT%\SysWOW64\odbcad32.exe
Case 2 : c:\windows\system32\odbcad32.exe

Case 1:
After trying to add System DSN i get:
Msgbox 1:
The setup routines for MySQL Myodbc 3.51 driver could not be accessed. Please
reinstall the driver.
Msgbox 2:
The setup routines for %s ODBC driver could not be accessed. Please reinstall the driver.

Case 2:

After playing a while. In this odbcad32.exe you won't see MyODBC listed as in CASE 1. I managed to play around with WIndows registry. Copying keys and so on.
We got 2 differences:

Under SOFTWARE in LOCAL_MACHINE and CURRENT_USER:
SOFTWARE->ODBC (Should be case 2,c:\windows\system32\odbcad32.exe)
SOFTWARE-WOW6432Node->ODBC (Should be case 1,%SYSTEMROOT%\SysWOW64\odbcad32.exe)

I copied some missing pieces to make MyODBC visible in the list.
But I get an error message that says:
msgbox 1:
The setup routines for myodbc 3.51 driver could not be loaded due to a system error code 193.
msgbox 2:
could not load the setup or translator library

I copied files to System32 Folder: dlls and libs (3 files I think). Still haven't checked if that are all in the Install of 3.51.04.

If you have any good sugesstions please say so. Now we are currently using the APP on One server (2003 32bit), MySQL x64 Server on Win 2008 x64. Works ok. But we prefer to have this APP installed locally.

How to repeat:
Install MyODBC 3.51.04 on a fresh installation of Windows 2008 x64.

However this error occurs on Windows 2003 x64 R2.

Suggested fix:
Frontend:
Install APP on a 32bit Server Running Windows XP or Windows 2000,2003 32 bit.

Backend:
Install MySQL x64 on a machine that has Windows x64 2003,2008.

Depends on APPLICATION, NETWORK (response,speed) so on.

Hi Andrej and thanks for your report.

What do you expect me to do now? Problem you report *is* fixed so please upgrade. I think 3.51.26 would solve most of your upgrade-related problems with "Always handle binary function results as character data" option set.

Andrej, if needs be, just post to this report and I'll respond. Never mind the status.

Tryed to do some tests... New myODBC doesn't work... Back to the beginning.... App has to be reprogrammed all over to work with the new version.... PS. I think it has to do something with SHOW COLUMNS from xxx_table. So my programmer said that it's not executing this command or it's returning some garbage data... Not sure 100% but something is missing..... I'll have a talk on Monday about this with him....

Andrej;
"Tryed to do some tests... New myODBC doesn't work... Back to the beginning.... App has to be reprogrammed all over to work with the new version.... PS. I think it has to do something with SHOW COLUMNS from xxx_table. So my programmer said that it's not executing this command or it's returning some garbage data... Not sure 100% but something is missing..... I'll have a talk on Monday about this with him...."

This is a no-problem! Please see discussion in Bug#10491. Your actual data from ad-hoc queries like "SHOW ..." is detected as BINARY data thus it's preceded with 0xYour_actual_result. This is a known problem in server causing troubles in all of connectors. Now, as it is known, it has been worked around. There is a new option in MyODBC 3.51.26 "Always handle binary function result as character data". Check it, and if your problem is as developer suspects, it will be gone.

Thanks for your interest in MySQL.

I fixed it. 

1. Installed the latest version.
2. Overwritten 3 files using myodbc 3.51.04-dll pack.

Software works fine. myODBC also works fine. We did not require to set any 
special Flags in MYODBC so I think its OK.

thank you