MySQL Notifier Release Notes  /  Changes in MySQL Notifier 1.1.4 (2013-07-09)

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

  • 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.