WampServer

I having a bit of a nightmare at the moment. For the last 7 or so months, Wamp has worked fine on my x64 Windows 7 machine. Now, recently, httpd has gone a little mad and just starts using up all available memory. I start it up, open task manager and watch it climb the ranks until it hits about 450,000k memory and just destroys everything else.

I keep seeing a repeated line: [Fri May 28 20:01:46 2010] [error] (OS 10022)An invalid argument was supplied. : Child 6140: Encountered too many errors accepting client connections. Possible causes: dynamic address renewal, or incompatible VPN or firewall software. Try using the Win32DisableAcceptEx directive.

over and over again. I added the Win32DisableAcceptEx directive which seemed to stop the memory issue but then still doesn't allow me to run any pages.

Need help. Badly ><

Thanks.

firewall or antivirus i think

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

Well I thought about that but I haven't made any changes. I disabled my AV, check exceptions for Apache with my firewall and still get the same.

I've also tried installing Apache on its own (without being part of the wamp collection) and I'm still having issues. Argh.

seem you had auto update on which result hosts file change so open file hosts in folder C:\WINDOWS\System32\drivers\etc and delete anything in there and have only this line and nothing else

127.0.0.1 localhost

Have fun,

FREE One A Day
FREE Photo
FREE Games
FREE Websites
FREE Portable GPS
FREE WAMP Guides

Thanks for the suggestion. It wasn't that either. I've tried connecting via localhost and 127.0.0.1 as well and get nothing. Checked the netstat output and when running, the only app binded to 0.0.0.0:80 is httpd.exe.

I never seemed to have a problem until the windows update and I can't seem o roll back to it.

I have exactly the same issue with a Vista PC. Does anyone have any further information about it, or a workaround?

Thank you,

Hi guys,
I had the same problem and I just solved checking winsock, with start -> run -> msinfo32
as suggested in
[support.microsoft.com]

i've seen a software for recording streaming recently installed that took the place of the original MSAFD
so i uninstalled that software and everything works now! (now the protocol is back to MSAFD)
i've seen in other forum that the same result is achieved using the command:

netsh winsock RESET

but I never tried

2 days beating my head against the wall... so I hope this can help someone...