Wamp Server

[paul-holmes83]

Does anybody know how to configure Wamp server running on Vista and using firefox.

I cannot access PHPmyAdmin.

When I first installed it when I tried to go to PHPmyAdmin I just got a blank white page, after some digging around on the internet I found that my Hosts file needed to have 127.0.0.1 localhost added.

After I added the above line I now get an error page as below.

Welcome to phpMyAdmin

Error

MySQL said: Documentation
#2002 - The server is not responding (or the local MySQL server's socket is not correctly configured)

I have not been able to find any info on this.

Not sure if it makes a difference but I keep my hosts file as read only.

[essellar]

Make sure you don't have any other web servers running locally (so no using WampServer while trying to test ASP.NET development locally using IIS) and that MySQL is listed as allowed for local access in whatever firewall software you're using (you'll probably need to be an admin to make the change if you usually run as a restricted user). The default MySQL port is 3306.

[paul-holmes83]

I have looked at the services and I do not see either ASP.NET or IIS in the list so I don't think it is them.

I see Mysql.exe listed in the allowed aplications of my firewall, it says any local port and any remote port, I use Bullgaurd if that makes a difference.

[essellar]

Odd, that -- WampServer has always been plug-and-play for me. It comes properly configured out of the box (usually). Is MySQL running when you start the server (check your task list)?

[paul-holmes83]

It appears to be I see in the services section of task manager

wampapache (pid5972) running
wampmysqld (pid5160) running

A suggestion made in the wampserver forum said that the hosts file should contain only the line
127.0.0.1 localhost

mine included some other lines so I made a copy then I deleted all lines except the above.

I have a spare PC here that just needs an HD and a mouse, I think I will rebuild that and try it on that one, only problem there is I have no spare space on my router

[misson]

One tool that may help is TCPView, which you can use to see which programs have what ports opened.

Check the connection settings in the MySQL and PHP configuration files to see what ports or named pipe each uses, and make sure they are the same. With PHP, you can use phpinfo instead of checking php.ini; XAMPP should make it available at http://localhost/phpinfo.php.

Check whether other MySQL clients (such as the command-line client or MySQL Workbench) can connect. This may help you narrow down the problem to PHP or MySQL.

As for the firewall, disable it temporarily while testing. Don't leave it off for long, but a short period shouldn't hurt.

[paul-holmes83]

Can I deal with your sugestions 1 at a time

I have downloaded TCPView and run it the entries tat look like they belong to Wamp are

httpd.exe (pid, 4164) (Protocol, TCP) (Local Port, http) (remote Port, 0) (State, Listening)
mysqld.exe (pid, 968) (Protocol, TCP) (Local Port, 3306) (Remote Port, 0) (State, Listening)
mysqld.exe (pid, 968) (Protocol, TCPV6) (Local Port, 3306) (remote Port, 0) (state, Listening)

the mysqld pid is supposed to be 968 , don't know where the smiley came from

there does not seem to be anything else using the local Ports.

phpinfo says (if I am looking at the correct parts!)

In the Apache2Handler section entry for hostname:port = localhost:80
In the php Variables Section entry for _SERVER["HTTP_HOST"] = localhost
In the php Variables Section entry for _SERVER["SERVER_PORT"] = 80

I disabled my firewall before starting the Wamp server, but it made no difference.

on the command line client following the example given in the link, but leaving out password, I have not set one
I got the following output ERROR 2003 (HY000): Can't connect to MySQL sever on 'localhost' (10060)

I have downloaded MySQL Workbench, but I am unsure how to use it?

[essellar]

Not to answer the question, 'cuz it's baffling and oh, so wrong...

The smiley comes from putting an eight and a close parenthesis right side-by-each. Graphic emoticons must die!

[misson]

mysqld.exe (pid, 968) (Protocol, TCP) (Local Port, 3306) (Remote Port, 0) (State, Listening)
mysqld.exe (pid, 968) (Protocol, TCPV6) (Local Port, 3306) (remote Port, 0) (state, Listening)

From this, you know which ports the MySQL server is listening on. If a MySQL client is using one of these ports and can't connect, that tells you something is blocking the connection.

phpinfo says (if I am looking at the correct parts!)

That isn't the relevant information. Since you need to check how PHP is configured to connect to MySQL, you should be looking at the MySQL configuration. phpMyAdmin before 3.4 defaulted to the outdated mysql extension. Starting with 3.4, phpMyAdmin defaults to mysqli. Check the settings for whichever extension phpMyAdmin is using on your install.

I disabled my firewall before starting the Wamp server, but it made no difference.

Make sure you leave the firewall disabled while testing, not just when starting the server. PHP connects to MySQL when it handles a request, not when Apache starts.

on the command line client following the example given in the link, but leaving out password, I have not set one
I got the following output ERROR 2003 (HY000): Can't connect to MySQL sever on 'localhost' (10060)

This is the most useful information so far. A web search for the exact error message will turn up many pages, including the manual page for MySQL error 2003 (10060).

If this error is caused by network connectivity problems, one resolution is to use named pipes, bypassing networking altogether.

I have downloaded MySQL Workbench, but I am unsure how to use it?

MySQL workbench is a graphical alternative to the command line utilities. You don't need both (though you may find MWB useful for other things).

the mysqld pid is supposed to be 968 , don't know where the smiley came from

The advanced post editor has a "Disable smilies in text" in the "Additional Options" section.

[paul-holmes83]

I will look at this shortly to see if I can make sense of it.

I will just say that I downloaded Wamp from the same place onto a friends PC who is using the same version of Vista, but different Anti Virus software and it run straight out of the box with no problems at all, so it is my PC configaration that is causing the problem somewhere.

---------- Post added at 09:16 PM ---------- Previous post was at 09:09 PM ----------

Make sure you leave the firewall disabled while testing, not just when starting the server. PHP connects to MySQL when it handles a request, not when Apache starts.

What I meant was that I disabled the firewall before starting the Wamp sever, then I tested it with the firewall still off.

Sorry for not being clear

---------- Post added at 11:26 PM ---------- Previous post was at 09:16 PM ----------

Just a further note I shut down my antivirus completly to test it, but it made no difference.

---------- Post added at 11:33 PM ---------- Previous post was at 11:26 PM ----------

Although Wamp is on the local machine could the router be causing the problem.

---------- Post added at 11:45 PM ---------- Previous post was at 11:33 PM ----------

From this, you know which ports the MySQL server is listening on. If a MySQL client is using one of these ports and can't connect, that tells you something is blocking the connection.

Looking at the Tcpview window there is nothing else using this port.

That isn't the relevant information. Since you need to check how PHP is configured to connect to MySQL, you should be looking at the MySQL configuration. phpMyAdmin before 3.4 defaulted to the outdated mysql extension. Starting with 3.4, phpMyAdmin defaults to mysqli. Check the settings for whichever extension phpMyAdmin is using on your install.

Sorry I do not understand what information you needed from phpinfo, but I can tell you what the version numbers are.
Apache 2.2.17
PHP 5.3.5
MySQL 5.5.8

This is the most useful information so far. A web search for the exact error message will turn up many pages, including the manual page for MySQL error 2003 (10060).

Sorry I did not understand the information in that link

If this error is caused by network connectivity problems, one resolution is to use named pipes, bypassing networking altogether.

Again this went right over my head.