The wampapache service terminated with service-specific error 1 (0×1)

Many people must have seen this error. I just installed WampServer 2, and got it. An analysis of the problem results in the following possible causes:

  • a misconfiguration in your httpd.conf. This is the most common. To resolve it, go to the command line (Start > Run > CMD), and enter “httpd.exe –S” in the apache\bin folder.
  • port 80 is already in use. This can happen because you have another application, e.g. IIS running on port 80. Actually there is no reason you shouldn’t be able to use both, just not at the same time. From the Wamp menu you can choose Apache > Test port 80 and it will tell you which service is using it. To stop IIS you will have to go to Control Panel > Adminstrative Tools > Services and stop the World Wide Web Publishing service.
  • your firewall is blocking port 80. All firewalls are different. First, just stop the firewall to test if it’s the cause of the problem. If it is, you need to add 127.0.0.1 to the ‘safe list’.
  • Update: I recently found the ‘IIS management service’. This can also interfere with apache, so stop it if you don’t need it.
  • Update2: Thanks, Anil, for the Skype issue. I had that one as well actually.. So, guys, just stop Skype (right click in the task bar, and exit the app). Then start Wampserver and you can restart Skype. Or change the Skype port numbers. See the Skype support page.

I hope this helps anyone, since I couldn’t find anything online.

12 comments so far

  1. Stian Tonnesen on

    I also noticed that if you run the Jungledisk software this will also interfere with Wampserver.

  2. anil on

    ever skype also runs on 80 by default. so it could also create a problem. start skype after wamp gets started and skype would take other port

  3. geoffrey on

    Thanks for the Skype tip-off! Worked nicely.

    - Geoffrey

  4. Andre on

    Yeah I had the same issue and stopped skype and the problem was sorted!

    Tnx guys

  5. twohawks on

    I run into this once in a while and I forget that sometime I adjust the
    *** Listening Port in http.conf ***
    for other PC’s I test from on the local LAN !!

    I am posting so when I come looking for the answer again I will see this …LOL!
    Check yer listening port assignments !!

    Thanks for the post here.
    Cheers,
    TwoHawks

  6. Artem Russakovskii on

    Skype was the issue indeed. I’ve now turned off the Skype port 80 usage in Advanced Settings. Thanks for the hint!

  7. Marty Peet on

    Nother thing you might want to look at is that if you have any aliases configured that they are in fact connected and resolving properly. Easiest way is to empty your wamp/alias directory, copy the .conf files to somewhere and restart all services. If it restarts you’ve found the problem, you’ll need to test each .conf file to find out which one/ones is causing the problem

  8. Seth Wilpan on

    Thanks. httpd.exe -S showed me the error in a config file.

  9. Wookie on

    Thanks Marty Peet, I’d forgotten I was half way through creating a .conf file in the alias directory. Things are working again!

  10. Niels on

    For me Skype as well.
    Thx for this page!

  11. Riz on

    Thanks or sharing and solving my problem

  12. Janak on

    Thanks for sharing this useful information. It solved my problem.


Leave a reply