WampApache service cannot start

ddantes
ddantes used Ask the Experts™
on
Although I haven't knowingly changed anything about my Wampserver configuration, the WampApache service will no longer start. Here is a text file saved from the Event Viewer...Event-Viewer.txt
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Haris DulicIT Architect

Commented:
Hi,

first check if anything is using port 80 using :
netstat -an |more 

Open in new window

?

Author

Commented:
Thank you.  I'm unclear how to interpret the results of that command, but I attached a screen shot...netstat
IT Architect
Commented:
In the second line you can see that there is service which is listening on port 80 and that is reason why you cannot start your apache since it tries to use port 80 which is busy.

To find what is listening on port 80, this version of netstat
netstat -bano

Open in new window

will give you more info.

You have two options either change the apache port in httpd.conf or stop whatever is listening on port 80.
CompTIA Cloud+

The CompTIA Cloud+ Basic training course will teach you about cloud concepts and models, data storage, networking, and network infrastructure.

Author

Commented:
Thank you.  I found one reference to listening on port 80:  tlntsvr.exe   Stopping the telnet service didn't allow WampApache service to start, and repeating the netstat -bano command shows port 80 as "listening".
Haris DulicIT Architect

Commented:
you can use "taskkill /pid PID" to free the port. Do not start apache until "netstat -bano shows that there is nothing listening on port 80. after you cleared the port apache wont have problem to start.

If it fails post the error msg here..

Author

Commented:
OK.  However, since I don't know the process identifier, but only the port, can you provide the taskkill code to use?
Haris DulicIT Architect

Commented:
Post the output of netstat -bano so that i can see the PID of the service using port 80

Author

Commented:
Sorry, I see it now.  The PID is 4, and access is denied when I try to force a taskkill.  I changed the hppd.conf port to 82, and the service started.   I think this resolved the issue, and thank you for your guidance.
Haris DulicIT Architect

Commented:
in order to use taskkill you need administrative prompt..

Author

Commented:
Good to know for future reference.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial