Apache HTTP Server Setup

Scrublet

I've been working on getting Apache up for this clinic I'm volunteering at. They want to be able to look at/update a calendar on this internal site. I did everything for it on my laptop running Windows Vista. Finally done, I moved stuff over to the server running Windows Server 2003 R2, SP2. During the Apache Install it generated an error having something to do with an inability to bind to 0.0.0.0:80 or something. I haven't been able to get the error to print out since.

The server will not start. I've checked all the paths in the config file, and nothing else should need modification. An error logfile isn't being generated, so it's failing before that. Any idea what could be causing the problem, or at least how to begin trying to find the problem?

Jimmy King

The windows server machine probably has IIS running, which would have something boudn to port 80.

Jasconius

In Windows Server 2003, open up IIS (found in the start menu some damn where, the 2003 start menu is grossly crowded).

In IIS, you will most likely see some sort of Default Application already running, unless they were actually using IIS in which case it may be named to something else.

I predict it can be as simple as just right clicking on that app and hitting "Stop", but I am not certain it will not start over again when you restart the machine. You should test for that.

If Stop doesn't free up Port 80, then you can just go right click, hit properties, on the Web Site tab change the TCP port (near the right) to some arbitrary number that isn't port 80 such as... I don't know 30683.

It doesn't really matter, just make sure the port is not conflicting with a service that is actually being used.