Bug #50830 MySQL Workbench cannot connect to MySQL when only named pipe is enabled

Submitted: 2 Feb 2010 13:02 Modified: 17 Feb 2010 17:55
Reporter: Franklin Tse Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S2 (Serious)
Version:5.2.15 OS:Windows
Assigned to: Mike Lischke CPU Architecture:Any
Tags: MySQL Workbench, named pipe, windows

[2 Feb 2010 13:02] Franklin Tse 
Description:
When TCP/IP is disabled (using skip-networking) and Named Pipe is enabled (enable-named-pipes), MySQL Workbench cannot connect MySQL and says "Can't connect to MySQL server on 'localhost' (10061)".

The MySQL is working because it can be connected via "mysql -W -u root -p" command.

How to repeat:
1. Set the MySQL server to use Named Pipe only
2. Create a new server instance in MySQL Workbench, with socket/pipe selected as connection type
3. Try to connect to the MySQL server

Suggested fix:
Support Named Pipe
[2 Feb 2010 19:28] MySQL Verification Team 
Thank you for the bug report.
[10 Feb 2010 14:24] Mike Lischke 
Fixed in 5.2
[12 Feb 2010 22:44] Johannes Taxacher 
fixed in repository
[15 Feb 2010 11:41] Tony Bedford 
An entry has been added to the 5.2.16 changelog:

If a MySQL server was set to accept named pipe connections only, and then a server instance created in MySQL Workbench using a named pipe connection, it was not possible to subsequently connect to the server with MySQL Workbench.
[17 Feb 2010 17:55] Franklin Tse 
Confirmed fixed in 5.2.16. Thanks!

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.075 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.