MySQL Bugs: #78138: THE INSTALLER IS THROWING AN EXCEPTION WHEN IS DETECTING EXISTING PRODUCTS

Bug #78138	THE INSTALLER IS THROWING AN EXCEPTION WHEN IS DETECTING EXISTING PRODUCTS
Submitted:	19 Aug 2015 16:31	Modified:	21 Aug 2015 21:16
Reporter:	Javier Treviño	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL for Windows: Installer	Severity:	S1 (Critical)
Version:	1.4.10	OS:	Any
Assigned to:	Jose Gabriel Valencia Ornelas	CPU Architecture:	Any

Description:
When the MySQL Installer for Windows is loading, while checking the existing products installed an exception is thrown.

This is happening during the detection of Windows Firewall rules where ports for installed MySQL Servers are open. If there is any Windows Firewall rule without a port, the problem occurs.

How to repeat:
You need to have a working internet connection so the 1.4.10 upgrade can be applied

1. Install a MySQL Server or have at least one already installed
2. Apply the 1.4.10 update
3. Run the updated installer (1,4,10)
4. You will see a popup with the exception:

Internal error. (Object reference not set to an instance of an object.) The installer will now close.

Suggested fix:
Fix how the Windows Firewall detection for MySQL Server ports is implemented to handle rules without a port

The same issue in windows 7 x64.
MySQL Installer ask for update, then after the successfully downloaded the update an error will occur.

ERROR: Internal error. (Object reference not set to an instance of an object.) The installer will now close.

For now, I revert to v1.4.8 and disable automatic catalog update.

I am unable to find the installer for v1.4.9

The bug is fixed in 1.4.11

José,

You write "The bug is fixed in 1.4.11". How can I install this level if Installer is actually failing ?

Please try to run the Installer as normal, if it crashes before detecting there is a new Installer update you can download then you will need to download the update package:

http://cdn.mysql.com/Downloads/MySQLInstaller/mysql-installer-update-1.4.11.0-Community.ms...

Please update this bug if you need more information.

Fixed as of the upcoming MySQL Installer 1.4.11 release, and here's the
changelog entry:

When MySQL Installer 1.4.10 was checking for existing products installed on
the host, an exception was thrown during the Windows firewall detection phase if
Windows firewall rules were created without assigned ports after MySQL
server was installed.

Thank you for the bug report.

Follow-up on http://bugs.mysql.com/bug.php?id=78287:

I deleted all firewall rules created by the MySQL Installer revously and now the Installer starts and connects to the online Catalog.  I was even able to add new firewall rules linked to the mysql server binaries (and not the port as the rules created by the Installer did) and could still launch the Installer after that. Here the Installer (again) asked for permission to update itself (to 1.4.11.0 this time) 

BTW: I notice that MariaDB's installers create the firewall rule for the server binary and not for the port as Oracle/MySQL's Installer does (both rule definitions are possible with the Windows Firewall). What is better?

.. so in my experience what happened is quite the opposite of what Philip's release notes tell. 

The rules I had on my system created by MySQL installer did specify a port for the rule (but not a binary). Anyway - the rules may hav been created long ago with an old Installer version.

Thanks Peter for your comment, creating the Firewall rule referencing the binary is a good idea, so we will consider it for a future improvement.

http://bugs.mysql.com/bug.php?id=78444 marked as duplicate of this one.

Does anyone have a resolution to the error ?