Topic: Installation and Start Up - UPDATED

[cueball]

:Windows 7 HPE
:Apache 2.2

I downloaded and installed Apache 2.2 today. I am totally new to Apache and to setting up a web server on my home PC. I have much to learn. (Please be gentle)

Following a how-to article at lifehacker.com, I was able to find the httpd.conf file. I edited it to make the changes to comment out the DocumentRoot option as shipped and change it (DocumentRoot "X:/folder-name") and to comment out and change the AllowOverride option to "All."

Following instructions in the how-to, I tried to save the file but got an error message: "Access Denied"

I found my error log file with this content:
"Starting the Apache2.2 service
The Apache2.2 service is running.
rmine the server's fully qualified domain name, using 192.168.1.7 for ServerName
[Sun Oct 26 12:41:20 2014] [notice] Apache/2.2.25 (Win32) configured -- resuming normal operations
[Sun Oct 26 12:41:20 2014] [notice] Server built: Jul 10 2013 01:52:12
[Sun Oct 26 12:41:20 2014] [notice] Parent: Created child process 18416
httpd.exe: Could not reliably determine the server's fully qualified domain name, using 192.168.1.7 for ServerName
httpd.exe: Could not reliably determine the server's fully qualified domain name, using 192.168.1.7 for ServerName
[Sun Oct 26 12:41:22 2014] [notice] Child 18416: Child process is running
[Sun Oct 26 12:41:22 2014] [notice] Child 18416: Acquired the start mutex.
[Sun Oct 26 12:41:22 2014] [notice] Child 18416: Starting 64 worker threads.
[Sun Oct 26 12:41:22 2014] [notice] Child 18416: Starting thread to listen on port 80."

You can see that I tried the file save several times. I have no clue what the bit about 'could not reliably determine server's fully qualified domain name . . . ' means. Here is the first part of my install.log:
"Installing Apache HTTP Server 2.x with
DomainName = xxxxxxxx.info
ServerName = www.xxxxxxxx.info
ServerAdmin = cueball@xxxxxxxx.com
ServerPort = 80
ServerSslPort = 443
ServerRoot = C:/Program Files (x86)/Apache Software Foundation/Apache2.2
Rewrote C:/Program Files (x86)/Apache Software Foundation/Apache2.2/conf/original/extra/httpd-autoindex.conf.in
to C:/Program Files (x86)/Apache Software Foundation/Apache2.2/conf/original/extra/httpd-autoindex.conf
Successfully removed C:\Program Files (x86)\Apache Software Foundation\Apache2.2\conf\original\extr ..."

Perhaps I failed to provide correct data at installation. If that is the case, what did I most likely do wrong and how can I fix it?

How do I go about saving the httpd.conf file with my modifications?

If I have failed to follow protocol in asking this question or failed to provide relevant information, please tell me what I should have done but didn't do.

Thank you!
cb

[Steffen]

You do not have to change files in conf/original/, it is a backup of the original config files, and are not used.

Maybe you find some pointers in :
http://www.apachelounge.com/viewtopic.php?t=2394


This is not an error:

[notice] Parent: Created child process 18416
httpd.exe: Could not reliably determine the server's fully qualified domain name, using 192.168.1.7 for ServerName

[cueball]

Thank you, Steffen!

I have much to learn.

[cueball]

I read the web page you suggested, Steffen; however, that leads me to more questions.

Yes, I installed httpd-2.2.25-win32-x86-no_ssl.msi. Per the post cited, I tried to follow the instructions to uninstall it. I do not understand the instructions calling for the httpd to be removed.

First, the run as adminstrator as it might be used in a command prompt puzzles me. What, specifically must I do?

Second, after changing directories to point to the location where Apache was installed down to the BIN sub-directory, I tried to run the Code: as shown in the cited post. The result was a message indicating that 'httpd' is not a valid command. Could anyone be more specific about what I should do?

Next, I navigated to the Control Panel > Programs and Features and selected Apache and uninstalled it. Although it took longer than I expected, the uninstall appears to have worked because it no longer appears in the list of Programs and Features; however, the folders and files in Program Files (x86) for Apache were not removed. When I tried to delete the folder titled Apache Software Foundation, I found that I could not. Can someone explain this?

I suspect - but do not know for certain - that there is some problem with my permissions for the files, but I have no idea what that might imply. If I learn to run as administrator will that give me the permissions needed to delete the files and folders created by the .msi installation?

Finally, I followed the link in the thread Steffen cited and downloaded the 2.4.x version but have done nothing more than download it. (I also downloaded the referenced PHP file and have done nothing with it.) I am fearful that trying to install the newer version without removing all vestiges of the 2.2.25 msi version will cause problems. I'm also confused because I read somewhere (can't remember the source) that 2.4.x was not the stable version but that 2.2.x was. Can anyone clarify?

Thank you.

cb

[glsmith]

If I remember correctly, the msi installer adds icons to your menu. There is one for editing the configuration. These worked just dandy up untill Windows Vista. These days, to do anything in Program Files other than run most software, you must be the administrator. Just because your account may be an administrator account, you cannot just blindly do administrative tasks like you could in XP and prior versions.

So to edit your httpd.conf file you need to run things in Administrator mode, to do so you simply right click on an icon and choose "Run as Administrator" from the pop-down menu.

Your Start/Stop/Restart Service icons you need to do the same for those to work. I forget the rest of the icons that are there for the installed Apache.

[cueball]

Thank you! It took me a bit to find the option in File Explorer but I finally did and was able to delete the Apache 2.2.25 MSI files.

I find it strange that this is the first time I've ever run into the RUN AS ADMINISTRATOR conundrum.

Thank you, again!