Posted By: bryan39 on January 12, 2016, 8:05 pm | Post: 2 |
For Apache to be able to start/run, it has to be able to bind to (and listen on) port 80 (the HTTP port).
If after installing Apache (or a WAMP such as WampDeveloper Pro), rebooting, and trying to start Apache again – Apache is not able to bind to port 80 and start, then another Application or Service has already taken this port. For Apache to start, we have to figure out what’s using port 80 (and possibly port 443) on your system, and stop and disable it. Known Windows Services That Listen on Port 80 From Services Manager (run: services.msc), stop and disable these native Windows Services which are known to bind to port 80. Double click Service, and change ‘Startup Type’ to ‘Disabled’. SQL Server Reporting Services (ReportServer) Web Deployment Agent Service (MsDepSvc) BranchCache (PeerDistSvc) Sync Share Service (SyncShareSvc) World Wide Web Publishing Service (W3SVC) Internet Information Server (WAS, IISADMIN) You might, or might not, have some of these Services installed and running. Sorry, that's all I know. ----------------------- FacebookYoutube Channel Home Page |
Posted By: nickgreaves on January 13, 2016, 4:55 pm | Post: 4 |
Well I've had no response from the helpdesk.
However after heading over to this page - https://www.devside.net/wamp-server/opening-up-port-80-for-apache-to-use-on-windows - and reading admin's (to my untutored eyes) definitive article, I got lucky at item 5.World Wide Web Publishing Service (W3SVC). After stopping the service and restarting AMPPS, Apache started fine. Thought I'd pass it on in case it's of use to anyone else feeling as desperate as I was! |
Posted By: webraven on January 13, 2016, 5:27 pm | Post: 7 |
Agreed! |
Posted By: ndaweb on October 22, 2018, 3:36 am | Post: 8 |
open cmd as administrator
first use: net stop http /y then: sc config http start= disabled restart apache on ampps panel. do it again! |