Bug #29950 Cannot connect to local host server during configuration
Submitted: 21 Jul 2007 18:55 Modified: 22 Aug 2007 18:59
Reporter: walter massey Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: Errors Severity:S3 (Non-critical)
Version:5.0.45 OS:Microsoft Windows
Assigned to: MySQL Verification Team CPU Architecture:Any

[21 Jul 2007 18:55] walter massey
Description:
when i try to "apply security settings" while configuring, i receive the error message "The security settings could not be applied to the database because the connection has failed with the following error.

Error Nr. 2003
Can't connect to MySQL server on 'localhost' (10061)

If a personal firewall is running on your machine, please make sure you have opened the TCP port 3306 for connections. Otherwise no client application can connect to the server. After you have opened the port please press [Retry] to apply the security settings.

If you are re-installing after you just uninstalled the MySQL server please not that the data directory was not removed automatically. Therefore the old password from your last installation is still needed to connect to the server. In this case please select skip now and re-run the Configuration Wizard from the start menu."

I did the first one, opening TCP port 3306, but it still came up. And i was not re-installing MySQL either.

How to repeat:
repeat above?
[22 Jul 2007 18:59] MySQL Verification Team
Thank you for the bug report. I was not able to repeat the behavior reported,
could you please try to start the server as standalone within a DOS command
prompt:

- Go to bin install directory.
- Issue the below command changing the my.ini path file for your actual path:

mysqld-nt --defaults-file="path_my.ini" --standalone --console

and see which messages error are printed. Thanks in advance.
[22 Aug 2007 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".