Bug #11666 Error when opening connection to localhost
Submitted: 30 Jun 2005 12:52 Modified: 1 Jul 2005 15:30
Reporter: Isaac Troll Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Query Browser Severity:S1 (Critical)
Version:1.1.10 OS:Windows (Windows XP sp2)
Assigned to: CPU Architecture:Any

[30 Jun 2005 12:52] Isaac Troll
Description:
I recently upgraded to mysql query browser 1.1.10 from 1.1.6.  However now that I upgraded as soon as I try to run query browser connecting to localhost, or any other server I get the following error.

As soon as query browser opens I get:

"A MySQL error was encountered.  The message is:

Could not fetch Catalogs/Schemata data.
The following eror occured: Lost connection to MySQL server during query (2013).

I have since uninstalled query browse 1.1.10, and moved back to 1.1.6 and everything works fine.  However the reason for my upgrade was because I could not get editing of a resultset to work, so I figured I would upgrade to see if that would fix the problem.  Needless to say it didn't.

How to repeat:
Install Query Browser 1.1.10, and try to connect to a database.

Suggested fix:
Not sure.  This is probably not an error everyone gets.
[30 Jun 2005 17:50] Aleksey Kishkin
'lost connection' means something wrong with mysql server, which mysql server do you use (version)? do you have any errors in the mysql error log?
[30 Jun 2005 18:40] Isaac Troll
There are no errors in the log.  the database is version 4.0.13, and the query browser is 1.1.10.  With browser 1.1.6 I could connect to the database fine.  I have however just upgraded the database to version 4.1.12a, and now the query browser works fine.  Maybe there was some sort of compatability issue with the old db version and the newer browser version.  At least an upgrade to the database solved it.  And gave me some nice new features I was hopeing for on the database side that I didn't realize were available yet.
[1 Jul 2005 15:30] MySQL Verification Team
Hello,

if you can't repeat this problem with latest server version and with latest MySQL query browser, then I close this bug report.