Apache Friends Support Forum

Hello,

There probably have been a lot more issues like that, I've googled around, but haven't really found the correct solution. What I am experiencing is that I can with my XAMP run mysql, but never Appache. No, I do not have Skype, however I do have other instant messaging applications such as XFire and Windows Live Messenger. I don't know if those use port 80, I've tried shutting all instant messaging services down, but still didn't work.

You can see my error below:

error wrote:(OS 10013)Er is geprobeerd toegang te verkrijgen tot een socket op een volgens de toegangsmachtigingen niet toegestane manier. : make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs

translated error wrote:(OS 10013)There was an attempt to get access to a socket on the access-granted manner. : make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs

Hmm, well, as you can see my translation skills aren't really that good, so I hope this is clear enough to understand.


I would really appreciate some help on this error, as I am wanting to set up a site on my localhost. Thanks in advance.

So you have to find out which process is listening on port 80.
There are several possibilities:
- use the netstat command in your windows command line as described here
- use the great netstat tool included in the new XAMPP control panel v3.0.2
- use the XAMPP portcheck
- use any other software which can show you used ports on your computer

It wasn't a process causing this. It was a service causing this. For people who have gave up hope like I did:

1) run cmd.exe
2) input 'services.msc' and hit enter
3) disable 'World Wide Web Publishing-service'

Hope that's going to help some people!

If the need arises again to see what is using the ports that XAMPP requires exclusively, use this nice little freeware no-install portable app. CurrPorts from here:
http://www.nirsoft.net/utils/cports.html
This little app. is/was the underlying application used in XAMPP's own port checker - works very well and gives you easy control over the ports, unlike some of the other methods offered here - you may also like some of the many free utilities available from the above linked web site.

Infernus666 wrote:It wasn't a process causing this. It was a service causing this. For people who have gave up hope like I did:

1) run cmd.exe
2) input 'services.msc' and hit enter
3) disable 'World Wide Web Publishing-service'

Hope that's going to help some people!

This can also be done from within the XAMPP Control Panel using the SCM (Service Control Manager) button or in the newer version 3 Control Panel you would use the Win-Services button.