MySQL Bugs: #30816: Connector .Net

Bug #30816	Connector .Net
Submitted:	5 Sep 2007 5:12	Modified:	11 Mar 2008 18:34
Reporter:	Reg Proctor	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	Connector / NET	Severity:	S1 (Critical)
Version:	5.1.2 / 5.1.3	OS:	Windows (XP)
Assigned to:		CPU Architecture:	Any
Tags:	delete, insert, UPDATE

Description:
When creating a table the INSERT, UPDATE, DELETE do not get generated. The error give is: Failed to find or load registered .Net Framework Data Provider.

However, everything else works fine. And, if you manually create the SQL's the .Net application will work fine with the tables in the DataSet.

This is when using VB.net in VS 2005.

When I first created the Dataset it worked fine, all the SQL's were being generated. Somewhere down the line it just stopped. I since uninstalled/installed the connector several times. This is working with MySQL 5.0.22 on Windows 2000 Server with VS 2005 on a XP client.

-Reg

How to repeat:
I don't know.

Suggested fix:
The work around is to create the 3 SQL's yourself. Everything works from that point onwards.

Hi Reg and thanks for your report.

This looks like GAC registration problem... Can you please check on discussion in bug#30425 (especially [23 Aug 17:14] Reggie Burnett) and try registering c/NET driver manually?

Waiting on your results.

Hello Tonci,

I tried the suggested fix in discussion bug#30425, here is the result:

C:\Program Files\MySQL\MySQL Connector Net 5.1.2\Binaries\.NET 2.0>"E:\Program F
iles\Microsoft Visual Studio 8\SDK\v2.0\Bin\gacutil.exe" /i mysql.data.dll
Microsoft (R) .NET Global Assembly Cache Utility.  Version 2.0.50727.42
Copyright (c) Microsoft Corporation.  All rights reserved.

Assembly successfully added to the cache

After this result I tried adding a table to the Dataset again, same problem.

Reg, although your offer is tempting I am not allowed to do such things unless you have a support contract covering it...

Ok, so driver *is* properly registered in GAC and you still have a problem. Can you try with latest snapshot available at http://downloads.mysql.com/snapshots/mysql-connector-net-5.1/mysql-connector-net-5.1.3-200... and inform me of result? If I'm not mistaken, this should have been fixed with patch for Bug#26347...

The results with this are a bit mixed. I think it will be easier for you to see the exact results rather than me describe them only. Here's what I did:

I closed VS2005, uninstalled connector/.net 5.1.2, installed connector/.net 5.1.3, reopened VS 2005. I then removed the old references and created new ones which eliminated a bunch of generated errors.

When I tried to add a table the result was this:
http://www.capiogroup.com/temp/MySQL_Connector_5.1.3_Usage_Result1.jpg

As you can see this is a real mixed bag. The UPDATE looks fine but was not generated, The INSERT returned an error and the DELETE didn't even show up.

On the previous version all three where the same (like the INSERT is now).

When, just as a test I tried changing the SELECT SQL (by removing unnecessary spaces) I got the following:

http://www.capiogroup.com/temp/MySQL_Connector_5.1.3_Usage_Result2.jpg
http://www.capiogroup.com/temp/MySQL_Connector_5.1.3_Usage_Result3.jpg

And here is all the properties in the table connector in the DataSet that was just created.
http://www.capiogroup.com/temp/MySQL_Connector_5.1.3_Usage_Result4.jpg

FYI, I have installed my VS2005 on my "D" drive for space reasons, but in the same path it would have been on the "C" drive if I just let it install normally.

Your connector is installed in its default location on my "C" drive.

More information for 5.1.3 (this did not happen in 5.1.2: When I shut down my application I get the following error:

System.Threading.SemaphoreFullException was unhandled
  Message="Adding the given count to the semaphore would cause it to exceed its maximum count."
  Source="System"
  StackTrace:
       at System.Threading.Semaphore.Release(Int32 releaseCount)
       at System.Threading.Semaphore.Release()
       at MySql.Data.MySqlClient.MySqlPool.RemoveConnection(Driver driver)
       at MySql.Data.MySqlClient.MySqlPoolManager.RemoveConnection(Driver driver)
       at MySql.Data.MySqlClient.NativeDriver.Dispose(Boolean disposing)
       at MySql.Data.MySqlClient.Driver.Close()
       at MySql.Data.MySqlClient.NativeDriver.Finalize()

MySQL_Connector_5.1.3_Usage_Result1

Attachment: MySQL_Connector_5.1.3_Usage_Result1.jpg (image/jpeg, text), 100.67 KiB.

MySQL_Connector_5.1.3_Usage_Result2

Attachment: MySQL_Connector_5.1.3_Usage_Result2.jpg (image/jpeg, text), 55.39 KiB.

MySQL_Connector_5.1.3_Usage_Result3

Attachment: MySQL_Connector_5.1.3_Usage_Result3.jpg (image/jpeg, text), 65.07 KiB.

MySQL_Connector_5.1.3_Usage_Result4

Attachment: MySQL_Connector_5.1.3_Usage_Result4.jpg (image/jpeg, text), 296.42 KiB.

Hi Reg and sorry for the delay in processing. I can not repeat this problem using 5.1.4 plug-in and driver built from latest sources. Does this still bother you?

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".