MySQL Bugs: #72343: MySQL Installer does not always 'Configure' / run mysql

Bug #72343	MySQL Installer does not always 'Configure' / run mysql_upgrade on Win32
Submitted:	14 Apr 2014 14:23	Modified:	13 Jan 2015 8:58
Reporter:	Christopher Hill	Email Updates:
Status:	Unsupported	Impact on me:	None
Category:	MySQL for Windows: Installer	Severity:	S2 (Serious)
Version:	5.6.17	OS:	Windows
Assigned to:		CPU Architecture:	Any

Description:
I have two instances of MySQL installed, one on a Windows Server 2003 R2 SP2 (x86) physical machine, and one on a Windows Server 2008 R2 SP1 (x64) virtual machine.

When upgrading MySQL on both of these machines using MySQL Installer's 'Check for Updates' option, I have found that the Server 2008 R2 (x64) virtual machine consistently prompts to 'Configure' the instance and runs mysql_upgrade.exe automatically after the upgrade - however, the Server 2003 R2 (x86) machine does not (it simply says that there are no instances to configure).

I have documented the installation process for these two machines and there are only two possible differences:

1) One is 2003 R2, a 32-bit operating system, and the other is 2008 R2, a 64-bit operating system...

2) The 2003 R2 (x86) machine is running with a custom 'Data Path' set in the installer options (D:\MySQL\MySQL Server 5.6\), and the 2008 R2 (x64) machine is running with the default 'Data Path' set (C:\ProgramData\MySQL\MySQL Server 5.6\).

I am not sure which of these is causing the problem (or if it is something else entirely) but it would be good if someone could work out why the 2003 machine consistently refuses to automatically run the 'Configure' process, and hence has to have mysql_upgrade -p run manually in order for the upgrade process to work properly.

How to repeat:
Install an old version of MySQL (5.6.16)

Attempt an upgrade to 5.6.17 (using MySQL Installer)

The Configure process will not run - mysql_upgrade has to be run manually

Thank you for the bug report. Notice that 2003 server isn't more supported OS for
5.6:

http://www.mysql.com/support/supportedplatforms/database.html

Thanks.

Done some testing and it seems as if the problem is due to a non-default data path anyway, rather than Server 2003 / 32bit issue.

Steps to repro:

Run mysql-installer-community-5.6.15.0.msi
 (License Agreement: Accept EULA)
 SKIP the 'Find latest products' check (to allow subsequent upgrade)
 Setup Type: Server only
  Data Path: D:\MySQL\MySQL Server 5.6\
 (Check Requirements - should not be any)
 (Allow installation to take place)

Run MySQL Installer (from Start Menu)
 Click 'Check for Updates'

Done some testing and it seems as if the problem is due to a non-default data path anyway, rather than Server 2003 / 32bit issue.

Steps to repro:

Run mysql-installer-community-5.6.15.0.msi
 (License Agreement: Accept EULA)
 SKIP the 'Find latest products' check (to allow subsequent upgrade)
 Setup Type: Server only
  Data Path: D:\MySQL\MySQL Server 5.6\
 (Check Requirements - should not be any)
 (Allow installation to take place)

Run MySQL Installer (from Start Menu)
 Click 'Check for Updates'
 (Should detect 5.6.17 as available update)
 (Installation screen - should install fine)
 Configuration screen - 'The following products will now be configured' table is empty

Expected results: 'The following products will now be configured' table should include the MySQL instance.

Hope this helps!

Thank you for the feedback. Looks related to http://bugs.mysql.com/bug.php?id=72200 too.

Would agree. The MySQL installer needs to handle custom installation / data directories better (since it actually offers these settings as part of the standard installation UI).

Thank you for the feedback.