Bug #56435 Error on OSX 10.6 using driver
Submitted: 1 Sep 2010 6:31 Modified: 3 Jan 2011 14:29
Reporter: Dick Impens Email Updates:
Status: Can't repeat Impact on me:
None 
Category:Connector / ODBC Severity:S1 (Critical)
Version:5.1 OS:MacOS (Version 10.6)
Assigned to: CPU Architecture:Any
Tags: Filemaker 11, ODBC Connector, OSX 10.6

[1 Sep 2010 6:31] Dick Impens
Description:
I've installed the OSX 10.6 driver, but every time I try to connect (in Filemaker Pro 11 via ODBC) I get this error message. I've set up a system-dsn and added the server, user, password and database parameters in ODBC manager of OS X. This seems to work ok, but as soon as I add a ODBC datasource to Filemaker, selecting the system-dsn I've created and adding the username and password this error occurs;

ODBC-fout: [iODBC][Driver Manager]dlopen(/usr/local/lib/libmyodbc5.so, 6): no suitable image found.  Did find:
	/usr/local/lib/libmyodbc5.so: mach-o, but wrong architecture
[iODBC][Driver Manager]Specified driver could not be loaded

I cannot find any solution to this.... can someone explain what I am doing wrong?

How to repeat:
Just try to add a the ODBC Source to any Filemaker file, this error occurs.
[1 Sep 2010 6:36] Tonci Grgin
Hi Dick and thanks fore your report.

Unfortunately, I do not have MAC box nor anyone has FileMaker to test with. I will, however, assign Sveta here but, imo, you should look into BugsDB and check many reports with similar synopsis.
[1 Sep 2010 7:02] Dick Impens
Hi Tonci,

Thanks for your fast reply. I've searched the BugDB, only one result, but no solution. I've even searched via google, no results so far. Hope Sveta can give me some answers...

Regards, Dick
[1 Sep 2010 11:19] Sveta Smirnova
Thank you for the feedback.

Unfortunately I only have Mac OSX 10.4, not 10.6, therefore can not test. 10.4 driver works fine. But which package do you use? Please send us filename of the file you downloaded.
[1 Sep 2010 12:02] Dick Impens
Hi Sveta,

Thank you for your fast reply. 

I've downloaded: Mac OS X ver. 10.6 (x86, 64-bit), DMG Archive Connector-ODBC
Filename: mysql-connector-odbc-5.1.7-osx10.6-x86-64bit.dmg

and installed it on Mac OS 10.6.4 with all the latest updates. 

Kind regards, Dick.
[7 Sep 2010 6:32] Tonci Grgin
Dick, I'd say you really need 32bit c/ODBC as almost all of the clients out there are *32bit*. This is a common mistake on all operating systems.

64bit ODBC drivers are useless unless you load them by hand from your own programs.

See also if discussion in Bug#50027 helps.
[7 Sep 2010 11:24] Dick Impens
Crash report OS 10.6 ODBC 32-Bit driver Filemaker

Attachment: crashreport.txt (text/plain), 42.58 KiB.

[7 Sep 2010 11:25] Dick Impens
Hi Tonci,

Thank you. I've removed all occurances of the 64-bit driver and installed the 32-bit driver. I do get a bit further, it connects and I see the tables. But if I select a table (in Filemaker via the ODBC connection) Filemaker crashes, every time. The crash report is a attachment. 

Kind Regards,
Dick
[7 Sep 2010 12:23] Tonci Grgin
Dick, 

I don't seem to find anything c/ODBC related in a crash... Can you please get a trace of ODBC calls for me (http://dev.mysql.com/doc/refman/5.1/en/connector-odbc-configuration-trace.html#connector-o...)?
[7 Sep 2010 12:47] Dick Impens
ODBC Trace Mac 10.6 32-Bit Filemaker

Attachment: ODBCTrace (application/octet-stream, text), 19.91 KiB.

[7 Sep 2010 12:47] Dick Impens
I've just posted the trace log of ODBC with Filemaker....
[7 Sep 2010 13:41] Tonci Grgin
Dick, there is no crash in this trace nor some unusual calls afais. However, I asked a colleague to take a second look.
[7 Sep 2010 13:45] Tonci Grgin
Maybe a complete table structure of table containing fields
	 | foondump2005                             |
and
	 | pink_phonenumber                         |
might help. Did you check if your table has errors?
[7 Sep 2010 13:56] Dick Impens
SQL Dump of fonedump2005

Attachment: foondump2005.sql (application/octet-stream, text), 5.22 KiB.

[7 Sep 2010 13:59] Dick Impens
The structure of pink_phonenumber is included in de foondump2005. 
I do not thing this file is the problem, it runs fine in Navicat or any other mysql tool. 

Kind regards, Dick.
[7 Sep 2010 14:34] Tonci Grgin
To summarize... Nothing is pointing to c/ODBC in stack trace. ODBC trace shows ENTER to SQLColumnsW (pink) but there is no exit. Could be that you just stopped tracing... Is this specifically related to pink_phonenumber table or does it happen for all the tables?
[7 Sep 2010 15:54] Dick Impens
Hi Tonci,

No, that is the point where FM crashes. It happens on all the tables. It is strange, when I use the 'commercial' app ActualODBC all goes well. I thought it perhaps be a Filemaker problem, but then it should occur on ActualODBC as well, right?

Regards,
Dick.
[7 Sep 2010 16:00] Tonci Grgin
Or the ActualODBC knows of FM and/or iODBC bug we know nothing about...

Well, as I said, stack trace shows no proof c/ODBC actually crashed (or, at least, I see none) so I have no other option but to abandon this report :-( FM is commercial piece of SW and none of us has a copy.

Sorry.
[20 Oct 2010 5:55] Scott Steven
I have installed the 32 bit with and I am getting the same results.  Suppose a post to FM is in order but so you know the Actual Technologies is working.  but the lic cost.  this is has been broken for so long I will be very surprised when it actually works.
[3 Jan 2011 14:29] Geert Vanderkelen
Since we don't have the used applications, like FileMaker, available, I'm using Python and pyodbc to verify the ODBC connection to MySQL.

Using the latest MySQL Connector/ODBC 5.1.8 (32-bit) and following script:

import pyodbc
cnx = pyodbc.connect('DRIVER={MySQL ODBC 5.1 Driver};SERVER=localhost;DATABASE=test;UID=root;PWD=')
cur = cnx.cursor()
cur.execute("SELECT * FROM t1")
print cur.fetchall()

I can successfully select data.

Maybe Apple's ODBC Administrator can be used to generate a trace file?
 http://support.apple.com/downloads/ODBC_Administrator_Tool_for_Mac_OS_X
[2 Feb 2011 13:12] Scott Steven
I just reinstalled the MyODBC Driver on a new system to see if this was still having the same issue. and it is.

I have also created a trace file but after reading it there is nothing about the crash of filemaker.  So I will go back to actual technologies and pay for a license as there driver works with out errors ..
[2 Feb 2011 19:17] Gonzalo Robaina
Hi, 

I'm having the same issue, when I try to select any tables, FileMaker just crash without any error displayed. It just closes itself.

I've installed the demo version of ActualTech ODBC driver and it works fine (with the limitation of 3 rows per query).

OS: 10.6.6
FileMakerPro 11.02v Advanced
mysql-connector-odbc-5.1.8-osx10.6-x86-32bit

It would be awesome to have this fixed.
[8 Aug 2011 10:09] M H
Installing the 32 bit version of the ODBC connector fixed this for me.
[24 Apr 2012 4:41] Robbie R
FileMaker do not support the Mysql community ODBC driver. They only support Actual Technologies, Open Source Databases version 3.0 

http://help.filemaker.com/app/answers/detail/a_id/6420/kw/mysql/session/L3RpbWUvMTMzNTI0Mj...
[24 Apr 2012 5:54] Tonci Grgin
Robbie, it says FM supports 3.51 branch of c/ODBC driver which is our single-byte ODBC driver, ie. not using WIDE (W) functions.
ODBC is old and well defined standard. However, some implementations do not follow the specs so closely. My guess is that the commercial driver you are talking about knows of fault in FM and/or iODBC and is bypassing it by "bending" the rules. We, however, have no such liberty as we need to support as much of other platforms, driver managers, 3rd party clients as possible.