MySQL Bugs: #73135: MySQL Notifier opens and gives an error message "High Severity Error"

Bug #73135	MySQL Notifier opens and gives an error message "High Severity Error"
Submitted:	27 Jun 2014 13:01	Modified:	28 Aug 2014 5:38
Reporter:	Vesko Jl	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL for Windows: MySQL Notifier	Severity:	S3 (Non-critical)
Version:	1.1.5	OS:	Windows (Windows 7 x64)
Assigned to:		CPU Architecture:	Any
Tags:	mysql notifier start failed

Description:
In brief, the problem is that MySQL notifier fails to start on Windows 7.
This bug is a duplicate of http://bugs.mysql.com/bug.php?id=70282 ,which has been closed as fixed, but now I'm getting the same issue with the newest "fixed" version 1.1.5 of the notifier.

In my case the reason notifier refused to start was another MySQL service (BMFMySQL), installed silently from another product: Toad Benchmark Factory for Databases. So I've uninstalled the Toad product and then MySQL notifier started normally. 

I'm not sure how the notifier should behave when multiple MySQL services are running, but for me this is an abnormal behavior.

How to repeat:
Install some old version of "Toad Benchmark Factory for Databases" (seems like the latest one doesn't use MySQL as a back-end) or any other product that installs a MySQL as a service, then install the MySQL 5.6.17 package, which comes with Notifier 1.1.5 and the notifier will fail to start.

Error Message

Attachment: 00000_severity_error.png (image/png, text), 50.89 KiB.

Thank you for the bug report. I have several services one with setup
with installer and others 4 installed manually. See prior attached picture
for error.

Posted by developer:
 
I was unable to reproduce the above mentioned High Severity Error. 
Notifier is able to work with multiple Local MySQL Services (e.g. if you have 3 different instances of MySQL installed, running on different ports, say 5.5:3306, 5.6:3307 and 5.7:3308; Notifier adds them to its list automatically and monitors them simultaneously). However I did noticed new services added into the system were automatically included to the notification list if they contained the filter name ("mysql" by default on settings) without validating if the services was truly MySQL related (Something that became evident with the test case explained in the description of the bug).
I've added further validation to ensure only true MySQL services are added to the watched list.

Fixed as of the upcoming MySQL Notifier 1.1.6 release, and here's the changelog entry:

Sometimes MySQL Notifier would fail to start when working with multiple MySQL
services (including third-party services) that used different ports.

Thank you for the bug report.