"catastrophic failure" in Teststand database viewer using mySQL

[EHat]

Hello all,
I am using Teststand 3.1 and mySQL version 5.0.3 I have everything set up and teststand seems to be logging results to the database. The reason I say this is because I can see the data using a mySQL query browser. The problem is when I try to use the Teststand database viewer I get a "Catastrophic Failure". I right click on a field from the database and say view data and I get the failure. Any ideas on what this problem is and/or how to fix it?
Thanks in advance.
EHat

[Scott_Richardson]

EHat -
I just debugged this problem last week using MYSQL source for their ODBC driver. This appears to be a bug in their ODBC driver.

Basically the MS DataGrid control is trying to access catalog info from a handle that has not yet been connected to the database. Internally in MYSQL a function table is null and a dereference occurs which causes an access violation. Even though the MS control should be better behaved, the MYSQL driver should be returning an error if the table is null, not crashing.

For the next version of TestStand we will workaround this problem. I have an updated DatabaseViewer that you can try attached to this posting.

[EHat]

Thanks, I tried the attached file but I got the same results. Any other ideas?

[Scott_Richardson]

Ehat -
What version of the ODBC driver are you using?

[Scott_Richardson]

EHat -
You can see this problem easily without TestStand if you just:
1) Create an empty test.udl text file in a directory
2) Edit the udl file by double clicking on it
3) In the Data Link Properties dialog box, on the Provider, select ODBC
3) In the Data Link Properties dialog box, on the Connection tab,
a) Select a ODBC data source under the Use Data Source Name combo box
b) Select a database in the Initial Catalog combo box
4) Test Connection -> Catastrophic Failure

I have reported this to MySQL, see...
http://bugs.mysql.com/bug.php?id=10238

When you specify a data link you can either use the Data Source Name
Provider=MSDASQL.1;Persist Security Info=False;Data Source=MySQL LocalHost

or you can use a connection string:
Provider=MSDASQL.1;Persist Security Info=False;Extended Properties="DATABASE=test;
DSN=MySQLLocalHost;OPTION=H,í;PORT=0;UID=root"

If you use the connection string, the database viewer works around the problem. Try this for now.

[Adamls]

I had trouble with the same "catestrophic failure" error in TS last year.
http://bugs.mysql.com/bug.php?id=7696
Supposedly, MySQL Connector/ODBC 3.51.11 was going to fix the problem (assuming this is actually the same problem).
At the time, one fix was to use an older version such as 2.50.
I will try your fixes in order to use version 3.51.11.
Thanks,
AdamLS

[Phil Rawlings]

Hello All,

I've just encountered the same problem using version 3.51.12 of the MyODBC driver. Looks like the easiest fix is to leave the "Enter the Initial Catalog to Use:" field blank - since you would have configured this when setting up the DSN - then everything works nicely.

I found the answer here (after a LOT of searching!) - I can't believe that more people havent encountered this issue!

http://forums.mysql.com/read.php?37,35642,41252#msg-41252

- Phil