Forum Moderators: open

Message Too Old, No Replies

MySql Errors since Upgrade

GoogleBot and other Bot Errors

         

sands904

1:07 am on Dec 1, 2009 (gmt 0)

10+ Year Member



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!

rocknbil

4:40 am on Dec 1, 2009 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Welcome aboard sands904, you will likely have better luck in the ASP/.NET [webmasterworld.com] forum, sounds more like an issue with the programming and server than the DB.

sands904

1:41 pm on Dec 1, 2009 (gmt 0)

10+ Year Member



Thanks, I will try over there. The only reason I tried in database is because the errors are coming from the actual connector provided by MySQL. I was hoping someone would know something about that or possibly some optimization/setting changes/etc that I could do on the database that may help. Thanks again.

sands904

2:15 pm on Dec 1, 2009 (gmt 0)

10+ Year Member



I forgot to mention that we have been using the same .net code for over two years without any issues. So I truely believe this is a database/connector issue. If anyone can give any pointers at all they would be greatly appreciated. Thanks!