Windows failed to start Apache2 on the local computer - problem

During the installation of Apache2, I received the following message in the cmd window:

Installing the Apache2.2 Service. Apache2.2 service installed successfully. Testing httpd.conf ....

Errors indicated here must be fixed before starting the service. httpd.exe: Failed to reliably determine the server fully domain name using 192.168.1.3 for ServerName (OS 10048) Only one use of each socket address (protocol / network address / port) is usually allowed .: make_sock: could not bind the address 0.0.0.0 : 80 no listening jacks available, shutdown open logs. Check for errors or messages. above and press the Exit key. 24 ...

and after installation, everything looks great, but it’s not. If I try to start the service, I received the following message:

Windows failed to start Apache2 Local Computer. See the system event log for more information. If this is a non-Micorsoft service, contact your service provider and refer to service error code 1.

Apach2 Version - 2.2.9

Someone has the same problem or may help me.

+61
windows windows-xp apache2
Oct 12 '08 at 16:13
source share
19 answers

There is another program listening on port 80, the usual suspects

  • Skype (listening on port 80)
  • NOD32 (add Apache to the IMON exception list so that it can bind Apache)
  • Some other antiviruses (same as above)

To fix this, you can disable a program that uses port 80, or configure it to use a different port, or configure Apache to listen on a different port using the Listen directive in httpd.conf. For an antivirus, configure an antivirus so that Apache can communicate with the port of your choice.

A way to diagnose which application, if any, is connected to port 80, runs netstat with these parameters, look for: 80 next to the local IP address (second column) and find the PID (last column). Then in the task manager you can find which process has the PID that you received in the previous step. (You may need to add a PID column in 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 disconnect Skype from listening on ports 80 and 443, you can click on the link http://www.mydigitallife.info/disable-skype-from-using-opening-and-listening-on-port-80-and- 443-on-local-computer /

+131
Oct 12 '08 at 16:21
source share

I hope this helps others with this error.

Run 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 missing ServerRoot loop. Even after running setup_xampp.bat, httpd.conf had the wrong path.

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

+84
Dec 18 '11 at 3:11
source share

The best way to solve the problem is to change the port number in Apache2 \ conf \ httpd.conf. Change the port number as vapor: Listen to 8888 and the server_name machine name: 8888. Restart the Apache server after changing the port number.

+20
Jun 24 '09 at 7:01
source share

I had the same problem. I checked netstat, other running processes, the firewall and changed httpd.conf, stopped the antivirus, But all my efforts were in vain. :(

So finally, the solution was to stop IIS. And it worked :)

I believe that IIS and apache do not work together. If anyone knows any work, let us know.

+5
Jan 10 '09 at 14:34
source share

Run httpd.exe from the command line, as Tim said. The path to PostgreSQL has changed, nothing else was running on port 80, and I did not see anything in the error.log file.

I clone my boot disk / partition after the base is configured, so I do not need to spend three days installing and relaying everything. Turned around, I reinstalled my WAPP stack and used very specific names / versions for PostgreSQL. Windows will not return a specific error message if you do not run the command from the command line.

+4
Apr 27 '15 at 15:45
source share

Follow this step, it will work fine. Go to Control PanelPrograms and Features → click on “Enable or Disable Windows Features” . → see IIS. Checked or not . If the check box is selected, cancel IIS and restart the computer. After that, the Open service will review the status of the Web Deployment Agent ; if it starts, stop. Also see WampAppache and WampSqlID , if it is not running, please start manually. this will work for me.

+3
Jul 11 '13 at 4:09
source share

Hi, I am also encountering this issue today. And the log error in the event viewer looks like this: Apache called the following error:

1.Wrapper php-cgi.exe could not be accessed: (720005) Access denied.

2. Service Monitor 2.apache: the requested operation failed

This is a pressing access issue. So the solution as current helps me change the security properties of php-cgi.exe

  • do not deny permission to parents ...

  • add each user

+3
Aug 15 '13 at 16:44
source share

if applications and IIS are running at the same time, then it is possible to hang up the apache service

when I stopped all IIS websites once and then restarted the Apache service and it works for me .... Jai ...

+2
Jan 10 2018-11-11T00:
source share

The problem with the Windows Vista Home Premium operating system: the easiest way to solve the problem is to change the port number in Apache2 \ conf \ httpd.conf.

Change the port number in the following lines. Listen from 80 to 8888 and ServerName machinename (for example: localhost) from 80 to 8888. Save, then close. Open Apache Service Monitor and restart the service or go to Computer Management> Services and find Apache 2.2 and start or restart.

+2
Mar 27 '11 at 4:29
source share

Remove apache from the control panel and delete the apache folder from Program Files and restart the computer, then install apache again. This will solve the problem; if you don’t follow these steps: install IIS, if it’s not installed, then start IIS and stop it ... Using Services, start the apache service ... enjoy apache.

+1
Jul 13 '10 at 9:13
source share

I had this problem twice. The first problem was fixed using the marked answer on this page (thanks for that). However, the second time turned out to be a bit more complicated.

I found that in my httpd-vhosts.conf file I made a mistake when assigning the document root to a domain name. This solution to my problem has been fixed. It is worth checking (or even returning to an empty copy) of your httpd-vhosts.conf file for any errors or typos.

+1
Mar 01 2018-12-01T00:
source share

if you use windows os and think skype is not suspect, then you can check the task manager and check "Show processes from all users" and make sure that there is no entry for httpd.exe. Otherwise, complete its process. This solves my problem.

+1
Mar 13 '13 at 6:00
source share

Yes, I had to change port: 80 to: 90 as port: 80 was busy with some other system resource.

You can view the logs in the Apache2.2 \ logs folder

Thank,

+1
Aug 26 '13 at 5:37 on
source share

Always double-check httpd.conf to make sure the document root directory points to an existing folder correctly.

 #if you have c:\your-main-folder\www\ DocumentRoot "c:/your-main-folder/www/" #if you have c:\your-main-folder\www\sub-folder\ DocumentRoot "c:/your-main-folder/www/sub-folder/" 

DocumentRoot points to the folder that must exist on your drive.

+1
Nov 23 '13 at 21:26
source share

I had the same problem. when I restarted my game, it turns yellow, but not green. In services, I stop all sql server services. after that it works for me ..

  • Two think they need to be taken care of. 1) the port must be different 2) stop those services that may be on port 80
+1
Mar 08 '14 at 9:33
source share

Thanks for helping the guys. I found another culprit. SimplifyMedia recently added a photo sharing option. Apparently, it also uses port 80 and prevents Apache from starting. Hope this helps someone.

0
Sep 10 '09 at 16:53
source share

Me too the same problem. The solution is to add or remove programs, and then turn on and off the functions of the rotation window. Disable IIS. This disables the "Internet Information Services" and the "Internet Service Removable Network Core." I have included the remaining functions. The computer will ask you to restart the system. Restart your computer and then install the apache HTTP server. I understood. Server is running successfully ...

0
May 10 '10 at 19:59
source share

For me, this was the result of installing the document root (in httpd.conf ) in a directory that did not exist (I just cleared the htdocs of the previous project).

0
May 29 '16 at
source share

Windows 10 - Administrator Account

I needed to switch the account to an administrator type account in windows services

 httpd.exe -k install 

Cannot add a setting with sufficient user rights.

0
Jun 14 '17 at 2:55 on
source share



All Articles