Bug #44428 Cannot recreate instance after clean install (apply security settings fails)
Submitted: 23 Apr 2009 11:07 Modified: 17 Aug 2009 16:36
Reporter: Elena Stepanova Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Config Wizard Severity:S3 (Non-critical)
Version:5.1.30, 5.1.34, 5.0.72sp1, 5.0.81 OS:Microsoft Windows (XP, 2003)
Assigned to: Iggy Galarza
Triage: Triaged: D2 (Serious)

[23 Apr 2009 11:07] Elena Stepanova
Description:
After successful fresh installation, when security settings (including a root password) were applied, if I remove the instance and want to create a new one, I cannot do so -- in security options screen config wizard does not ask for the current password, and consequently configuration fails with error 1045 (Access denied for user 'root'@'localhost' (using password: NO)).

If I do exactly the same, but after an upgrade (NOT fresh installation), configuration wizard shows the 'current password' field, and configuration runs smoothly.

I found a few records complaining about error 1045 during installation, mostly in 'can't repeat' status (e.g. bug#6891, bug#36491), but they do not look quite the same.

How to repeat:
- uninstall MySQL and remove the data folder;
- install MySQL using default settings (any type of installation);
- configure instance using default settings, set a root password;
- make sure that configuration finished successfully;
- remove the instance using configuration wizard;
- make sure that configuration wizard reported that the instance was removed successfully;
- start configuration wizard again to create a new instance;
- configure the instance using default settings;

   => in security options screen, no 'Current password' field

- enter root password;
- press 'execute' in the final wizard screen 

  => configuration fails on the lat stage (security settings) with error 1045

Suggested fix:
Show 'current password' field in security settings screen.
[28 Apr 2009 17:26] Elena Stepanova
Configuration Wizard error screen

Attachment: config_wizard_error.PNG (image/png, text), 29.08 KiB.

[28 Apr 2009 17:26] Elena Stepanova
Connection error screen

Attachment: connection_error.PNG (image/png, text), 18.41 KiB.

[1 May 2009 6:56] Miguel Solorzano
Bug: http://bugs.mysql.com/bug.php?id=44596 marked as duplicate of this one.
[4 May 2009 16:46] Miguel Solorzano
Thank you for the feedback.
[12 May 2009 11:58] Miguel Solorzano
Bug: http://bugs.mysql.com/bug.php?id=44818 marked as duplicate of this one.
[21 May 2009 22:04] Miguel Solorzano
Bug: http://bugs.mysql.com/bug.php?id=45018 marked as duplicate of this one.
[26 May 2009 8:18] Sveta Smirnova
Bug #44428 was marked as duplicate of this one.
[28 May 2009 13:24] Sveta Smirnova
Bug #45156 was marked as duplicate of this one.
[4 Jun 2009 19:35] Sveta Smirnova
Bug #45341 was marked as duplicate of this one.
[17 Jun 2009 22:43] Iggy Galarza
Marked http://bugs.mysql.com/bug.php?id=45200 as a duplicate of this bug.
[26 Jun 2009 14:11] Iggy Galarza
Remove Instance sets FoundExistingDataDir reg key.

Attachment: bug44428.patch (application/octet-stream, text), 1.89 KiB.

[6 Jul 2009 16:13] Patrick Crews
Ok to push.
[17 Aug 2009 16:36] MC Brown
A note has been added to the respective changelogs: 

Creating a new instance after previously removing an instance would fail to complete the installation properly because the security settings could not be applied correctly.
[27 Jun 2010 17:14] Janet Shen
I discovered a workaround for this, which was to completely uninstall and delete Program Data and Program Files folders for MySQL, then when reinstalling, to **leave root password blank** in Configuration Wizard.  Log into MySQL with an empty password, then configure root password from there.

Hope that helps!