XAMPP Port 80 Error in Windows 7

Question

XAMPP 3.1.0 does not work because port 80 is used. I looked around and this seems to be a common problem. I stopped IIS, skype is not running, the web deployment agent service is running, I changed the Apache httpd.conf configuration to listen on port 80 according to the second answer to this question: XAMPP PORT 80 is a Busy / EasyPHP error in the Apache configuration file:, but still no luck. Here are the error messages in the XAMPP control panel:

2:03:49 PM [Apache] Problem detected! 2:03:49 PM [Apache] Port 80 in use by "system"! 2:03:49 PM [Apache] Apache WILL NOT start without the configured ports free! 2:03:49 PM [Apache] You need to uninstall/disable/reconfigure the blocking application 2:03:49 PM [Apache] or reconfigure Apache to listen on a different port 2:03:49 PM [Apache] XAMPP Apache is already running on port 443 2:03:49 PM [mysql] MySQL Service detected with wrong path 2:03:49 PM [mysql] Change XAMPP MySQL settings or 2:03:49 PM [mysql] Uninstall/disable the other service manually first 2:03:49 PM [mysql] Found Path: ERROR: Not Able To Open Service Manager 2:03:49 PM [mysql] Expected Path: c:\xampp\mysql\bin\mysqld.exe --defaults-file=c:\xampp\mysql\bin\my.ini mysql 2:03:49 PM [mysql] Problem detected! 2:03:49 PM [mysql] Port 3306 in use by "mysqld.exe"! 2:03:49 PM [mysql] MySQL WILL NOT start without the configured ports free! 2:03:49 PM [mysql] You need to uninstall/disable/reconfigure the blocking application 2:03:49 PM [mysql] or reconfigure MySQL to listen on a different port 2:03:49 PM [Tomcat] Problem detected! 2:03:49 PM [Tomcat] Port 8080 in use by "c:\xampp\apache\bin\httpd.exe"! 2:03:49 PM [Tomcat] Tomcat WILL NOT start without the configured ports free! 2:03:49 PM [Tomcat] You need to uninstall/disable/reconfigure the blocking application 2:03:49 PM [Tomcat] or reconfigure Tomcat to listen on a different port 

When I switch to localhost, it displays me on the IIS7 screen, even if the service is stopped in the control panel.

Answer 1

Use netstat -bano on the advanced command line to find out which applications are listening on which ports.

But usually the following applications use port 80 on Windows:

 IIS World Wide Web Publishing service IIS Admin Service SQL Server Reporting services Web Deployment Agent Service 

Stop any of the above applications. This can be done on the Services tab in the task manager.

Answer 2

See The Computer Hugger answer at this link (hope this helps) Apache work and port 80

If not, try following because it helped in my case: The reason for the error is that SQL Reporting Services uses PORT 80, which uses Apache. Disabling SQL Reporting Services to start will automatically solve the problem.

Stop the SQL Reporting Service, start, and then enter “Administration”, click “Name”, select “Computer Management”, then “Services and Applications”> “SQL Server Configuration”> “Services” and “SQL Reporting Servicves Services”, install it in "Manual Start" and "Stop."

Reboot the XAMPP server and hopefully it will be useful for you :)

Answer 3

I got this error after installing XAMPP on Windows 8:

 [Apache] You need to uninstall/disable/reconfigure the blocking application [Apache] or reconfigure Apache to listen on a different port 

This is what I did to fix this:

• Go to Windows Update and verify that all Windows updates are processed.

• Reboot the computer. And launch the XAMPP control panel. Then the errors disappear and the following is displayed:

   [main] Windows Version: Windows 8 Pro 64-bit [main] XAMPP Version: 1.8.3 [main] Control Panel Version: 3.2.1 [ Compiled: May 7th 2013 ] [main] You are not running with administrator rights! This will work for [main] most application stuff but whenever you do something with services [main] there will be a security dialogue or things will break! So think [main] about running this application with administrator rights! [main] XAMPP Installation Directory: "c:\xampp\" [main] Checking for prerequisites [main] All prerequisites found [main] Initializing Modules [main] Starting Check-Timer [main] Control Panel Ready 

So, a few warnings, but it started off fine.