MySQL Bugs: #74119: Cannot continue installation after path conflict is resolved

Bug #74119	Cannot continue installation after path conflict is resolved
Submitted:	27 Sep 2014 17:11	Modified:	7 Dec 2014 0:10
Reporter:	Aaron Cohn	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL for Windows: Installer	Severity:	S2 (Serious)
Version:	5.6.21.0 community (not web installer)	OS:	Windows (Windows 7 SP 1)
Assigned to:		CPU Architecture:	Any

Description:
During installation, MySQL Installer wanted to use the path "ProgramData/MySQL/MySQLServer 5.6", but this path already existed, so there was a path conflict. I resolved the conflict by renaming the existing folder. Then I clicked the little arrow button near the "Data Directory" field, and the warning was cleared. However, there was no way to continue with the installation. No "Next" or "Continue" button shows up, no hints on what to do at all. I had to kill the process and start the installation again to make it work.

How to repeat:
Before installation, create the directory which will cause a path conflict, then open the installer and try to install the application which needs that directory.

Actually, this bug should be generalized to "UI buttons are missing during installation". After renaming the folder and restarting the installation, I made it further, but still ran into the same problem on a different "page". This time, during MySQL configuration, where it asks how much memory for MySQL to use. You can select any option you want, but there is no button to continue the process, so you get stuck on that page.

I am upgrading severity to Critical because this is a complete failure of the application, with no identifiable workaround other than to just download the "noinstall" zip.

Downgrading back to Serious severity because the application was actually installed, it's only the configuration process that couldn't be completed. Since there's a workaround to configure the application afterwards, this isn't a complete loss of service. So in the end, there are two workarounds one must make: the first is to make sure that no path conflicts exist prior to the installation process, and second, you must configure the applications manually since there are no UI buttons to guide the configuration process.

I disagree the downgrading to S2. It may install a new installation, but when I tried to upgrade from my 5.6.14.0 version, the bug means that the update did not occur.

... and additionally, I want to install a 32-bit instance alongside the 64-bit instance I have installed, so as to test a UDF I'll be writing against both versions.

Seems to me like 5.6.21.0 was a broken build. I haven't had any issues with 5.6.21.1.

Please try version 5.6.21.1. Thanks.

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".