Bug #59801 | Not able to connect to MySQL server | ||
---|---|---|---|
Submitted: | 28 Jan 2011 18:22 | Modified: | 1 Apr 2014 8:53 |
Reporter: | MARIO van Grichen | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Config Wizard | Severity: | S1 (Critical) |
Version: | 5.5.8 | OS: | Windows |
Assigned to: | CPU Architecture: | Any |
[28 Jan 2011 18:22]
MARIO van Grichen
[28 Jan 2011 18:47]
Valeriy Kravchuk
Do you have MySQL server (5.5.8 I assume?) up and running at that port on localhost? If you don't and got a problem at some step of Configuration Wizard, please, describe all the steps performed and error message9s) you've got (if any).
[29 Jan 2011 1:00]
MARIO van Grichen
Hi Valeriy Using MySQL Server Configuration Wizard --------------------------------------- 1- Standard Configuration 2. Install as Windows Service MySQL5 Launched the MySQL Server Automatically (ticked) 3. Redefined password for user "root" 4. Execute a) Prepare Configuration (OK) b) Write configuration file at c:\Program Files\MySQL\MySQL Server 5.5\my.ini (OK) c) Start Service (OK) d) Apply Security Settings (not OK) Error message "The security settings could not be applied to the database because the connection has failed with the following error" --------------------------------------------------------- Error Nr. 2002 Cant´t connect to MySQL server on 'localhost' (10061) --------------------------------------------------------- Comments ------------------------- I have included service MySQL5 which is the service name running on "services.msc" on the the windows firewall exceptions at port 3306 as per default Hostname 127.0.0.1 as per default I even uninstalled Avast anti virus Still cannot connect. This is drivng me crazy. I really liked the EER modelling feature and the possibilty of forward engineering but as it is right now it turned out to be a waste of time, I would like to take all the advantage I can get from this Workbench application. Valeriy, is this a bug or a feature? What am I doing wrong? Is there a way to overcome this difficulty? Thanks in advance Kind regards Mario van Grichen
[29 Jan 2011 1:04]
MARIO van Grichen
Sorry just forgot to tell you. Yes I do have I have mysql-5.5.8-win32 server Mario van Grichen
[29 Jan 2011 1:12]
MARIO van Grichen
My SQL server error
Attachment: MySQL.JPG (image/pjpeg, text), 35.94 KiB.
[29 Jan 2011 9:26]
Valeriy Kravchuk
First of all, as service started OK (you can check for mysqld.exe process running in a task manager) you probably should be able to connect from any local client (including Workbench) as a root user with no password. Please, try. Had you enabled root connection from remote machines or anonymous login in the Config Wizard? There are check boxes for these. If you had, this is a known bug in Wizard.
[30 Jan 2011 19:11]
MARIO van Grichen
Hi Valeriy This time I checked the boxes to allow for anonymous login and connection from remote machines to no avail. I checked the running processes in the task manager and mysqld.exe is running. The problem arises on the 4th and last step of the MySQL configuration wizard when it tries to apply the security settings. I still get the same error message. If I am successful at this 4th stage I believe everything will work out fine. Regards Mario
[1 Feb 2011 10:29]
MySQL Verification Team
Are you able to connect local with user root without password as Valery asked before?. Thanks in advance.
[1 Feb 2011 12:33]
MARIO van Grichen
Hi Miguel At the beginning I did not even know how to do it but then I found a way and the four steps of the configuration wizard ended out successful. However it gives me the same error message when I test the connection from the Workbench. This is driving me crazy. Thank you. Mario
[1 Feb 2011 12:49]
MySQL Verification Team
Thank you for the reply. So the issue is with Workbench (with the command line client mysql.exe you are able to connect)?. If yes then the bug report needs to switch from server to Workbench. Thanks in advance.
[1 Feb 2011 13:07]
MARIO van Grichen
Miguel I am a total ignorant as to CLI regarding MySQL, but I will investigate and come up with some further results. Thank you so much. Mario
[9 Feb 2011 13:29]
MARIO van Grichen
screenshot01
Attachment: MySQL_DetailedConfig01.JPG (image/pjpeg, text), 34.20 KiB.
[9 Feb 2011 13:30]
MARIO van Grichen
screenshot02
Attachment: MySQL_DetailedConfig02.JPG (image/pjpeg, text), 44.92 KiB.
[9 Feb 2011 13:30]
MARIO van Grichen
screenshot03
Attachment: MySQL_DetailedConfig03.JPG (image/pjpeg, text), 44.72 KiB.
[9 Feb 2011 13:30]
MARIO van Grichen
screenshot05
Attachment: MySQL_DetailedConfig05.JPG (image/pjpeg, text), 44.75 KiB.
[9 Feb 2011 13:31]
MARIO van Grichen
screenshot06
Attachment: MySQL_DetailedConfig06.JPG (image/pjpeg, text), 37.50 KiB.
[9 Feb 2011 13:31]
MARIO van Grichen
screenshot07
Attachment: MySQL_DetailedConfig07.JPG (image/pjpeg, text), 40.98 KiB.
[9 Feb 2011 13:31]
MARIO van Grichen
screenshot08
Attachment: MySQL_DetailedConfig08.JPG (image/pjpeg, text), 37.55 KiB.
[9 Feb 2011 13:31]
MARIO van Grichen
screenshot09
Attachment: MySQL_DetailedConfig09.JPG (image/pjpeg, text), 37.22 KiB.
[9 Feb 2011 13:32]
MARIO van Grichen
screenshot10
Attachment: MySQL_DetailedConfig10.JPG (image/pjpeg, text), 65.12 KiB.
[9 Feb 2011 13:32]
MARIO van Grichen
screenshot04
Attachment: MySQL_DetailedConfig04.JPG (image/pjpeg, text), 36.57 KiB.
[9 Feb 2011 13:35]
MARIO van Grichen
I still believe this is a passowrd issue and thus server related. No matter what options I choose on the MySQL Instance Configuration Wizard the result on the CLI is the same: -------------------------------------------------------------------- C:\Program Files\MySQL\MySQL Server 5.5\bin>telnet localhost 3306 H 5.5.8?kmc*CRQ$!?ǧ\$;?hmm[^I2^mysql_native_password Connection to host lost. C:\Program Files\MySQL\MySQL Server 5.5\bin>mysqladmin -u root ping mysqld is alive C:\Program Files\MySQL\MySQL Server 5.5\bin> -------------------------------------------------------------------- This might be password related. MySQL server is up and running but I cannot connect to localhost on 3306 (I have tried other ports)
[9 Feb 2011 14:40]
Valeriy Kravchuk
This is, probably, a duplicate of bug #59038 (based on the screenshots uploaded). Try to NOT enable root access from the remote machines when installing and check if this will change anything.
[10 Feb 2011 2:04]
MARIO van Grichen
Valeriy As I told on my previous comment I have tried all the possible combinations and this includes not enabling the root access from remote machines which was my very first settings. It never workded out and it always returned the same error. Thanks you for bug #59038 as though I am still digesting it:) I am a newbie so there is a lot there to figure out and most of it I cannot understand either because I don't have enough knowledge or I have not experienced it myself. ---------------- Possible problem ---------------- I have IIS 5.1 installed. Could this be a problem? Definetely I get more and more convinced this is password related and that I my credentials are not being accepted by the MySql engine. Logically and intelectually speaking one question remains. Why should a fresh new installation require an old password? I this a bug, a feature or a bugged feature? Another way of looking at it. Why should I be prompted for an old password of my new credit card when I never had one before? Can you understand me? Thanks in advance. Mario
[10 Feb 2011 4:21]
Valeriy Kravchuk
Mario, If you had NEVER had MySQL 5.5.x installed on this machine, it is indeed weird to ask for an old password. But now, after numerous installation attempts, you do have a data directory of 5.5.x in place. So, if you want to make sure that this is a bug in 5.5.8's configuration wizard related to password settings, please, uninstall it, remove data directory (it is in Documents and Settings/All users/Application Data) and try again. You should NOT be asked for an old root password. Do not enable access for root from remote machines or anonymous login also (these lead to know bugs).
[11 Feb 2011 12:57]
MARIO van Grichen
Did all that you asked me to and still the same error.
[11 Feb 2011 12:57]
MARIO van Grichen
Did all that you asked me to and still the same error.
[11 Feb 2011 12:57]
MARIO van Grichen
Did all that you asked me to and still the same error.
[11 Feb 2011 12:57]
MARIO van Grichen
Did all that you asked me to and still the same error.
[14 May 2011 11:28]
Valeriy Kravchuk
Please, check if the same problem happens with a recent version, 5.5.12.
[14 Jun 2011 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
[11 Jan 2014 21:02]
Tomer Guri
Hi, I am expiriencing same thing. I follow everything and can't find a way to make it work. Everything described here is exactly what I expirience, so no need to repeat. I would like to know the next steps I can do as nothing worked for me so far. I am running MySql 5.06. Windows XP SP3. Tomer.
[1 Apr 2014 8:52]
Yngve Svendsen
Closing this: no forther information was supplied on the original issue for almost three years. @Tomer: please submit a separate bug report if you still experience your problem, stating correct Server version number (5.06 is not a valid one) and describe your problem in detail. Also please note that if you are using 5.0, that was EOL several years ago. If you are referring to 5.6, you are presumably using the MySQL Installer for Windows, in which case your problem is very likely different from the one referred to in this bug report.
[1 Apr 2014 8:53]
Yngve Svendsen
Closing this: no further information was supplied on the original issue for almost three years. @Tomer: please submit a separate bug report if you still experience your problem, stating correct Server version number (5.06 is not a valid one) and describe your problem in detail. Also please note that if you are using 5.0, that was EOL several years ago. If you are referring to 5.6, you are presumably using the MySQL Installer for Windows, in which case your problem is very likely different from the one referred to in this bug report.
[1 Apr 2014 8:53]
Yngve Svendsen
Closing as per above comment.