MySQL Notifier Release Notes

Abstract

This document contains release notes for the changes in each release of MySQL Notifier.

For additional MySQL Notifier documentation, see MySQL Notifier.

Updates to these notes occur as new product features are added, so that everybody can follow the development process. If a recent version is listed here that you cannot find on the download page (http://dev.mysql.com/downloads/), the version has not yet been released.

The documentation included in source and binary distributions may not be fully up to date with respect to release note entries because integration of the documentation occurs at release build time. For the most up-to-date release notes, please refer to the online documentation instead.

For legal information, see the Legal Notices.

For help with using MySQL, please visit either the MySQL Forums or MySQL Mailing Lists, where you can discuss your issues with other MySQL users.

For additional documentation on MySQL products, including translations of the documentation into other languages, and downloadable versions in variety of formats, including HTML and PDF formats, see the MySQL Documentation Library.

Document generated on: 2016-08-17 (revision: 9605)

Preface and Legal Notices

This document contains release notes for the changes in each release of MySQL Notifier.

Legal Notices

Copyright © 1997, 2016, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

This documentation is NOT distributed under a GPL license. Use of this documentation is subject to the following terms:

You may create a printed copy of this documentation solely for your own personal use. Conversion to other formats is allowed as long as the actual content is not altered or edited in any way. You shall not publish or distribute this documentation in any form or on any media, except if you distribute the documentation in a manner similar to how Oracle disseminates it (that is, electronically for download on a Web site with the software) or on a CD-ROM or similar medium, provided however that the documentation is disseminated together with the software on the same medium. Any other use, such as any dissemination of printed copies or use of this documentation, in whole or in part, in another publication, requires the prior written consent from an authorized representative of Oracle. Oracle and/or its affiliates reserve any and all rights to this documentation not expressly granted above.

Changes in MySQL Notifier 1.1.7 (2016-08-01)

Functionality Added or Changed

Bugs Fixed

Functionality Added or Changed

The automatic migration of connections from MySQL Notifier to MySQL Workbench can now be delayed for a period of time or suspended indefinitely.

An option for setting the interval to ping monitored MySQL server instances for status changes was added to the Actions, Options menu.

Bugs Fixed

The Configure Instance option was renamed to Manage Instance. (Bug #24339668)

An error was displayed when valid domain user credentials were used to add a remote Windows service. (Bug #24305736)

Testing new connections for remote MySQL instances would display a “High Severity Error" message. (Bug #24010582)

When MySQL Notifier was installed using MySQL Installer, an exception was thrown and MySQL Notifier failed to start. (Bug #23762891)

The SQL Editor link to MySQL Workbench was disabled for each monitored MySQL instance or service when MySQL Workbench was installed. (Bug #23748734)

Validation checking identified domain\username as an invalid format to use when adding a remote Windows service to be monitored. Now, domain users with sufficient permissions to access the remote computer can connect using the domain\username format. (Bug #23746334)

The main XML element in %APPDATA%\Oracle\MySQL Notifier\settings.config was renamed to MySQLNotifier from MySQLForExcel. Indentations were added to improve the overall readability of configuration settings. (Bug #23740262)

Windows services on a remote computer were not retrieved and could not be added to the list services to be monitored. (Bug #23667056)

A corrupted connections.xml file caused MySQL Notifier to display a "Root element is missing" error message when started. (Bug #22160640, Bug #73540)

Attempts to subscribe to a remote Windows service for the first time failed and returned a “High Severity Error" message when the remote service was an instance of MySQL. (Bug #20389122, Bug #75319)

Case-sensitive naming prevented status changes to MySQL instances running as services for Windows. Now, service names for MySQL instances are added with compatible casing. (Bug #19881188, Bug #74516)

A "High Severity Error" raised by MySQL Notifier appeared intermittently during installations performed using MySQL Installer. (Bug #17825477)

Changes in MySQL Notifier 1.1.6 (2014-09-22)

Bugs Fixed

A "High Severity Error" was thrown when restarting Notifier if MySQL services/products had been removed while Notifier was not running. (Bug #19439604, Bug #73576)

A "High Severity Error" was thrown when a my.ini file for a monitored MySQL instance was deleted. (Bug #19422802, Bug #73539)

Available updates detected by MySQL Installer were not being communicated back to MySQL Notifier. Now, the Notifier correctly displays notifications for available updates. (Bug #19219905)

MySQL Notifier failed to start when a monitored service name contained the string "MySQL" since it was being treated as a MySQL server service. Now, the detection of MySQL services has been fixed to select real MySQL server services. (Bug #19078684, Bug #73135)

Removing MySQL Workbench's connections from within Workbench, or by deleting the MySQL Workbench connections.xml file, now removes those MySQL connections from the SQL editor sub menus of corresponding monitored services in MySQL Notifier. (Bug #18163378)

Selecting Actions, Check for updates, and then No, would throw a "High Severity Error". (Bug #17858917)

MySQL Notifier now handles fabric, fabric managed, and unknown connections, in the instances dialog. Fabric connections are not shown, "Fabric Managed" connections are shown in the Manage Instances dialog with "Type = Fabric Managed". MySQL Connections that do not use a native, SSH, socket, or fabric driver are treated as unknown and not shown.

Changes in MySQL Notifier 1.1.5 (2013-12-18)

This section documents all changes and bug fixes applied to MySQL Notifier since the release of 1.1.4.

Functionality Added or Changed

Bugs Fixed

Functionality Added or Changed

MySQL connections can now be edited from within MySQL Notifier, and no longer requires MySQL Workbench to be installed.

The MySQL Utilities can now be opened from MySQL Notifier.

Notifier now automatically detects when Workbench is installed or uninstalled, and starts or stops monitoring its files, depending, which no longer requires MySQL Notifier to be restarted.

Bugs Fixed

After executing Action, Manage Monitored items, Instance, and then Add MySQL Instance, clicking Cancel would generate an unexpected fatal error. (Bug #17697914)

MySQL Instances linked to workbench connections were not removed automatically when MySQL Workbench was uninstalled. (Bug #17671410)

A "High Severity Error" would be generated at startup if MySQL Installer attempted to install the MySQL Server and MySQL Notifier, and failed to install the MySQL Server. (Bug #17432516, Bug #70282)

On Windows XP, if the current user lacked credentials to schedule tasks, the MySQL Notifier startup task was not scheduled after it was installed. (Bug #14388579)

The SQL editor submenu did not automatically refresh when connections were added or removed outside of MySQL Notifier while it was running.

Reinstalling MySQL Workbench would cause duplicate connection entries to be listed in MySQL Notifier.

Installing a MySQL Notifier package when a previous version of MySQL Notifier was installed could corrupt the configuration file.

Changes in MySQL Notifier 1.1.4 (2013-07-09)

The first public release of the new 1.1 branch that offers remote monitoring.

Functionality Added or Changed

Bugs Fixed

Functionality Added or Changed

A Refresh Status action was added to the Actions menu. It manually refreshes the status of all monitored services (in both local and remote computers) and MySQL instances.

Bugs Fixed

MySQL Notifier would crash if a dead (bogus) MySQL Server service was registered, and discovered.

A workaround was to remove the dead service, such as "sc delete MySQL_BROKEN", and then restart MySQL Notifier. (Bug #16980502, Bug #14349610)

The MySQL Notifier service will now start itself immediately after being installed by the MySQL Installer. (Bug #16927045)

On Microsoft Windows 8, the autostart registry entry was not created properly, therefore the Notifier would not start after the user logged in. (Bug #16832752, Bug #69279)

MySQL Notifier would continue to run after it was uninstalled.

A workaround was to close MySQL Notifier before uninstalling it. (Bug #16661468)

Services that were manually added to MySQL Notifier would not be listed until after MySQL Notifier was restarted.

MySQL Notifier would not start after upgrading version 1.0.3 to 1.1.3.

A workaround was to delete the old 1.0.3 settings from the APPDATA folder before executing the upgrade.

Instance options edited from the Manage Instance Settings dialog were not saved. They are now written to settings.config.

Changes in MySQL Notifier 1.1.3 (Not released, Internal)

The third internal release of the 1.1 branch.

Bugs Fixed

The MySQL Notifier status tray icon was improved, in that the status colors (green, yellow, and red) are more noticeable. (Bug #14332309)

Changes in MySQL Notifier 1.1.2 (Not released, Internal)

The second internal release of the 1.1 branch.

Bugs Fixed

Sometimes the MySQL Notifier failed to automatically add MySQL services to the monitor even when the AutoAddServicesToMonitor option was enabled. (Bug #16660623, Bug #15887501, Bug #14345177, Bug #67617)

The MySQL Workbench SQL Editor link was visible even when the option was not available, and it would open the Home screen of MySQL Workbench. This link is now enabled if the available MySQL Workbench supports opening the SQL Editor from the command line, and if the bound service contains MySQL Workbench connections, otherwise the link is disabled. (Bug #14332402)

Changes in MySQL Notifier 1.1.1 (Not released, Internal)

The second internal release of the 1.1 branch.

Version 1.1.1 has no changelog entries, or they have not yet been published because the product version has not yet been released.

Changes in MySQL Notifier 1.1.0 (Not released, Internal)

The initial release of the 1.1 branch, an internal release.

This branch introduces monitoring services for remote Windows machines through Windows Management Instrumentation (WMI), and monitoring of MySQL Instances (multi-platform) via a configurable timer.

Functionality Added or Changed

Added the ability to monitor MySQL Instances (multi-platform) via a configurable timer.

Added monitoring services for remote Windows machines through Windows Management Instrumentation (WMI).

Changes in MySQL Notifier 1.0.3 (2012-07-25)

Initial public release of the MySQL Notifier.

Bugs Fixed

Changing the Use Colorful Icons option would not go into effect after option dialog window closed. (Bug #14357610)

On Microsoft Windows XP, installing the MySQL Notifier would not schedule the startup task. (Bug #14357592)

The MySQL Notifier failed to load if MySQL Workbench had not already been loaded at least once. This was due to how MySQL Workbench created a required directory. (Bug #14356442)

MySQL Notifier would not uninstall previous versions during installation. (Bug #14352140)

Filtering errors would result in full stack traces. Stack traces are not longer reported to the user. (Bug #14347636)

The error message windows were title as "MySQL Notifer" instead of "MySQL Notifier". (Bug #14347590)

A log file was added, and unhandled exceptions are now logged. The log file is located here: %APPDATA\Oracle\MySQL Notifier\MySQLNotifer.log (Bug #14343520)

The MySQL Notifier status could be incorrect if the MySQL Server was stopped and started without the Notifier. (Bug #14332357)

The Configure Instance option would open the Server Status section of MySQL Workbench but now loads the Administration window. Also, SQL Editor now opens the MySQL Workbench SQL editor. (Bug #14332346)

On Microsoft Windows XP, the Notification when service changes state option now works properly. (Bug #14332341)