Important Apache install omission

I have just finished installing Apache 2.0.55 on a Win XP Pro
platform. This is often frustrating, since I am pretty much an
amateur.

In this case, I have been chasing an inability to install the service
problem.

Symptom: I get the message

An invalid argument was supplied. : make_sock: unable to listen for
connections on address 127.0.0.1:80.
no listening sockets available, shutting down
Unable to open logs

I tried many things, changing address, port, etc.

Solution: I closed my virus scanning program, McAfee VirusScan.

As soon as I did that, the installation of apache as a service
happened immediately.

Why doesn't the documentation say to shut down virus protection
services, or provide a workaround? This has got to be a common
problem.

On 03 Mar 2007, "Data Guy" <paul@wubios.wustl.edu> wrote in
comp.infosystems.www.servers.ms-windows:

> Why doesn't the documentation say to shut down virus protection
> services, or provide a workaround? This has got to be a common
> problem.

Not every virus program gets in the way. Avast and AVG don't - I've
installed apache without shutting them down. But if I did have a
problem, that would be the first place I'd look. It's just common
sense.

McAfee is the problem, not apache.

On Mar 3, 8:11�pm, Nil <rednoise+n...@REMOVETHIScomcast.net> wrote:
> On 03 Mar 2007, "Data Guy" <p...@wubios.wustl.edu> wrote in
> comp.infosystems.www.servers.ms-windows:
>
> > Why doesn't the documentation say to shut down virus protection
> > services, or provide a workaround? *This has got to be a common
> > problem.
>
> Not every virus program gets in the way. Avast and AVG don't - I've
> installed apache without shutting them down. But if I did have a
> problem, that would be the first place I'd look. It's just common
> sense.
>
> McAfee is the problem, not apache.

Common sense is what you get after you solve a problem, not before.

So that's a silly comment.

Documentation is meant to provide common sense, not to be usable only
when you already know how to install the product.

That is just common sense.

On 05 Mar 2007, "Data Guy" <paul@wubios.wustl.edu> wrote in
comp.infosystems.www.servers.ms-windows:

> Documentation is meant to provide common sense, not to be usable only
> when you already know how to install the product.

I suppose it would be nice if the Apache people advised you that you
need to turn off McAfee, but other virus scanners can stay on. But I
really don't expect them to. For one thing, are you sure it's a general
problem with McAfee and not just a quirk with your particular setup?
And is it a problem with all versions of McAfee or just one or some?
And is it due to the use of any McAfee feature or just certain ones?

I believe that apache is developed by volunteers. I really wouldn't
expect them to have the resources to troubleshoot its interactions with
the hundreds of other Windows' (not to mention all other operating
systems's) applications, unless it was a known and common problem.
Maybe they don't know about it. Have you submitted a report to them?

And I still maintain that Apache isn't a toy, and anyone who is capable
of setting up a server application like that is likely to know enough
to suspect antivirus scanners as a source of installation problems
before almost any other cause.