MySQL Bugs: #5293: Error starting Tray Monitor after configuring Service using MySQL Administrator

Bug #5293	Error starting Tray Monitor after configuring Service using MySQL Administrator
Submitted:	30 Aug 2004 14:03	Modified:	30 Sep 2004 22:07
Reporter:	Symon Rottem	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Administrator	Severity:	S2 (Serious)
Version:	1.0.11	OS:	Windows (Windows XP Professional (SP1))
Assigned to:	Assigned Account	CPU Architecture:	Any

Description:
When mysqld is installed using "mysqld --install" or "mysqld --install-manual" and the Tray Monitor application is run it will display the status of the mysql service that was installed as expected.

If the MySQL Administrator application is used to configure the service instance in any way (ie. change the "Launch MySQL server automatically" from true to false or vice versa) and the changes are applied then the next time the Tray Monitor is started a modal critical error dialog appears stating:

"Access violation at address 77FA4032 in module ntdll.dll.  Write of address 00404F46"

After the dialog is dismissed the tray monitor is no longer displaying service status and the context menu does not operate as expected.

Closing the tray montor, then executing "mysqld --remove" and then executing "mysqld --install" to resinstall the service will return the Tray Monitor to working order.

How to repeat:
1. Fresh install of MySQL on Windows
2. Execute "mysqld --console" to initialize database.
3. Execute "mysqld --install" or "mysqld --install-manual" to install the service.
4. Run the MySQL Tray monitor
5. Open Tray Monitor context menu and select configure instance.
6. When MySQL Administrator opens select the Configure Service tab.
7. Check or uncheck the "Launch MySQL server automatically" or change one of the Server Features checkboxes.
8. Apply Changes.
9. Close MySQL Administrator
10. Close MySQL Tray Monitor
11. Restart Tray Monitor to see the error dialog.

Thanks for reporting. Could you start the Registration Editor and check the following key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\YOURSERVICENAME

Then, please paste the value of ImagePath here when the Monitor doesn't work as expected.

That would help a lot fixing the bug. I expect a corrupted registry entry.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".