Bug #60830 5.5.10 64bit >> 5.5.11 32bit 'upgrade' returns weird dialog
Submitted: 11 Apr 2011 12:31 Modified: 8 Dec 2016 11:49
Reporter: Peter Laursen (Basic Quality Contributor) Email Updates:
Status: Won't fix Impact on me:
None 
Category:MySQL Server: Installing Severity:S3 (Non-critical)
Version:5.5.11, 5.5.18 OS:Microsoft Windows (7/64)
Assigned to: CPU Architecture:Any
Tags: qc
Triage: Needs Triage: D3 (Medium)

[11 Apr 2011 12:31] Peter Laursen
Description:
By mistake I downloaded 5.5.11 32 bit and ran the installer.  5.5.10 64 bit was installed in advance. The installer opens a dialog that allows me to change features, repair or remove. 

How to repeat:
see above.

Suggested fix:
This dialog does not make sense here. It should eihter

1) either tell me that before a 32 bit can be installed the existing 64 bit must be remvoed
2) or allow for parallel installation of 32bit and 64bit of same major ('x.y') versions.
[11 Apr 2011 12:32] Peter Laursen
The dialog referred

Attachment: noupgrade.jpg (image/jpeg, text), 37.24 KiB.

[12 Apr 2011 6:57] Valeriy Kravchuk
Looks like you had some older 32-bit 5.5.x version on this machine before. When I tried to install 5.5.11 32-bit over 5.5.10 64-bit on XP where all 5.5s were always 64-bit, I had not got any dialog like yours, and installation process went as usual (Config. Wizard had not started at the end, bu this is another story). When I tried to run .msi for 32-bit 5.5.11 *again* I've got dialog like yours...

I was NOT able to install 64-bit 5.5.11 .msi after that (had to remove 32-bit 5.5.11 first), so I see a valid requests here for detection of "another bit" version and allowing for 32-bit and 64-bit versions to co-exist (as their basedirs are different).
[12 Apr 2011 8:10] Peter Laursen
You are right.  There is both a 32bit and 64 bit.  The 32 bit is not functional as there is no configuration file:

Microsoft Windows [version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Alle rettigheder forbeholdes.

C:\Users\Peter>cd \Program Files (x86)\MySQL\MySQL Server 5.5

C:\Program Files (x86)\MySQL\MySQL Server 5.5>dir
 Disken i drev C har ikke noget navn.
 Diskens serienummer er 40AF-D553

 Indhold af C:\Program Files (x86)\MySQL\MySQL Server 5.5

08-04-2011  22:02    <DIR>          .
08-04-2011  22:02    <DIR>          ..
08-04-2011  22:02    <DIR>          bin
08-04-2011  22:02    <DIR>          data
08-04-2011  22:02    <DIR>          include
08-04-2011  22:02    <DIR>          lib
31-03-2011  18:06             4.829 my-huge.ini
31-03-2011  18:06            20.238 my-innodb-heavy-4G.ini
31-03-2011  18:06             4.803 my-large.ini
31-03-2011  18:06             4.812 my-medium.ini
31-03-2011  18:06             2.921 my-small.ini
01-04-2010  17:58            13.128 my-template.ini
08-04-2011  22:02    <DIR>          share
               6 fil(er)           50.731 byte
               7 mappe(r)  36.445.372.416 byte ledig

C:\Program Files (x86)\MySQL\MySQL Server 5.5>cd \Program Files\MySQL\MySQL Serv
er 5.5

C:\Program Files\MySQL\MySQL Server 5.5>dir
 Disken i drev C har ikke noget navn.
 Diskens serienummer er 40AF-D553

 Indhold af C:\Program Files\MySQL\MySQL Server 5.5

15-03-2011  21:15    <DIR>          .
15-03-2011  21:15    <DIR>          ..
15-03-2011  21:15    <DIR>          bin
15-03-2011  21:15    <DIR>          data
15-03-2011  21:15    <DIR>          include
15-03-2011  21:15    <DIR>          lib
09-03-2011  17:45             4.829 my-huge.ini
09-03-2011  17:45            20.238 my-innodb-heavy-4G.ini
09-03-2011  17:45             4.803 my-large.ini
09-03-2011  17:45             4.812 my-medium.ini
09-03-2011  17:45             2.921 my-small.ini
01-04-2010  17:58            13.128 my-template.ini
16-02-2011  18:13             8.903 my.ini
15-03-2011  21:15    <DIR>          mysql-test
15-03-2011  21:15    <DIR>          scripts
15-03-2011  21:15    <DIR>          share
               7 fil(er)           59.634 byte
               9 mappe(r)  36.445.372.416 byte ledig

C:\Program Files\MySQL\MySQL Server 5.5>

.. but in Add/Remove programs in Control Panel only one 5.5 instance is listed and no service is registered for the 32 bit. 

So maybe the issue here is that you may (completely or not) install a n-bit version even when a m-bit version is installed. This should not be possible unless they get each their entry in Add/Remove.
[12 Apr 2011 8:11] Peter Laursen
Add/remove info

Attachment: mysql.jpg (image/jpeg, text), 24.95 KiB.

[12 Apr 2011 8:24] Peter Laursen
So it looks like I may have startet the installation of 5.5.11 32 bit 1-2 weeks ago. I have no memory about it, though.

Anyway now I have an inconsistent situation: 1) Windows *knows* that 5.5.11 32 bit is installed but not that 5.5.10 32 bit is. 2) The server that is actually running (.10 64 bit) cannot be handled from Windows Add/remove menu. This is probably not a big deal as I think that installing 5.5.11 (or higher) 64bit will repair this situation and the 32 bit folder can next simply be deleted.

However I do not want to install 5.5.11 now due to this: 
http://bugs.mysql.com/bug.php?id=60829 :-)

The conclusion I have reached now is that
1) either: a n-bit of a x.y version should refuse to install if a m-bit of same x.y version is installed
2) or: n-bit and m-bit should should identify themselves so that Windows can handle them in parallel. (not only 'MySQL Server 5.5" but "MySQL Server 5.5 - 64 bit" etc.)
[12 Apr 2011 10:39] Valeriy Kravchuk
Based on your last comment we have a clear and reasonable feature request here.
[13 Apr 2011 7:57] Peter Laursen
duplicate here:
http://bugs.mysql.com/bug.php?id=60823

(one more example that the situation where both a 32 bit and 64 bit is intalled cannot be handled gracefully)
[19 Nov 2011 16:29] Peter Laursen
Please consider this a real bug and not a 'feature request'!
Refer: http://bugs.mysql.com/bug.php?id=63328

Same software should not install as 32 bit and 64 bit simultaneously unless they identify themselves in such a way that they can be handled in parallel by the OS.
[8 Dec 2016 11:49] Yngve Svendsen
Posted by developer:
 
While this seems like a very real issue, Windows packaging has in the meantime been heavily revised, with the MySQL Installer for Windows replacing the old, plain MSIs. Weighing the risk and considerable effort of fixing the issue against the somewhat corner case nature of this report, I am thus closing this as Won't Fix.