MySQL Error 2015: Named Pipe Connection on Windows
Troubleshoot MySQL Error 2015 on Windows by checking named-pipe support, the pipe name, and client access permissions.
On this page
MySQL client Error 2015 (CR_NAMEDPIPE_CONNECTION) is raised when a Windows client cannot connect to MySQL through a named pipe. Named pipes are a local Windows transport; MySQL uses separate error codes for Unix socket and TCP/IP connection failures. See the MySQL 8.4 client error reference and connection options.
Confirm the client is using a named pipe
Test from the same Windows machine as the server:
mysql --protocol=PIPE --user=app_user --password
The client prompts for the password. The default pipe name is MySQL; when the server uses a different name, specify it with --socket=pipe_name. To test a separate TCP/IP connection, use --protocol=TCP --host=127.0.0.1 --port=3306. If TCP works while the pipe fails, focus on the server’s named-pipe setting, pipe name, and access controls.
Check whether the server allows named pipes
On Windows, the MySQL server’s named_pipe setting is OFF by default and requires a server restart to change. If named-pipe connections are required, an administrator can enable it in the server configuration:
[mysqld]
named_pipe
Restart the MySQL service after changing the option. If you can connect through another method, check the effective setting:
SHOW GLOBAL VARIABLES LIKE 'named_pipe';
If named pipes are not required, keep them disabled and use the working TCP/IP connection instead.
Check the named-pipe access group
Some older client software may require additional Windows group permissions to open the pipe. Check the server setting with an administrator:
SHOW GLOBAL VARIABLES LIKE 'named_pipe_full_access_group';
Its default is empty, which grants no Windows group full access. If a client requires full access, ask a Windows administrator to create a dedicated local group for the required client users and configure that group. Do not use *everyone* as a shortcut; keep membership limited. See MySQL’s named_pipe_full_access_group documentation.
Distinguish Error 2015 from other connection errors
- Error 2015 (
CR_NAMEDPIPE_CONNECTION): the Windows client could not connect through its named pipe. - Error 2002 (
CR_CONNECTION_ERROR): a local Unix socket connection failed; see MySQL Error 2002 troubleshooting. - Error 2003 (
CR_CONN_HOST_ERROR): the client could not connect to the specified host and TCP/IP port; see MySQL Error 2003 troubleshooting. - Error 2005 (
CR_UNKNOWN_HOST): the client could not resolve the server hostname; see MySQL Error 2005 troubleshooting.
For other connection, authentication, and SQL failures, browse the MySQL error troubleshooting index.