Bug #42191 | Cannot Logon to MySQL Administrator when multiple MySQL servers are installed | ||
---|---|---|---|
Submitted: | 19 Jan 2009 7:03 | Modified: | 28 Jan 2009 13:18 |
Reporter: | Ngu Soon Hui | Email Updates: | |
Status: | Won't fix | Impact on me: | |
Category: | MySQL Administrator | Severity: | S2 (Serious) |
Version: | 1.2.15 | OS: | Windows |
Assigned to: | Mike Lischke | CPU Architecture: | Any |
[19 Jan 2009 7:03]
Ngu Soon Hui
[19 Jan 2009 13:05]
MySQL Verification Team
Thank you for the bug report. I noticed this behavior when the server instance wasn't installed using the package installer.
[28 Jan 2009 13:18]
Mike Lischke
This behavior is by design. The server does not report where it found its config file (yes, there are many locations where the file can be) and the command line client does not need to know that, so it works nicely. MySQL Administrator also can login and do the things that don't require the knowledge which config file was used. However, in order to find the right configuration file it has no other help than examining what the service entries contain. These entries have a parameter for the given command line that specifies the path to the used configuration file. Without the service entries MA is lost (and wild speculating which file could be the right one is highly dangerous). So what you can do are two things: 1) Install the servers using their installers, or, if that is not desirable 2) Start MA in service mode (hold the ctrl key in the login dialog, the Cancel button switches to Skip, click on that) and add a new service entry with help of MA, using your customized config file and mysql binaries. Next time you start MA it will then be able to finde these files. Mike
[27 Feb 2009 3:23]
Edward Reid
I have exactly the same problem. I installed using the package installer, and I think my installation is totally "clean" with respect to the various points raised in the many reports of this bug. I installed from mysql-essential-5.1.31-winx64.msi mysql-gui-tools-5.0-r16-win32.msi using the standard installers. This was a new install (no upgrade, no old DB) on a new Vista64 system (all updates applied). All files are in default locations AFAIK. I ran the installer from an admin account (not elevated from a normal account). I did have to uninstall and reinstall several times before it completed correctly; I don't know why. I have been unable to get around the "Either the server service or the configuration file could not be found". The locations of the binary and config files are C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld.exe C:\Program Files\MySQL\MySQL Server 5.1\my.ini Things I've tried, and other notes: 1) I disabled the MySQL service and set up a new service, as suggested in this thread by Mike Lischke. I got the same result. 2) I have tried adjusting the position of the quote around --defaults-file= and see no difference. 3) The binary and config paths in the MA configuration are correct. I've checked them and reset them several times, always either by browsing to the file (for the binary) or by copying the path in another program and pasting it (for the config). The section name shown by MA is mysqld, which is where I'm looking in the config file. 4) The server is using port 3306. I CAN connect -- if I enter an incorrect password; I get a different error. Therefore I assume the error is in locating the config file or the contents of the config file. 5) The port item is active in the config file -- I have not had the problem reported at times of config file items getting commented out. 6) I tried commenting out default-storage-engine as suggested by one user in another thread. This made no difference. 7) I do have another version of MySQL installed as part of the hMailServer installation. (I realize that you do not support this installation, and mention it only as a possible factor, especially since the OP of this thread thinks the problem is related to multiple installations.) It is installed in a different folder -- in fact in the x86 program files -- and uses port 3307. I see no sign of interaction between the two installations. However, I suppose it's possible, though unlikely, that MA is getting confused when it finds two MySQL services (albeit with different names). 8) The name of the server binary does keep shifting between ...\mysqld and ...\mysqld.exe. I don't know whether Windows or MA is doing this. It would help A LOT if MA would report the exact error, rather than this catch-all. Edward
[15 Apr 2009 15:29]
MySQL Verification Team
Bug: http://bugs.mysql.com/bug.php?id=44288 has been marked as duplicate of this one.