Bug #70408 | Mysql installer: convert to commercial license | ||
---|---|---|---|
Submitted: | 24 Sep 2013 15:24 | Modified: | 25 Feb 2014 17:48 |
Reporter: | Michael B | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL for Windows: Installer | Severity: | S3 (Non-critical) |
Version: | 5.6.14 | OS: | Windows |
Assigned to: | CPU Architecture: | Any |
[24 Sep 2013 15:24]
Michael B
[24 Sep 2013 16:46]
MySQL Verification Team
Thank you for the bug report.
[25 Sep 2013 7:59]
Peter Laursen
I have reported another 'flavor' of this bug: http://bugs.mysql.com/bug.php?id=70387
[25 Sep 2013 8:37]
Michael B
My assumption is that the Mysql Installer detects any Mysql Community Edition minor version larger then the minor version it can download itself as a Non GPL version. The Mysql installer has the following minor versions on offer in it's Product Catalog (in mysql-installer-web-community-5.6.14.0.msi): 5.6.14 5.5.33 5.1.70 5.7.1 This seems to coincide with your experience Peter Laursen. Before it gets to the product catalog it seems to check the internet for the latest versions. I think if these are updated to the correct latest versions that the Installer will work again (short term solution). Long term would be a better check if something is community or commercial in the installer.
[4 Dec 2013 15:08]
MySQL Verification Team
http://bugs.mysql.com/bug.php?id=71065 duplicate of this one.
[14 Dec 2013 18:55]
Christian Benner
Would be nice to have any helpful hints how to update with the installer?! What should we do now? "Thanks for the Bug Report" isn't enough (not for this Long period of time without any helpful answer). Thats boring. Sorry...
[14 Dec 2013 19:52]
Peter Laursen
What shalll we do now?" Forget about the installer. 1) Download .zip package 2) unzip to where you wnat it 3) navigate ("cd" ...") to the ../../bin folder 4) Open command line and install MySQL as a service with the command "mysqld --install servicename" 5) start service "net start servicename" and/or set properite sfor the service in Control Panel .. administration .. services. I have don e myself with MySQL 5.6.15 and 5.7.3. I have gone completely nuts with the "MySQL installer" and do not want to waste a minute more with this horrible crap.
[14 Dec 2013 20:01]
Peter Laursen
I intended to post a link to documentation, but I missed it. Here it comes: http://dev.mysql.com/doc/refman/5.6/en/windows-install-archive.html (but this documentation paragraph is expremely poor quality writing unfortunately. It is much simpler actualy than what impression you get from it.)
[19 Dec 2013 12:02]
Christian Benner
Hi Peter, thats not the solution for the installer Problem. My question was "how to do it WITH installer". Your fix is nice for home users and/or simple one man Show installations but not für SCM Installation on more than 100 Hosts :-) But it's blaming to see how Oracle answers this Problem ;-)
[19 Dec 2013 13:16]
Michael B
I think I came across the (xml) configuration file that is most likely used for the checks/upgrades. Maybe some manual editing in the file could make the the error go away (in particular setting the version of 5.5.33 to 5.5.34). I'm not in the position to test this, maybe someone else is? The file: C:\programdata\mysql\mysql installer\products.xml
[19 Dec 2013 13:33]
Christian Benner
Hello Michael, you're very close but better to take a look into the product.xml But that't not what customers (users) should do - it's on Oracle to help and let users know how they can fix it. (the latest "update" was taking some mistakes in writing back those files. Best regards Chris
[19 Dec 2013 13:34]
Christian Benner
Hello again, sorry meant config.xml and not product.xml .... sh Best regards Chris
[19 Dec 2013 13:53]
Peter Laursen
That is interesting indeed! In C:\ProgramData\mysql\MySQL Installer\config.xml I have this <ProductCode>{45588729-7E5F-4862-AEA6-CE844D03F593}</ProductCode> <ActiveCatalog>mysql-5.5-winx64-commercial</ActiveCatalog> <MaxLogCount>100</MaxLogCount> <Commercial>true</Commercial> .. but how it came there, I have no clue. I *ABSOLUTELY NEVER* installed any commercial software from Oracle. I never had any access to it, simply. Besides I also have <SendSystemInfo>1</SendSystemInfo> .. and I don't recall I ever agreed to that! I have now unistalled the "MySQL Installer". Currently I have 5.1.71, 5.5.35 5.6.15 and 5.7.3 servers installed. The two first of them with 'stand-alone' installed and the two latter with "mysqld .." command. So this must be a relic from long time ago when I installed a 5.5 build with the (integrated and buggy) "MySQL Installer" (probably when the first version of it was released). Why don't Oracle just tell us to delete or edit this file if that is the problem? Or to uninstall the "MySQL Installer" so that a fresh and better version is installed next time you install. The silence from Oracle here is *deafening*
[19 Dec 2013 14:00]
Christian Benner
Should be <ProductCode>{88359D24-F64F-477E-B080-50FB024BA6F7}</ProductCode> <ActiveCatalog>mysql-5.6-winx64</ActiveCatalog> But they have no glue what they're doin'. Take a look at the .NET connector problem. Someone (without thinking a little bit about the result) removed the Visual Studio checkings. No VS2013 users are able to use it - sind 6.8.1 Beta (and now 6.8.2rc)it's working but over an half year to late!!! Same on installer here, Oracle is sitting on their nuts and nothing happens.. Thats not the right way to work with users/customers. (And that's also the reason we've changed from MySQL to MariaDB now) They're working OPEN !!! and faster ('til now).
[19 Dec 2013 14:02]
Christian Benner
sorry, it's me again 'cause htting to fast my "submit" button here ;-) It's also not assigned to somebody... So I think this thread is unread by Oracle ;-)
[19 Dec 2013 14:04]
Peter Laursen
+ MariaDB installers work like a charm!
[25 Feb 2014 17:48]
Philip Olson
Fixed as of the upcoming MySQL Installer 1.3.6 release, and here's the changelog entry: The license conversion process was improved. This process converts MySQL product licenses from Commercial to Community, or Community to Commercial. Also, a product was designated as having a different license if the installed product version was newer than the version known by the Installer. Thank you for the bug report.