MySQL Bugs: #22595: ADO connecting with MyODBC 3.51.12: "Catastrophic failure"

Bug #22595	ADO connecting with MyODBC 3.51.12: "Catastrophic failure"
Submitted:	22 Sep 2006 15:34	Modified:	29 Sep 2006 21:19
Reporter:	Brian Kolstad	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Connector / ODBC	Severity:	S2 (Serious)
Version:	3.51.12; 3.51.14	OS:	Windows (Windows 2003, XP)
Assigned to:		CPU Architecture:	Any

Description:
Connecting to MySQL 5.0.18 OR 5.0.24a (the error happens on both versions) with ADO and MyODBC 3.51.12, the connection fails with the error message "Catastrophic failure".

I found bug reports referring to the same issue with version 3.51.10 (which was supposed to be resolved with version 3.51.12).

Installing an older version (3.51.09 or 3.51.06) solves this issue, but this isn't an acceptable workaround since it introduces the "Multi step" error when  using SUM() on int fields.  

How to repeat:
Install MySQL 5.0.24 
Install MyODBC 3.51.12
Set up an ODBC driver using MyODBC.
Test the connection in the Connector/ODBC setup window.  The test works correctly: "Success; connection was made!"
Connect using ADO.  This is the code that I used (C++ Builder):
    TADOConnection * sql_connect=new TADOConnection(NULL);
    sql_connect->ConnectionString=AnsiString("DSN=mysql_DSN");
    sql_connect->Open();

Hi Brian.

Can you please attach entire Builder project as well as MyODBC options you use.

I have uploaded an example program (bug-project-22595.zip).
The Connector/ODBC are as follows:
Login:
  Data Source Name: mysql
  Description: mysql
  Server: localhost
  User: default
  Password: default
  Database: tmp

"default" is setup as a user with access to the "tmp" database.

Connection Options: I left all options blank (Default)

Advanced: No flags are checked

I cannot recreate this error on Windows XP.

I'm also at a slight disadvantage for debugging this issue.  We were on a time limit and had to go live with the 3.51.09 version of MyODBC on our Windows 2003 Web Server.  I'm now adjusting queries to remove the "Multi-step" errors as they pop up.  I would like to find a solution to this, but now any testing will need to be done during low traffic hours.

Hi Brian.

Don't see any files attached to this report. Where did you upload project to?

The file was too large to attach using the MySql Bugs interface.  I uploaded the file to: ftp://ftp.mysql.com/pub/mysql/upload/

New information:
I was NOT able to recreate this same issue on another Windows 2003 server.  This leads me to think that this might be a configuration issue.

Brian, this looks definetly "machine related". On my XP Pro SP2 box I'm able to repeat this crash from within Delphi 6 just by changing things inside property editor of TADOConnection... If I click "Test connection" inside Delphi IDE TADOConnection property editor -> Crash. If I just click to drop down database list -> all ok... Anyway, compiled exe does not work. Tested on 3.51.14 too with MS OLEDB provider for ODBC drivers who, infact, throws design time and RT error.
I will test on other machines available to me and see what could be done...
If you can provide any more info regarding this, please do.

The error was being cought by DrWatson as follows:
"The exception generated was c00000fd at address 77E6B793 (kernel32!SwitchToFiber)"

We host our servers at RackSpace.  Their recomendation was to replace the processors and memory, which they did at a scheduled time that evening. 

After swaping the processors and memory, I was able to install and use MyODBC 3.51.12 without the "Catastrophic Failure".

It looks like the "bug" was actually a hardware issue.

Thanks for your help!

I have the same problem with the latest MyODBC Driver (3.51.15). When I like to
connect with a MySQL Engine (5.0.41) through ADO  with the MyODBC provider
appears the following error: ADO Error: Catastrophic failure. How i can resolve
this problem? is there any patch to this driver? Thanks and sorry about my
english...

Cesar, "ADO Error: Catastrophic failure" can mean anything... I do not posses any magical skills to give you an answer. Please read related forum threads and bug reports and check again your code and hardware...