Microsoft HTTPAPI/2.0 use Port 80 – Cannot Start WAMP Apache

Screenshot of Microsoft Web Deployment Service
Microsoft Web Deployment Service

I just installed fresh Microsoft Windows 7, and I installed WAMP for my APACHE – PHP server. When I want to start the server, the WAMP icon turn yellow (not green). Upon further investigation, I found out that when I go to WAMP dock icon -> Apache -> Service -> Test Port 80, I received a message that Port 80 is used Microsoft HTTPAPI/2.0.

I fire up Google and most of the solutions mentioned about turning off Microsoft SQL Server Reporting Services (SSRS). I have browsed my Services and couldn’t find any SSRS installed (although I have SQL Server 2008 Express installed).

Luckily I came across this forum which gives me the solution.

We must stop Web Deployment Agent Service (MsDepSvc) from Administrative Tools > Services area. You can disable the service, to have port 80 ready when you boot your system.

The following article will explain about this service, you can follow the link below to read more.

Microsoft Web Deploy

Web Deploy is a free technology built by my team that can improve web deployment. It is a deployment service that runs on a server, and enables you to either locally or remotely deploy applications onto it. Web Deploy includes built-in support for creating virtual directories and applications within IIS, copying files and folders, provisioning databases (both SQL Server and MySQL), setting file-system ACLs and more (it even includes built-in providers for things like setting registry entries, registering COM components, etc). In addition to having these built-in deployment features, it also supports a .NET based provider API that enables you to create and plug-in your own custom deployment actions – which allow you to customize it however you want.

106 Replies to “Microsoft HTTPAPI/2.0 use Port 80 – Cannot Start WAMP Apache”

  1. Thank You Friend….. It really worked. Before finding this article, Iread too many article for this problem But none worked. But After reading this I have resolved my problem. Thank You Very Much….

  2. got awamp start up problem from few days and tried everything , what solves my problem is go to control panel, than administrative tools, than services, and look for wampapache and wampsqlid and , they were disabled , i right click on properties and change start-up type from disabled to automatic and apply it.
    after this restart all services on wamp icon and now its start.

  3. Hi .. Thanks Alot .. My whole class was upset searching how to stop that port tried many ideas nothing worked 🙂 Now with this help i started my wamp easily , Thanks again..

  4. Seriously, have been working on this all day – like 7 hours – and your post finally got WAMP to work. Thank you SO much for posting this! I know nothing about computers, but your directions were great and solved the problem. Can’t thank you enough, I only wish I found the information sooner! Cheers!

  5. I had same problem. Here is how I solved it. Right click on computer->Manage->Services And Applications->Web Deployment agent services then right click then stop. You can also adjust Properties if you don’t want it to start automatically.

  6. Thank you very very much. I m trying to solve this problem from many months ago finally with the help of this article i could fix my problem..! Thankx very much..!

  7. Wow, thank you a lot! I was using xampp just fine, then it stopped working… after much troubleshooting, i finally uninstalled it and installed wampp, and it still didn’t work! hours were spent, like you, going through google and trying to figure it out. Your solution worked! Thanks a ton!

  8. Thank you so much! Like the rest of the people here I read dozens of posts elsewhere to no avail, but you saved me. My business partner told me I have to start learning codeigniter and I couldn’t do it without you. Thanks again!

  9. If you have SQL Server already installed, and in the Services list, you don’t find, “Web Deployment Agent Service” … then search for, “SQL Server Reporting Services” … stop either of the services that is Marked as Automatic ….
    It worked for me …
    Thanks to the original Author of this post ….

  10. can not find that agent services in services to stop
    i have microsoft visual studio and microsoft sql
    but want to run now apache
    help me

  11. What can I say, bro. You saved me from pulling out my hair. Gotta love Microsoft. They must have initialized this thing after I installed Visual Studio. Thank you.

  12. Hi, first of all thanks for the solution. It seems to work but there is a silght problem. I can access PHPmyAdmin but when I type in localhost I get a 403 forbidden message. However, I can access localhost through typing I just wanted to know why I cant access the local host the way I did before. Also, I cant access webgrind either.

    ps- when i fist installed wamp it worked fine but then out of the blue it stopped working and I had to follow you solution.

  13. Hey, so I fixed the problem mentioned in the earlier post. Before I found this solution I tried another which involved making changes in the apache httpd.config file. I had changed the listen code to 8080. Once I changed it back to just 80 everything else was working again. Once again thanks for this.

  14. stoping the sqlserver reporting service allowed apache to start for me, so give it a shot, just go to run and services.msc and stop it.

  15. I don’t think people on the internet are polite enough, so I just wanted to say thanks! Just what I was looking for, works a treat – will serve me right for trying to do development work on a Windows machine too I guess!

  16. Guys who are still having problems should restart their system and try.

    Thank you guys. You are great. keep it up.

  17. Hi,

    When I tested the port 80 I can see the Microsoft-HTTPAPI/2.0

    But there is not a service named Web Deployment Service Agent.

    What can I do?

    This is a Windows 7 Enterprise Running on a Oracle Virtual Machine over a MAC OS as host.

  18. This got me going in the right direction. For me, it was a windows update that turned on Windows Remote Managemenet. Turned it off and all of a sudden, Port 80 started working. Thanks!

  19. Disable both:
    1-Web Deployment Agent Service.
    2-SQL Server Reporting Services if you have sql server installed.
    It worked for me
    Thanks to the original Author

  20. Thank you man. but for me the “offending” service was “World Wide Web Publishing Service”. Any how thanks

  21. Simple solution…
    click on the “W” icon on the task bar > got to “Apache” > select “httpd.conf” > change “listen to port 80″ to “81″

  22. Hi…
    Thanks for the detail…
    In my case stoping “Microsoft SQL Server Reporting Services (SSRS)” worked out pretty well…
    I din’t had Web Deployment Agent Service (MsDepSvc)installed on my system…:)

  23. THANK YOU! You have saved me a ton of time and a ton of work! I had searched many other websites and none really had viable solutions, but turning off that service did the trick!

  24. If you have SQL Server installed too.then search for,controll panel>systems and security>Administrative Tools > Services area. “SQL Server Reporting Services” … right click on it and stop services…
    It works for me …
    however thanks for all the solutions……..

  25. Please add another evil service “Routing and Remote Access Service” to the list, that prevented my WAMP from starting on port 80.
    I checked out all the options above – IIS, Skype, Web Deployment etc. and none of those was running on my Windows Server 2008 r2. Finally, I started disabling and re-enabling the services one by one, running the telnet 80 (if no telnet, install using pkgmgr /iu:”TelnetClient” ) and GET in between. I always got the Microsoft HTTPAPI/2.0 response, but after I disabled the Routing and Remote Access Service, the telnet connection started failing, instead of allowing me to type a GET. So, that was it, disabled it, and Apache started just fine on port 80.
    Routing and Remote Access Service
    Offers routing services to businesses in local area and wide area network environments.
    On hindsight, this may have been due to an earlier VPN connection that was hosted from this machine.
    Hope that helps,

Leave a Reply

Your email address will not be published. Required fields are marked *