WampApache service cannot start

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
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Haris DulicIT ArchitectCommented:

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

Open in new window

ddantesAuthor Commented:
Thank you.  I'm unclear how to interpret the results of that command, but I attached a screen shot...netstat
Haris DulicIT ArchitectCommented:
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.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Microsoft Azure 2017

Azure has a changed a lot since it was originally introduce by adding new services and features. Do you know everything you need to about Azure? This course will teach you about the Azure App Service, monitoring and application insights, DevOps, and Team Services.

ddantesAuthor 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 ArchitectCommented:
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..
ddantesAuthor 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 ArchitectCommented:
Post the output of netstat -bano so that i can see the PID of the service using port 80
ddantesAuthor 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 ArchitectCommented:
in order to use taskkill you need administrative prompt..
ddantesAuthor Commented:
Good to know for future reference.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Apache Web Server

From novice to tech pro — start learning today.