Errors during peak traffic times

Upgraded MySQL database

[sands904]

I just recently upgraded to MySQL 5.1 and the .NET Connector 6.1.3. I have had a huge influx in errors since this.
Background:

I have several .net sites on a single quad core server with 4GB ram. I also upgraded my internet service which has doubled my upload speed from 2Mbps to 4Mbps. Along with that I upgraded my version of MySQL and the connector. I am now receiving anywhere from 5000 to 15000 errors per day from one of my sites (the one with the most traffic). They seem to be lumped together in chunks of time and most of them are from GoogleBot, ContextAdBot, etc.

I have placed several posts on the MySql forums and reported a bug but am getting no where with them. I am hoping someone can shed some light on this or point me in a direction to fix these.

Here are the errors I am receiving:

System.Data.DuplicateNameException
A DataTable named 'Procedure Parameters' already belongs to this DataSet.

System.ArgumentException
The given name 'procedure parameters' matches at least two names in the collection object with different cases, but does not match either of them with the same case.

System.ArgumentException
The given name 'procedure parameters' matches at least two names in the collection object with different cases, but does not match either of them with the same case.

I have tried digging through the 6.1.3 connector code and have also tried the 6.0.5 connector. I tried going back to the same connector I was originally using 5.0.7 and instead of receiving errors I would experience huge page loads and backed up queries.

Any help would be greatly appreciated!

[Ocean10000]

I have not personally seen the errors you have listed. I only have on a rare occasion to work with MySql. I am not sure if MySql is case sensitive or not. But I have a feeling from the errors provided that it is. And that you are executing sql statements which are the same fields, but cased differently causing the MySql connector problems refreshing the datasets.

It might be worth looking at the change logs for the new version to see if they changed any fundamentals of the connector between the previous version you were using.