WampServer

I just installed WAMP on my desktop but Apache will not start. I've read posts of other people having the same problem and it appears that I might have some other process using port 80.

I did a netstat -a -o -n and this is what I get:

Proto Local Address Foreign Address State PID
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 848
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:2869 0.0.0.0:0 LISTENING 1200
TCP 0.0.0.0:3306 0.0.0.0:0 LISTENING 2264
TCP 127.0.0.1:1042 127.0.0.1:1043 ESTABLISHED 1936
TCP 127.0.0.1:1043 127.0.0.1:1042 ESTABLISHED 1936
TCP 127.0.0.1:5152 0.0.0.0:0 LISTENING 1572
TCP 192.168.0.10:139 0.0.0.0:0 LISTENING 4
TCP 192.168.0.10:1161 66.162.107.142:1935 ESTABLISHED 3732
TCP 192.168.0.10:1840 66.162.107.175:80 TIME_WAIT 0
TCP 192.168.0.10:1841 66.162.107.175:80 TIME_WAIT 0
TCP 192.168.0.10:1842 66.162.107.175:80 TIME_WAIT 0
TCP 192.168.0.10:1843 89.31.144.147:80 TIME_WAIT 0
TCP 192.168.0.10:1844 89.31.144.147:80 TIME_WAIT 0
TCP 192.168.0.10:1845 66.162.107.175:80 TIME_WAIT 0
TCP 192.168.0.10:1846 89.31.144.147:80 TIME_WAIT 0
TCP 192.168.0.10:1847 89.31.144.147:80 TIME_WAIT 0
TCP 192.168.0.10:1848 66.162.107.175:80 TIME_WAIT 0
TCP 192.168.0.10:1850 66.162.107.175:80 TIME_WAIT 0
TCP 192.168.0.10:1852 89.31.144.147:80 TIME_WAIT 0
TCP 192.168.0.10:1854 66.162.107.175:80 TIME_WAIT 0
TCP 192.168.0.10:1855 66.162.107.175:80 TIME_WAIT 0
TCP 192.168.0.10:1856 66.162.107.175:80 TIME_WAIT 0
TCP 192.168.0.10:1857 66.162.107.175:80 TIME_WAIT 0
TCP 192.168.0.10:1858 66.162.107.175:80 TIME_WAIT 0
TCP 192.168.0.10:1859 66.162.107.175:80 TIME_WAIT 0
TCP 192.168.0.10:1860 66.162.107.175:80 TIME_WAIT 0
TCP 192.168.0.10:1861 66.162.107.175:80 TIME_WAIT 0
TCP 192.168.0.10:1862 66.162.107.175:80 TIME_WAIT 0
UDP 0.0.0.0:445 *:* 4
UDP 0.0.0.0:500 *:* 600
UDP 0.0.0.0:4500 *:* 600
UDP 127.0.0.1:123 *:* 916
UDP 127.0.0.1:1690 *:* 1208
UDP 127.0.0.1:1900 *:* 1200
UDP 192.168.0.10:123 *:* 916
UDP 192.168.0.10:137 *:* 4
UDP 192.168.0.10:138 *:* 4
UDP 192.168.0.10:1900 *:* 1200

No local addresses are using port 80, but quite a few foreign are using it. Can anyone help with this issue?
Let me know if you need more information.

Thanks.

Try doing wampmanager -> Apache -> Service -> Test Port 80

Its easier to read.

If thats no help look in your Windows Event Viewer in the Windows Logs -> Application section for any messages from "Apache Service". That normally gives a clue.

WampManager (tray icon) -> apache -> Service -> Install service

Thank you doncuan and RiggsFolly.

The results of Test Port 80 are "Your port 80 is not actually used"
I did the "Install service" and also checked Windows event viewer but there is no Apache errors, just some informational messages about MySQL.
The Apache Error log says this:

[Wed Aug 15 07:52:02 2012] [notice] Apache/2.2.21 (Win32) PHP/5.3.8 configured -- resuming normal operations
[Wed Aug 15 07:52:02 2012] [notice] Server built: Sep 10 2011 11:34:11
[Wed Aug 15 07:52:02 2012] [notice] Parent: Created child process 3224
[Wed Aug 15 07:52:03 2012] [notice] Child 3224: Child process is running
[Wed Aug 15 07:52:03 2012] [crit] (OS 10022)An invalid argument was supplied. : Child 3224: setup_inherited_listeners(), WSASocket failed to open the inherited socket.
[Wed Aug 15 07:52:03 2012] [crit] Parent: child process exited with status 3 -- Aborting.

I searched for the error and found information here: [www.apachelounge.com]

I followed directions. But I still can't start Apache. Can you provide any help?
Steve

Did u have a virus recently on that machine?

Steven Martin
stevenmartin99@gmail.com
stevenmartin99@hotmail.com
PampServer.com - [pampserver.com]

Hi Steven,
Thank you very much for joining this discussion.

Yes I recently had a virus. Malware removed it. In fact that's the reason why I purchased Malware. So the virus happened sometime before I started experiencing the inability to start Apache.

Do you think that might be related to this issue?

Thanks!
Steve

yes, most definitely.

in all the cases ive dealt with, this issue always ends up with a corrupt winsock/firewall issues.

there is a couple of tools you can try....

ComboFix is good
Microsoft have released a hot fix that can repair the damaged to the firewall.


start here >
[support.microsoft.com]
[www.combofix.org]
[answers.microsoft.com]

But honestly I would reinstall the OS.

Steven Martin
stevenmartin99@gmail.com
stevenmartin99@hotmail.com
PampServer.com - [pampserver.com]



Edited 1 time(s). Last edit at 08/16/2012 02:41PM by stevenmartin99.