Support

This is a problem with WAMPServer on your computer. It told you so when you run its self_test:

===== Tested by command netstat filtered on port 3306 =====

 

Test for TCP
Your port 3306 is used by a processus with PID = 6304
The processus of PID 6304 is 'mysqld.exe' Session: Services
The service of PID 6304 for 'mysqld.exe' is 'N/D'
*** WARNING *** This service does not seem from Wampserver
Should be: 'wampmysqld64' or 'wampmariadb64'

Test for TCPv6
Your port 3306 is used by a processus with PID = 6304
The processus of PID 6304 is 'mysqld.exe' Session: Services
The service of PID 6304 for 'mysqld.exe' is 'N/D'
*** WARNING *** This service does not seem from Wampserver
Should be: 'wampmysqld64' or 'wampmariadb64'

Unfortunately I cannot help you with setting up a local server environment. I can try to point you to the right direction. You can't have multiple servers trying to use the same port on your computer to start the MySQL server; only one will success and the others will fail — this is what happened.

If you have installed other local web server environments, other than WAMPServer, such as XAMPP please uninstall them. If you have installed MySQL manually, please uninstall it.

Beyond that you can post to WAMPServer's community support forum (http://forum.wampserver.com/list.php?1). Make sure to include the test results you gave me. They should be able to help you identify what is going on with your computer and fix it.

Side note: I have not used a pre-packaged local web server in well over a decade. I am usually on a Mac but when I use Windows I use my custom IIS local server build as I documented a couple of years ago in my personal blog. As a result I don't know how to help you with WAMPServer, I can only infer based on the information I read on your message that the problem is that there's another service running on TCP/IP port 3306 with the name "N/D" instead of WAMPServer's expected  'wampmysqld64' or 'wampmariadb64'. I would assume that if you press WIN-R, type services.msc and press ENTER to get to the services manager on your computer you will find a service named 'N/D' and a service named 'wampmysqld64' or 'wampmariadb64'. If you disable the first and start the latter the problem will fix itself. This is based on my knowledge of how Windows services work and inferring from the test results shared with me; I won't claim it's 100% accurate as I cannot test it myself :)