Bug #26999 Access violation when adding a redundant instance
Submitted: 9 Mar 2007 14:20 Modified: 19 May 2009 13:01
Reporter: Clifton Kilby III Email Updates:
Status: Closed Impact on me:
Category:MySQL Administrator Severity:S3 (Non-critical)
Version:1.2.10 OS:Windows (Windows XP SP2 Pro)
Assigned to: CPU Architecture:Any

[9 Mar 2007 14:20] Clifton Kilby III
When using the MySQL System Tray Monitor to Manage Instances, if you attempt to add a new instance with a name that is already in use, it will fail. Clicking on the installed instance then causes an Access Violation. Happened with MySQL nt 5.0.18(build from MySQL), and MySQL nt 5.0.33 built locally.
May be related to #26729.

How to repeat:
with an existing mysql-nt instance
stop instance
start MySQL Administrator in instance mode
right click in the bottom left... install new service
name it the same as an existing mysql service
enter a valid ini path
enter a valid exe path (to mysqld in this case)
hit apply (fails due to naming conflict)
click on the first Mysql service on the right
Access violation, and will not terminate

Suggested fix:
I do not have the skills needed to track down such a bug, let alone propose a fix. Perhaps adding a new instance name conflict check would assist, though it would not actually remove the bug.
[9 Mar 2007 15:27] MySQL Verification Team
Thank you for the bug report.
[19 May 2009 13:01] Susanne Ebrecht
Thank you for your bug report. This issue has already been fixed in the latest released version of that product, which you can download at