Update: Using XAMP
After I’ve written this blog post I’ve figured out that XAMP, although very similar to WAMP, doesn’t force you to run Apache as a service, instead it can run it as a regular process. So I ended up using XAMP, and changed Apache port to 8080 so now everything works.WAMP Issues
If you have Window 7 or later you may have come across issues with WAMP server trying to start Apache service on port 80 and failing.
There are many conflict and issues that might have come up.
Before you try anything, check if you have ZoneAlarm, Nod32, or any other program/firewall that might be blocking Apache server.
If you’re sure that firewall isn’t the problem here is a couple of fixes that you can try.
NOTE: After every fix you try, you must click on yellow WAMP icon and choose Restart All Services
Checking which process is causing the problem
- Open Command Prompt window by typing cmd in Run command box or Start Search, and hit Enter.
- Type in the following command:
netstat -o -n -a | findstr 0.0:80 |
The last column of each row is the process identified (process ID or PID).
- Identify which process or application is using the port by matching the PID against PID number in Task Manager.
- If you don’t see PID column in your Task Manager you need to go to Processes tab -> View Menu -> Select Columns and choose PID from the list
- Now, you may have identified application that reserves port 80, or you may have found out that System is using your port 80. That means that one of internal services is using your port, in which case continue reading further.
Conflict with Skype
If
you found out that Skype is using your port 80, you need to change some
settings in Skype. On Windows, Skype reserves port 80 which is used for
HTTP. Apache requires this port. So if you’re running Skype, you must
go to Tools > Options. Then in the Advanced section, select
Connection. Un-check the box that says “Use port 80 and 443 as alternatives for incoming connection“. Quit Skype and restart. The issue should be resolved.Conflict with IIS Server
IIS Server and Apache are both web server that use port 80 so they might be in conflict. Try stopping IIS by:- Going into Control Panel -> Administrative Tools -> Internet Information Services
- Right click on Default Web Site
- Click on Stop option in the popup menu, and see of the listener on port 80 has cleared.
Conflict with MS SQL Server
MS SQL Server installs “SQL Server Reporting Services (MSSQLSERVER)” that apparently defaults to 80. You can try stopping it to free up port 80.- Go to Control Panel -> Administrative Tools -> Services
- There find MSSQLSERVER (might be found also under SQL Server)
- Double click it -> Click Stop
- Under Startup type: choose Manual
Other Services that can cause conflicts
As described above for MS SQL Server:- Go to Control Panel -> Administrative Tools -> Services
- You can try stopping:
- Web Deployment Agent Service
- Windows Remote Management
- Autodesk EDM Server
- World Wide Web Publishing Service
Try turning off HTTP driver directly
If you’ve tried everything mentioned above and your WAMP server is still not working you could try this (which eventually helped me).- Right click on My Computer icon -> Properties
- Go to Device Manager
- Click on View menu and chooseShow hidden devices
- Now from the list choose Non-Plug and Play devices
- Double click HTTP -> go to Driver
- For Type choose Disabled
- Restart your computer
If everything else fails
You could try changing Apache server to listen to some other port other than port 80.- Click on yellow WAMP icon in your taskbar
- Choose Apache -> httpd.conf
Listen 80 |
ServerName localhost:80 |
Listen 8080 |
ServerName localhost:8080 |
WAMP server should now be working.
No comments:
Post a Comment