Can & #39; t open named pipe to host:. pipe: MySQL, namedpipe

Can't open named pipe to host:. pipe: MySQL, namedpipe
The following error is reported when mysql is connected to odbc: Can't open named pipe to host:. pipe: MySQL:

According to the methods mentioned on the Internet, the official mysql statement did not work. The final solution is to delete the old odbc connection and create a new one with the same name. Solve the problem.
This problem is caused by a new odbc driver installed by a colleague.
With the previous blog address to help me solve the problem: http://blog.csdn.net/virus1992/article/details/8681839

Mysql-Front cannot connect to the database

Mysql-front is a graphical tool for managing mysql, allowing you to conveniently operate databases.

Can't open named pipe Error
If you use the Mysql-Win32 shared software version on NT, with the latest Mysql client, you will get the following error:
Error 2017: can't open named pipe to host:. pipe...

This is because the named pipe is used by default in the Mysql official version of NT. You can avoid this error by using the -- host = localhost option for new Mysql customers or creating a file "C: my. cnf" containing the following information:

[Client]
Host = localhost

#2003-Can't connect to MySQL server on 'localhost' (10061) report this error in win7. Is there a solution,

When you connect to the MySQL remote host through TCP/IP, ERROR 2013 (HY000): Lost connection to MySQL server at 'reading initial communication packet ', system error: 104 appears.

If you directly run the mysql command in the linux shell Command Line and can smoothly connect to MySQL, the query statement execution is also normal, but if you execute the stop slave command; the ERROR 2013 (HY000): Lost connection to MySQL server during query problem occurs randomly. If you write the operation command to the script file and then execute the script file, Lost connection to MySQL server at 'reading initial communication packet ', system error: 111 will inevitably occur.

If a remote access error occurs in any way, it can be considered that the system has limits such as firewalls, but such strange cramps are puzzling. The final solution is to add a startup parameter in the [mysqld] section of my. cnf.

Skip-name-resolve

The problem disappears. However, the reason is still unknown.

If it is helpful to you, please remember to adopt a satisfactory answer. Thank you! Wish you a happy life!

Vaela