Re: ODBC connect error code

[Pär Iwarson]

We have had a simular problem with our site. We have a MySQL server 4.0.21 on Linux and webserver on Windows 2003 Web Edition. The site is built with ASP.Net. We use MyODBC 3.51.10.

The problem that occured was that the connection was lost at times for about between 10 seconds and 1 minute each time. The problem seeme to occure from nowhere. It worked fine for about a year and then it started to occure sometimes. We made no changes that could be blamed. The problem started to escalate recently and as we tried more and more to find the problem it just got worse.

First we blamed the ISP's network and the lines between the Linux and the Windows computers. But we tried to connect the 2 computers p2p and that didn't work. Then we put our site on an own switch and that didn't work.

Then we blamed the ODBC and reinstalled MyODBC and .Net ODBC Provider but that didn't help either. Nothing worked and the more we work on the problem the problem just occured more often. The duration of the lost connection still were between 10 seconds and around a 1 minute. And we could relate the problem to anything.

Finally we found something that seemed to cause the problem. The one thing that seemed to cause the problem where MySQL Control Center. The connection between the application and the database were never lost when MySQL Control Center was down. But as soon as we started up MySQL Control Center the connection was lost for between 15 seconds to 1 minute. Since we realized this we haven't used MySQL Control Center and since then the problem is gone and we have had no interuptions.

So stay out of MySQL Control Center. I don't know if this is a coincident and I don't know why this would cause connection problems. If someone has any explaination for this and could explain how MySQL Control Center could be a conflict to MyODBC I would really appreciate the answer.

The version of MySQL Control Center we use is 0.9.4.

I don't know if this will help anybody, but I would be glad if we could confirm that the problem was actually caused by MySQL Control Center. If not I would really like to know why we got these problems out of nowhere.