Bug #74190 | Utilities 1.5 not recognized by Installer - Community | ||
---|---|---|---|
Submitted: | 2 Oct 2014 9:46 | Modified: | 19 Feb 2015 5:20 |
Reporter: | Gintas Grigelionis | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL for Windows: Installer | Severity: | S2 (Serious) |
Version: | 1.4.2.0 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[2 Oct 2014 9:46]
Gintas Grigelionis
[2 Oct 2014 10:56]
Peter Laursen
See also: http://bugs.mysql.com/bug.php?id=74070 As far as I rememebr, the Installer actually did handle MySQL Utilities on my environment (it installed version 1.4.4 according to the display in Control Panel .. Programs), but not the Notifier. -- Peter -- Not a MySQL/Oracle person
[2 Oct 2014 11:02]
Peter Laursen
OK .. this page http://dev.mysql.com/downloads/ lists the current version as 1.52. My instance of the MySQL Installer (installed with mysql-installer-community-5.7.5.0-m15.msi) also does not detect versions more recent than 1.44.
[2 Oct 2014 11:43]
MySQL Verification Team
Update options
Attachment: utilities_update.png (image/png, text), 112.73 KiB.
[2 Oct 2014 11:44]
MySQL Verification Team
Thank you for the bug report.
[3 Oct 2014 14:51]
Peter Laursen
It is there now (for me at lest)
Attachment: nowitistthere.jpg (image/jpeg, text), 68.67 KiB.
[3 Oct 2014 14:54]
Peter Laursen
... but it failed to install :-(
Attachment: installfal.jpg (image/jpeg, text), 59.22 KiB.
[3 Oct 2014 15:01]
Gintas Grigelionis
The catalog is updated now, but the Utilities are not recognized still; regedit finds no keys for Utilities in HKLM\Software, is this an installation/upgrade issue (I upgraded from 1.4.4 x86 to 1.5.2 x64)? There is another inconsistency, MySQL Server x64 created keys in HKLM\Software\Wow6432Node (albeit Installer handles it).
[3 Oct 2014 15:05]
Gintas Grigelionis
Trying to install from catalog
Attachment: installer.png (image/png, text), 34.10 KiB.
[3 Oct 2014 15:07]
Gintas Grigelionis
When I try to install Utilities from catalog, Installer recognizes that Utilities are installed and tells me I'm choosing the commercial version... but I run Installer - Community. Still problems with catalog update?
[3 Oct 2014 15:08]
Gintas Grigelionis
Oops, it's actually the other way around...
[3 Oct 2014 15:13]
Gintas Grigelionis
Well, I guess the problem is getting clearer: x64 version is commercial, community gets only x86...
[3 Oct 2014 15:16]
Peter Laursen
No matter what it should still upgrade sucessfully. I wonder if it is "fabric" that will not isntall on Windows?
[3 Oct 2014 15:21]
Gintas Grigelionis
I can install both x86 and x64 cleanly; x86 through the Installer, and x64 from msi downloaded from Community site. So I believe that the catalog is still incorrect. As to your problem, look at the installation details in the Installer; perhaps that would provide some clues.
[5 Oct 2014 12:30]
Peter Laursen
yes .. C++ Redistributable Package for Visual Studio 2013 was missing. Also see http://bugs.mysql.com/bug.php?id=74227
[5 Oct 2014 16:40]
Gintas Grigelionis
Good catch. So, to sum it up: Workbench 6.2.x and Utilities 1.5.x went 64-bit with C++ 2013 runtime. Whereas Workbench got updated in catalog and its msi checks for dependencies, Utilities are still not updated (for 64-bit version) in catalog and msi lacks dependency checks. I mentioned registry keys above; all MySQL components create keys in both HKLM and HKCU, except Utilities which store keys in HKCU only. How can Utilities/Fabric be user specific?
[29 Oct 2014 10:35]
Gintas Grigelionis
Would somebody please add an entry for "MySQL Fabric & Utilities" X64 architecture to catalog?
[13 Nov 2014 10:10]
Gintas Grigelionis
Would somebody please add an entry for "MySQL Fabric & Utilities" X64 architecture to catalog? 1.5.3 was added as X86 only.
[19 Feb 2015 5:20]
Philip Olson
Posted by developer: Fixed as of the upcoming MySQL Installer 1.4.4 release, and here's the changelog entry: The MySQL Installer manifest was missing 64-bit builds of the MySQL Utilities. Therefore, they were neither recognized nor installed. Thank you for the bug report.