Bug #22572 Administrator crashes on opening against local when named pipes is not enabled
Submitted: 21 Sep 2006 22:25 Modified: 22 Sep 2006 7:43
Reporter: Simeon Theobald Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Administrator Severity:S3 (Non-critical)
Version:5.0r3 OS:Windows (XP Pro 2002 SP1)
Assigned to: CPU Architecture:Any

[21 Sep 2006 22:25] Simeon Theobald
Description:
Administrator crashes on opening against localhost or 127.0.0.1 when named pipes is not enabled (Default).

MySQLQueryBrowser works fine with the same saved connection.

Versions: MySQL5.0.24, MySQL GUI Tools 5.0 r3 
Both installed using the NOInstall zip files. 

The failure is trapped by the OS, and a generic "Administator for MySQL Servers has encountered a problem and needs to close. We are sorry for the inconvenience." error message is provided. This does not help to diagnose or resolve the problem.

How to repeat:
- Install above versions of MySQL and GUI tools using the NoInstall zip files.
- Start MySQL engine as a service,
- Start MySQLQueryBrowser and connect to localhost, or 127.0.0.1 as root (this will work, and proves that the engine is running properly
- Start MySQLAdministrator, connect using same details as used in QueryBrowser (this will cause MySQLAdministrator to crash, and windows will provide a generic error message)

Suggested fix:
Work around:
- With MySQL running, start the MySQLSystemTrayMonitor.exe 
- Right click on the tray icon, and choose actions / manage MySQL Instances 
- Under 'Service Control', on the 'Configure Service' tab, tick the 'Named Pipes' checkbox. 

Now try MySQL Administrator again. It 'should' startup with no problems. 

Perhaps the developers could look at trapping this error, and presenting an error message containing a clue as to where the problem is? Letting the OS provide a non-specific error is not helpful! 

Technically, this is not a bug, as it is 'recommended' to use named pipes when connecting to localhost (although the default is to leave named pipes disabled), but the absence of a useful error message causes this to be a problem to the un-initiated.
[22 Sep 2006 7:43] Sveta Smirnova
Thank you for the report.

This bug duplicates bug #22380. So I mark this as "Duplicate" and will add to bug #22380 note with link to your description of the problem. Please, add your new comments to the original bug.