MySQL Bugs: #56889: MySQL 5.6 installed on system prevents upgrading MySQL 5.5

Bug #56889	MySQL 5.6 installed on system prevents upgrading MySQL 5.5
Submitted:	21 Sep 2010 7:38	Modified:	9 Jan 2015 16:35
Reporter:	Peter Laursen (Basic Quality Contributor)	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Server: Installing	Severity:	S3 (Non-critical)
Version:	5.6.0, 5.6.2	OS:	Windows (7 64bit)
Assigned to:		CPU Architecture:	Any
Tags:	qc

Description:
When I try to upgrade from 5.5.5 to 5.5.6 I get a message that 'a later version' is already installed. I will put up an image.

File/installer  is "mysql-5.5.6-rc-winx64.msi" from 
ftp://mirrors.dotsrc.org/mysql/Downloads/MySQL-5.5/ downloaded around 16 hours ago.

How to repeat:
I have told! :-)

Suggested fix:
I know I can uninstall 5.5.5 but it is inconvenient.  So please provide a new 5.5.6 package if possible (if it is a problem with the existing 5.5.5 then I realize that you probably cannot).

Installer exits with this message

Attachment: later.jpg (image/jpeg, text), 41.95 KiB.

Let me add - if it matters - that I also have server version "5.6.0-m4" installed.

It appeared here
ftp://mirrors.dotsrc.org/mysql/Downloads/MySQL-5.6/
.. for a few days (maybe a week) after what the folder on the FTP-server was emptied.

If uninstalling "5.6.0-m4" will do the trick it is OK - not at least if the "5.6.0-m4" was a mistake from the beginning and this tree will not be continued.  In that case please confirm.

I can upgrade freshly installed 5.5.5 to 5.5.6, using both packages from ftp://mirrors.dotsrc.org/mysql/Downloads/MySQL-5.5/

No 5.6 installed

hmmm .. looks then like the 5.5.6 installer *thinks* that 5.6.0 is a higher 5.5.x than what 5.5.5 is.

correction:

.. the 5.5.6 installer *thinks* that 5.6.0 is a higher 5.5.x than what 5.5.6 is.

Uninstalling 5.6.0-m4 should do the trick. This tree will not continue, and the release should not have happened, trunk will continue as 5.6.1(+).

As for how 5.6.0 was built I do not know, there should have been a WiX error that prevents building a package if patch number is 0 (like in this case).
Perhaps, it was fixed by quick engineering during release (and that could allow things like 5.6.0 is later 5.5).

I fixed the error mentioned (irregularities with patch == 0) in trunk right now, so it should be fine next time (i.e with 5.7.0 or whatever release will have 0 as third version number)

Closing the bug for now. Please feel free to reopen, if something is unclear.

Yes .. it works fine after uninstalling 5.6.0

hmmm .. I was not able to start the service after upgrading.  I had to completely remove 5.5 from uninstall menu + delete installation folder.

I tried with both my old my.ini (bypassing the configuration wizard) as well trying to let the configuration wizard rewrite configuration. The old my.ini was generated by the wizard of an earlier versions (likely 5.5.3 or 5.5.4)

I have my old data folder and it is working with the new server so everything is OK. 

Set to back 'open' in order to assure that you see this. I don't require more 'service' here so you can take it from here as you want. If you want I may be able to 'fish' the old my.ini and its backups from the Recycle Bin.

config files - the oldest is my original - the others generated by wizard

Attachment: my.zip (application/zip, text), 10.68 KiB.

I came across this Blog: http://www.chriscalender.com/?p=140

.. so maybe taht wey why I could not make the upgraded instance start?  As i started as a service (adn have deleted everything from 5.5.5 except data) unfortunately I cannot help debugging/confirming this.

Thank you for the feedback.

Please try to install current version 5.5.8 and if you still can not start mysqld provide full error log file.

@Sveta .. you don't get the point here!  

The problem was that 5.6.0 (what is now no longer available as a binary download - it was removed) prevented upgrading from 5.5.n to 5.5.n+1.  Uninstalling 5.6.0 solved the issue. 5.5.n+1 *thought* that 5.6.0 was a higher 5.5.x (and not a completely different branch) and thus refused to install.

I think Vladimir explained that this was a bug in the 5.6.0 .msi installer script. Only after 5.6.1 release (as a .msi installer) I can verify that it is fixed.  Before it is not possible for me.  But you can close if you know that the .msi script in 5.6 trunk now fixes the problem.

Sorry .. his name is Vladislav and not Vladimir!

Since this is/was really a bug with the 5.6/5.6.0 installer and not 5.5 I changed version and updated synopsis accordingly.

I hae now installed 5.6.2.  Waiting for the next 5.5.x release where http://bugs.mysql.com/bug.php?id=60829 is fixed (or at least properly documented), so that I can verify that this is fixed in 5.6 tree.

I've seen this problem with 5.6.2 on Windows XP. Installation prevented upgrade to 5.5.11. I had to uninstall 5.6.2 first.

This is still an issue (having 5.6.3 installed and trying to upgrade 5.5.16 >> 5.5.17).

Could somebody please fix this stupied bug?

http://bugs.mysql.com/bug.php?id=63708 is a duplicate.

No, it is not a duplicate.

@wlad .. why not?

This one is specifically about upgrading 5.5.x to 5.5.y (y > x) while 5.6.z is installed. 
It was a bug in MSI major upgrade condition, I might even have fixed it while still at Oracle, I do not recall.

Another one is something about the new unified installer, which is a .NET application not an MSI.

This one is specifically about upgrading 5.5.x to 5.5.y (y > x) while 5.6.z is installed. 
It was a bug in MSI major upgrade condition, I might even have fixed it while still at Oracle, I do not recall.

Another one is something about the new unified installer, which is a .NET application not an MSI.

@wlad .. you did not fix it with the 'standalone' .msi (even though you told once before - just before you left Oracle - that you did). If you fixed anything it failed to work properly because it still does not.  See Valeriy's comment above. He faced the same problem. And if I run *either* of the 5.5.19 installers with 5.6.3 installed I still get the same problem ("a more recent ..[of same] .. is already installed" and the installer(s) abort).

Ok , if you think it is the same problem, so be it. You know it better:)

This was the fix that indeed got lost somewhere. The effect is that 5.5 upgrade proceeds even if 5.6 is installed. It  does not fix the "duplicate".

=== modified file 'packaging/WiX/mysql_server.wxs.in'
--- packaging/WiX/mysql_server.wxs.in   2011-06-30 15:46:53 +0000
+++ packaging/WiX/mysql_server.wxs.in   2011-12-11 19:57:29 +0000
@@ -49,6 +49,7 @@
         />
       <UpgradeVersion
         Minimum="@MAJOR_VERSION@.@MINOR_VERSION@.@PATCH_VERSION@"
+        Maximum="@MAJOR_VERSION@.@MINOR_VERSION@.999"
         OnlyDetect="yes"
         Property="NEWERVERSIONDETECTED" />
     </Upgrade>

@wlad .. I am not so sure now.  Not after your comments.  I realize that you were involved a lot in the 'standalone' installers till around 1 year ago. I only notice that I get exactly the same error with both installers when upgrading a 5.5 server on a system where also 5.6 is installed.

But let the MySQL people sort this out (if they care).

also see http://bugs.mysql.com/bug.php?id=64909