Windows could not start the Apache2 on Local Computer - problem

Question

During the installation of Apache2 I got the following message into cmd window:

Installing the Apache2.2 service The Apache2.2 service is successfully installed. Testing httpd.conf....

Errors reported here must be corrected before the service can be started. httpd.exe: Could not reliably determine the server's fully qualified domain name , using 192.168.1.3 for ServerName (OS 10048)Only one usage of each socket address (protocol/network address/port) is normally permitted. : make_sock: could not bind to address 0.0.0.0:80 no listening sockets available, shutting down Unable to open logs Note the errors or messages above, and press the key to exit. 24...

and after installing everything look fine, but it isn't. If I try to start service I got the following message:

Windows could not start the Apache2 on Local Computer. For more information, review the System Event Log. If this is a non-Micorsoft service, contact the service vendor, and refer to service-specific error code 1.

Apach2 version is 2.2.9

Does anyone have the same problem, or could help me.

Answer 1

There is some other program listening on port 80, usual suspects are

1. Skype (Listens on port 80)
2. NOD32 (Add Apache to the IMON exceptions' list for it to allow apache to bind)
3. Some other antivirus (Same as above)

Way to correct it is either shutting down the program that's using the port 80 or configure it to use a different port or configure Apache to listen on a different port with the Listen directive in httpd.conf. In the case of antivirus configure the antivirus to allow Apache to bind on the port you have chosen.

Way to diagnose which app, if any, has bound to port 80 is run the netstat with those options, look for :80 next to the local IP address (second column) and find the PID (last column). Then, on the task manager you can find which process has the PID you got in the previous step. (You might need to add the PID column on the task manager)

C:\Users\vinko>netstat -ao -p tcp

Conexiones activas    Proto  Dirección local          Dirección remota        Estado           PID   TCP    127.0.0.1:1110         127.0.0.1:51373        TIME_WAIT       0   TCP    127.0.0.1:1110         127.0.0.1:51379        TIME_WAIT       0   TCP    127.0.0.1:1110         127.0.0.1:51381        ESTABLISHED     388   TCP    127.0.0.1:1110         127.0.0.1:51382        TIME_WAIT       0   TCP    127.0.0.1:1110         127.0.0.1:51479        TIME_WAIT       0   TCP    127.0.0.1:1110         127.0.0.1:51481        TIME_WAIT       0   TCP    127.0.0.1:1110         127.0.0.1:51483        TIME_WAIT       0   TCP    127.0.0.1:1110         127.0.0.1:51485        ESTABLISHED     388   TCP    127.0.0.1:1110         127.0.0.1:51487        TIME_WAIT       0   TCP    127.0.0.1:1110         127.0.0.1:51489        ESTABLISHED     388   TCP    127.0.0.1:51381        127.0.0.1:1110         ESTABLISHED     5168   TCP    127.0.0.1:51485        127.0.0.1:1110         ESTABLISHED     5168   TCP    127.0.0.1:51489        127.0.0.1:1110         ESTABLISHED     5168   TCP    127.0.0.1:59264        127.0.0.1:59265        ESTABLISHED     5168   TCP    127.0.0.1:59265        127.0.0.1:59264        ESTABLISHED     5168   TCP    127.0.0.1:59268        127.0.0.1:59269        ESTABLISHED     5168   TCP    127.0.0.1:59269        127.0.0.1:59268        ESTABLISHED     5168   TCP    192.168.1.34:51278     192.168.1.33:445       ESTABLISHED     4   TCP    192.168.1.34:51383     67.199.15.132:80       ESTABLISHED     388   TCP    192.168.1.34:51486     66.102.9.18:80         ESTABLISHED     388   TCP    192.168.1.34:51490     74.125.4.20:80         ESTABLISHED     388 

If you want to Disable Skype from listening on port 80 and 443, you can follow the link http://www.mydigitallife.info/disable-skype-from-using-opening-and-listening-on-port-80-and-443-on-local-computer/

Answer 2

I hope this helps others with this error.

Run the httpd.exe from the command line to get an accurate description of the problem.

I had the same error message and it turned out to be a miss configured ServerRoot path. Even after running setup_xampp.bat the httpd.conf had the wrong path.

My error.log was empty and starting the service does not give an informative error message.