MySQL Bugs: #12196: Instance Configuration fails with Error 1130

Bug #12196	Instance Configuration fails with Error 1130
Submitted:	27 Jul 2005 7:15	Modified:	27 Jul 2005 12:28
Reporter:	gernot adams	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Server	Severity:	S1 (Critical)
Version:	5.0.10	OS:	W indows 2003 Server SP 1
Assigned to:		CPU Architecture:	Any

Description:
hi,
i install the MySQL 5.0.10 an then configure it with the Instance Configuration Wizard. When i click "execute" on the last page of this wizard i get the error message:

"
Connection Error:
The security settings could not be applied to the database because the connection has failed with the following error.

Error 1130
Host 127.0.0.1 is not allowed to connect to the MySQL server.

..."

A firewall is not running on this machine. netstat -a show that the server listen to this port:

C:\>netstat -a

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    pc-da-130:3306         pc-130:0            LISTENING

Then i can just click on "Cancel". The MySQL service is running but i can't connect to it.

Do you have any idea on that?

cheers
gernot

How to repeat:
see above

hi,
just for one thing: TCP/IP is enabled, ping on localhost repeats 127.0.0.1 and this problem never appears with the 5.0x-beta versions before. ;-) The server installation is "out of the box" and contains the latest updates.

cheers
gernot

Thank you for the bug report.

Looks similar too http://bugs.mysql.com/bug.php?id=12188. Workaround is suggested there.

hi,
funny things happen on the MySQL download page. When i look on the page this morning i saw (and download) version 5.0.10. When i look on the page now i see the old page from yesterday. Could it be that the release of this beta happen to quick or accidentially  ;-)

cheers
gernot

Yes, there is only 5.0.9 for all platforms at http://dev.mysql.com/downloads/mysql/5.0.html now. 5.0.10 was not _officially released_. I saw only a draft yesterday. So, please, wait for the release.

This is duplicate of bug #12188, how commented by Valeriy.
Thank you for the bug report.