Setting up Apache Server and PHP (Windows 7 Ultimate 64-bit)

  • (2 Pages)
  • +
  • 1
  • 2

18 Replies - 22405 Views - Last Post: 23 August 2012 - 04:40 AM

#1 Tenderfoot  Icon User is offline

  • D.I.C Head
  • member icon

Reputation: 11
  • View blog
  • Posts: 160
  • Joined: 21-March 12

Setting up Apache Server and PHP (Windows 7 Ultimate 64-bit)

Posted 22 August 2012 - 03:08 AM

So I've been trying to set up Apache and PHP but it doesn't seem to work. I'm hoping some of you guys could help me with this, so I'll be as detailed as I can.

This is what I did to download Apache (I'm following specific instructions):

Quote

If you’re running Windows and would like to use Apache, then download the latest stable Windows
binary located within the binaries/win32 directory. Two binary versions are available: one containing
additional SSL-related capabilities and one lacking these capabilities. These binaries are appropriately
named to make clear which is which. I suggest choosing the non-SSL capable version for development
purposes.


What I did:

1) Went to http://httpd.apache.org/download.cgi
2) Clicked version 2.4.3 (the latest stable version)
3) Clicked other files
4) Went to binaries
5) Went to win32
6) Downloaded httpd-2.2.22-win32-x86-no_ssl.msi from the most recent date



Downloading PHP:

1) Went to php.net
2) Went to downloads

I was instructed to download the windows zip package.

3) So I went to Windows 5.4.6 (current stable) binaries and source
4) Downloaded the VC9 x86 Thread Safe (2012-Aug-15 22:48:37) zip file.


Here are my instructions for downloading PHP - please tell me if I did something wrong here.

Quote

Building from source on Windows isn’t recommended and isn’t discussed
in this book. Except in very special circumstances, the Windows binary will suit
your needs just fine. This distribution is archived in bzip2 and gzip formats. Keep

in mind that the contents are identical; the different compression formats are just
there for your convenience.
Windows zip package: If you plan to use PHP in conjunction with Apache on
Windows, you should download this distribution because it’s the focus of the later
installation instructions.


Installing Apache and PHP:

1) Started the Apache.msi file (not the exact name)
2) Went through the next(s) and such.
3) Filled in the servers with localhost and then my e-mail address
4) Selected 'run as service for all users'
5) Set-up type 'Typical'
6) Destination folder was made to be 'C:\Apache'

Now for the PHP.

1) Unzipped the contents of the .zip file into C:\PHP
2) Went to "C:\apache\conf" and opened httpd.conf for editing.
3) Added these lines: 'LoadModule php_module c:/php/php5apache2_2.dll
AddType application/x-httpd-php .php
PHPIniDir "c:\php"'

I tried adding them almost anywhere, but whenever I put them in the Apache file, the server won't start.

4) Here's a part I may have failed at:

Quote

Rename the php.ini-dist file to php.ini and save it to the C:\php directory (as
of PHP 5.3.0, the INI files have been reorganized and renamed as php.ini-development
and php.ini-production, so if you are running 5.3+ you should
rename one of these as php.ini depending upon your situation). The php.ini
file contains hundreds of directives that are responsible for tweaking PHP’s
behavior. The “Configuring PHP” section examines php.ini’s purpose and
contents in detail. Also note that there is another default configuration file at
your disposal, php.ini-recommended. This file sets various nonstandard settings
and is intended to better secure and optimize your installation, although this
configuration may not be fully compatible with some of the legacy
applications. Consider using this file in lieu of php.ini-dist.


For the record, I didn't have a php.ini-dist file. As the instructions mention.

Another thing that struck me as odd was that I did not have a php.ini-recommended file.

But what I did do was change the php.ini-development file's name to php.ini, and same for production (one at a time) and attempt to restart the server, no luck.

Does anyone know what the problem is?

This post has been edited by Tenderfoot: 22 August 2012 - 03:10 AM


Is This A Good Question/Topic? 0
  • +

Replies To: Setting up Apache Server and PHP (Windows 7 Ultimate 64-bit)

#2 creativecoding  Icon User is offline

  • Hash != Encryption
  • member icon


Reputation: 926
  • View blog
  • Posts: 3,205
  • Joined: 19-January 10

Re: Setting up Apache Server and PHP (Windows 7 Ultimate 64-bit)

Posted 22 August 2012 - 05:46 AM

I don't know what the solution to your problem is, but I can say that for Windows testing it's much easier (and better, imo) to use one of the pre-setup tools and such. XAMPP is great and VERY simply, I recommend it to starters. WAMP provides a great interface I think and it gives you the ability to switch Apache/PHP ini values at a click of a button (which is VERY useful).

If you can't find the solution to your problem I would advice you use either one of those programs.
Was This Post Helpful? 2
  • +
  • -

#3 JackOfAllTrades  Icon User is offline

  • Saucy!
  • member icon

Reputation: 6062
  • View blog
  • Posts: 23,514
  • Joined: 23-August 08

Re: Setting up Apache Server and PHP (Windows 7 Ultimate 64-bit)

Posted 22 August 2012 - 06:04 AM

Alternatively, where you're using Windows 7 Ultimate, you can use the Windows web server, IIS, with PHP. Microsoft has a site dedicated to this.
Was This Post Helpful? 1
  • +
  • -

#4 no2pencil  Icon User is online

  • Toubabo Koomi
  • member icon

Reputation: 5303
  • View blog
  • Posts: 27,195
  • Joined: 10-May 07

Re: Setting up Apache Server and PHP (Windows 7 Ultimate 64-bit)

Posted 22 August 2012 - 06:10 AM

Topic has nothing to do with PHP (as indicated by the subject) : Moved to Web Servers & Hosting.

View PostTenderfoot, on 22 August 2012 - 06:08 AM, said:

I tried adding them almost anywhere, but whenever I put them in the Apache file, the server won't start.

This sounds like your problem. Can you post the httpd.conf file? There are specific areas that you need to add the type & load the library file, as some of the file is written in an xml like fashion & you need to adhere to open & end areas.
Was This Post Helpful? 1
  • +
  • -

#5 Tenderfoot  Icon User is offline

  • D.I.C Head
  • member icon

Reputation: 11
  • View blog
  • Posts: 160
  • Joined: 21-March 12

Re: Setting up Apache Server and PHP (Windows 7 Ultimate 64-bit)

Posted 22 August 2012 - 06:53 AM

View Postno2pencil, on 22 August 2012 - 06:10 AM, said:

Topic has nothing to do with PHP (as indicated by the subject) : Moved to Web Servers & Hosting.

View PostTenderfoot, on 22 August 2012 - 06:08 AM, said:

I tried adding them almost anywhere, but whenever I put them in the Apache file, the server won't start.

This sounds like your problem. Can you post the httpd.conf file? There are specific areas that you need to add the type & load the library file, as some of the file is written in an xml like fashion & you need to adhere to open & end areas.


I'm setting this up for a class where they specifically ask you to set up Apache & PHP in this manner. I've up-voted all of your replies however.

Here's the httpd.conf file:

#
# This is the main Apache HTTP server configuration file.  It contains the
# configuration directives that give the server its instructions.
# See <URL:http://httpd.apache.org/docs/2.2> for detailed information.
# In particular, see 
# <URL:http://httpd.apache.org/docs/2.2/mod/directives.html>
# for a discussion of each configuration directive.
#
# Do NOT simply read the instructions in here without understanding
# what they do.  They're here only as hints or reminders.  If you are unsure
# consult the online docs. You have been warned.  
#
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path.  If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so "logs/foo.log"
# with ServerRoot set to "C:/apache" will be interpreted by the
# server as "C:/apache/logs/foo.log".
#
# NOTE: Where filenames are specified, you must use forward slashes
# instead of backslashes (e.g., "c:/apache" instead of "c:\apache").
# If a drive letter is omitted, the drive on which httpd.exe is located
# will be used by default.  It is recommended that you always supply
# an explicit drive letter in absolute paths to avoid confusion.

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# Do not add a slash at the end of the directory path.  If you point
# ServerRoot at a non-local disk, be sure to point the LockFile directive
# at a local disk.  If you wish to share the same ServerRoot for multiple
# httpd daemons, you will need to change at least LockFile and PidFile.
#
ServerRoot "C:/apache"

#
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the <VirtualHost>
# directive.
#
# Change this to Listen on specific IP addresses as shown below to 
# prevent Apache from glomming onto all bound IP addresses.
#
#Listen 12.34.56.78:80
Listen 80

#
# Dynamic Shared Object (DSO) Support
#
# To be able to use the functionality of a module which was built as a DSO you
# have to place corresponding `LoadModule' lines at this location so the
# directives contained in it are actually available _before_ they are used.
# Statically compiled modules (those listed by `httpd -l') do not need
# to be loaded here.
#
# Example:
# LoadModule foo_module modules/mod_foo.so
#
LoadModule actions_module modules/mod_actions.so
LoadModule alias_module modules/mod_alias.so
LoadModule asis_module modules/mod_asis.so
LoadModule auth_basic_module modules/mod_auth_basic.so
#LoadModule auth_digest_module modules/mod_auth_digest.so
#LoadModule authn_alias_module modules/mod_authn_alias.so
#LoadModule authn_anon_module modules/mod_authn_anon.so
#LoadModule authn_dbd_module modules/mod_authn_dbd.so
#LoadModule authn_dbm_module modules/mod_authn_dbm.so
LoadModule authn_default_module modules/mod_authn_default.so
LoadModule authn_file_module modules/mod_authn_file.so
#LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
#LoadModule authz_dbm_module modules/mod_authz_dbm.so
LoadModule authz_default_module modules/mod_authz_default.so
LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
LoadModule authz_host_module modules/mod_authz_host.so
#LoadModule authz_owner_module modules/mod_authz_owner.so
LoadModule authz_user_module modules/mod_authz_user.so
LoadModule autoindex_module modules/mod_autoindex.so
#LoadModule cache_module modules/mod_cache.so
#LoadModule cern_meta_module modules/mod_cern_meta.so
LoadModule cgi_module modules/mod_cgi.so
#LoadModule charset_lite_module modules/mod_charset_lite.so
#LoadModule dav_module modules/mod_dav.so
#LoadModule dav_fs_module modules/mod_dav_fs.so
#LoadModule dav_lock_module modules/mod_dav_lock.so
#LoadModule dbd_module modules/mod_dbd.so
#LoadModule deflate_module modules/mod_deflate.so
LoadModule dir_module modules/mod_dir.so
#LoadModule disk_cache_module modules/mod_disk_cache.so
#LoadModule dumpio_module modules/mod_dumpio.so
LoadModule env_module modules/mod_env.so
#LoadModule expires_module modules/mod_expires.so
#LoadModule ext_filter_module modules/mod_ext_filter.so
#LoadModule file_cache_module modules/mod_file_cache.so
#LoadModule filter_module modules/mod_filter.so
#LoadModule headers_module modules/mod_headers.so
#LoadModule ident_module modules/mod_ident.so
#LoadModule imagemap_module modules/mod_imagemap.so
LoadModule include_module modules/mod_include.so
#LoadModule info_module modules/mod_info.so
LoadModule isapi_module modules/mod_isapi.so
#LoadModule ldap_module modules/mod_ldap.so
#LoadModule logio_module modules/mod_logio.so
LoadModule log_config_module modules/mod_log_config.so
#LoadModule log_forensic_module modules/mod_log_forensic.so
#LoadModule mem_cache_module modules/mod_mem_cache.so
LoadModule mime_module modules/mod_mime.so
#LoadModule mime_magic_module modules/mod_mime_magic.so
LoadModule negotiation_module modules/mod_negotiation.so
#LoadModule proxy_module modules/mod_proxy.so
#LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
#LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
#LoadModule proxy_connect_module modules/mod_proxy_connect.so
#LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
#LoadModule proxy_http_module modules/mod_proxy_http.so
#LoadModule proxy_scgi_module modules/mod_proxy_scgi.so
#LoadModule reqtimeout_module modules/mod_reqtimeout.so
#LoadModule rewrite_module modules/mod_rewrite.so
LoadModule setenvif_module modules/mod_setenvif.so
#LoadModule speling_module modules/mod_speling.so
#LoadModule ssl_module modules/mod_ssl.so
#LoadModule status_module modules/mod_status.so
#LoadModule substitute_module modules/mod_substitute.so
#LoadModule unique_id_module modules/mod_unique_id.so
#LoadModule userdir_module modules/mod_userdir.so
#LoadModule usertrack_module modules/mod_usertrack.so
#LoadModule version_module modules/mod_version.so
#LoadModule vhost_alias_module modules/mod_vhost_alias.so
[b]LoadModule php_module c:/php/php5apache2_2.dll
AddType application/x-httpd-php .php
PHPIniDir "c:\php"[/b]

<IfModule !mpm_netware_module>
<IfModule !mpm_winnt_module>
#
# If you wish httpd to run as a different user or group, you must run
# httpd as root initially and it will switch.  
#
# User/Group: The name (or #number) of the user/group to run httpd as.
# It is usually good practice to create a dedicated user and group for
# running httpd, as with most system services.
#
User daemon
Group daemon

</IfModule>
</IfModule>

# 'Main' server configuration
#
# The directives in this section set up the values used by the 'main'
# server, which responds to any requests that aren't handled by a
# <VirtualHost> definition.  These values also provide defaults for
# any <VirtualHost> containers you may define later in the file.
#
# All of these directives may appear inside <VirtualHost> containers,
# in which case these default settings will be overridden for the
# virtual host being defined.
#

#
# ServerAdmin: Your address, where problems with the server should be
# e-mailed.  This address appears on some server-generated pages, such
# as error documents.  e.g. admin@your-domain.com
#
ServerAdmin ragnarbr1992@gmail.com

#
# ServerName gives the name and port that the server uses to identify itself.
# This can often be determined automatically, but we recommend you specify
# it explicitly to prevent problems during startup.
#
# If your host doesn't have a registered DNS name, enter its IP address here.
#
#ServerName localhost:80

#
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
#
DocumentRoot "C:/apache/htdocs"

#
# Each directory to which Apache has access can be configured with respect
# to which services and features are allowed and/or disabled in that
# directory (and its subdirectories). 
#
# First, we configure the "default" to be a very restrictive set of 
# features.  
#
<Directory />
    Options FollowSymLinks
    AllowOverride None
    Order deny,allow
    Deny from all
</Directory>

#
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
#

#
# This should be changed to whatever you set DocumentRoot to.
#
<Directory "C:/apache/htdocs">
    #
    # Possible values for the Options directive are "None", "All",
    # or any combination of:
    #   Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
    #
    # Note that "MultiViews" must be named *explicitly* --- "Options All"
    # doesn't give it to you.
    #
    # The Options directive is both complicated and important.  Please see
    # http://httpd.apache.org/docs/2.2/mod/core.html#options
    # for more information.
    #
    Options Indexes FollowSymLinks

    #
    # AllowOverride controls what directives may be placed in .htaccess files.
    # It can be "All", "None", or any combination of the keywords:
    #   Options FileInfo AuthConfig Limit
    #
    AllowOverride None

    #
    # Controls who can get stuff from this server.
    #
    Order allow,deny
    Allow from all

</Directory>

#
# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
#
<IfModule dir_module>
    DirectoryIndex index.html
</IfModule>

#
# The following lines prevent .htaccess and .htpasswd files from being 
# viewed by Web clients. 
#
<FilesMatch "^\.ht">
    Order allow,deny
    Deny from all
    Satisfy All
</FilesMatch>

#
# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here.  If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
ErrorLog "logs/error.log"

#
# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
#
LogLevel warn

<IfModule log_config_module>
    #
    # The following directives define some format nicknames for use with
    # a CustomLog directive (see below).
    #
    LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
    LogFormat "%h %l %u %t \"%r\" %>s %b" common

    <IfModule logio_module>
      # You need to enable mod_logio.c to use %I and %O
      LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio
    </IfModule>

    #
    # The location and format of the access logfile (Common Logfile Format).
    # If you do not define any access logfiles within a <VirtualHost>
    # container, they will be logged here.  Contrariwise, if you *do*
    # define per-<VirtualHost> access logfiles, transactions will be
    # logged therein and *not* in this file.
    #
    CustomLog "logs/access.log" common

    #
    # If you prefer a logfile with access, agent, and referer information
    # (Combined Logfile Format) you can use the following directive.
    #
    #CustomLog "logs/access.log" combined
</IfModule>

<IfModule alias_module>
    #
    # Redirect: Allows you to tell clients about documents that used to 
    # exist in your server's namespace, but do not anymore. The client 
    # will make a new request for the document at its new location.
    # Example:
    # Redirect permanent /foo http://localhost/bar

    #
    # Alias: Maps web paths into filesystem paths and is used to
    # access content that does not live under the DocumentRoot.
    # Example:
    # Alias /webpath /full/filesystem/path
    #
    # If you include a trailing / on /webpath then the server will
    # require it to be present in the URL.  You will also likely
    # need to provide a <Directory> section to allow access to
    # the filesystem path.

    #
    # ScriptAlias: This controls which directories contain server scripts. 
    # ScriptAliases are essentially the same as Aliases, except that
    # documents in the target directory are treated as applications and
    # run by the server when requested rather than as documents sent to the
    # client.  The same rules about trailing "/" apply to ScriptAlias
    # directives as to Alias.
    #
    ScriptAlias /cgi-bin/ "C:/apache/cgi-bin/"

</IfModule>

<IfModule cgid_module>
    #
    # ScriptSock: On threaded servers, designate the path to the UNIX
    # socket used to communicate with the CGI daemon of mod_cgid.
    #
    #Scriptsock logs/cgisock
</IfModule>

#
# "C:/apache/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
#
<Directory "C:/apache/cgi-bin">
    AllowOverride None
    Options None
    Order allow,deny
    Allow from all
</Directory>

#
# DefaultType: the default MIME type the server will use for a document
# if it cannot otherwise determine one, such as from filename extensions.
# If your server contains mostly text or HTML documents, "text/plain" is
# a good value.  If most of your content is binary, such as applications
# or images, you may want to use "application/octet-stream" instead to
# keep browsers from trying to display binary files as though they are
# text.
#
DefaultType text/plain

<IfModule mime_module>
    #
    # TypesConfig points to the file containing the list of mappings from
    # filename extension to MIME-type.
    #
    TypesConfig conf/mime.types

    #
    # AddType allows you to add to or override the MIME configuration
    # file specified in TypesConfig for specific file types.
    #
    #AddType application/x-gzip .tgz
    #
    # AddEncoding allows you to have certain browsers uncompress
    # information on the fly. Note: Not all browsers support this.
    #
    #AddEncoding x-compress .Z
    #AddEncoding x-gzip .gz .tgz
    #
    # If the AddEncoding directives above are commented-out, then you
    # probably should define those extensions to indicate media types:
    #
    AddType application/x-compress .Z
    AddType application/x-gzip .gz .tgz

    #
    # AddHandler allows you to map certain file extensions to "handlers":
    # actions unrelated to filetype. These can be either built into the server
    # or added with the Action directive (see below)
    #
    # To use CGI scripts outside of ScriptAliased directories:
    # (You will also need to add "ExecCGI" to the "Options" directive.)
    #
    #AddHandler cgi-script .cgi

    # For type maps (negotiated resources):
    #AddHandler type-map var

    #
    # Filters allow you to process content before it is sent to the client.
    #
    # To parse .shtml files for server-side includes (SSI):
    # (You will also need to add "Includes" to the "Options" directive.)
    #
    #AddType text/html .shtml
    #AddOutputFilter INCLUDES .shtml
</IfModule>

#
# The mod_mime_magic module allows the server to use various hints from the
# contents of the file itself to determine its type.  The MIMEMagicFile
# directive tells the module where the hint definitions are located.
#
#MIMEMagicFile conf/magic

#
# Customizable error responses come in three flavors:
# 1) plain text 2) local redirects 3) external redirects
#
# Some examples:
#ErrorDocument 500 "The server made a boo boo."
#ErrorDocument 404 /missing.html
#ErrorDocument 404 "/cgi-bin/missing_handler.pl"
#ErrorDocument 402 http://localhost/subscription_info.html
#

#
# MaxRanges: Maximum number of Ranges in a request before
# returning the entire resource, or one of the special
# values 'default', 'none' or 'unlimited'.
# Default setting is to accept 200 Ranges.
#MaxRanges unlimited

#
# EnableMMAP and EnableSendfile: On systems that support it, 
# memory-mapping or the sendfile syscall is used to deliver
# files.  This usually improves server performance, but must
# be turned off when serving from networked-mounted 
# filesystems or if support for these functions is otherwise
# broken on your system.
#
#EnableMMAP off
#EnableSendfile off

# Supplemental configuration
#
# The configuration files in the conf/extra/ directory can be 
# included to add extra features or to modify the default configuration of 
# the server, or you may simply copy their contents here and change as 
# necessary.

# Server-pool management (MPM specific)
#Include conf/extra/httpd-mpm.conf

# Multi-language error messages
#Include conf/extra/httpd-multilang-errordoc.conf

# Fancy directory listings
#Include conf/extra/httpd-autoindex.conf

# Language settings
#Include conf/extra/httpd-languages.conf

# User home directories
#Include conf/extra/httpd-userdir.conf

# Real-time info on requests and configuration
#Include conf/extra/httpd-info.conf

# Virtual hosts
#Include conf/extra/httpd-vhosts.conf

# Local access to the Apache HTTP Server Manual
#Include conf/extra/httpd-manual.conf

# Distributed authoring and versioning (WebDAV)
#Include conf/extra/httpd-dav.conf

# Various default settings
#Include conf/extra/httpd-default.conf

# Secure (SSL/TLS) connections
#Include conf/extra/httpd-ssl.conf
#
# Note: The following must must be present to support
#       starting without SSL on platforms with no /dev/random equivalent
#       but a statically compiled-in mod_ssl.
#
<IfModule ssl_module>
SSLRandomSeed startup builtin
SSLRandomSeed connect builtin
</IfModule>



I put the lines I added in bold.
Was This Post Helpful? 0
  • +
  • -

#6 Tenderfoot  Icon User is offline

  • D.I.C Head
  • member icon

Reputation: 11
  • View blog
  • Posts: 160
  • Joined: 21-March 12

Re: Setting up Apache Server and PHP (Windows 7 Ultimate 64-bit)

Posted 22 August 2012 - 07:22 AM

Hope some of you guys read this forum. ^^
Was This Post Helpful? 0
  • +
  • -

#7 no2pencil  Icon User is online

  • Toubabo Koomi
  • member icon

Reputation: 5303
  • View blog
  • Posts: 27,195
  • Joined: 10-May 07

Re: Setting up Apache Server and PHP (Windows 7 Ultimate 64-bit)

Posted 22 August 2012 - 08:16 AM

Try the following :

#
# This is the main Apache HTTP server configuration file.  It contains the
# configuration directives that give the server its instructions.
# See <URL:http://httpd.apache.org/docs/2.2> for detailed information.
# In particular, see 
# <URL:http://httpd.apache.org/docs/2.2/mod/directives.html>
# for a discussion of each configuration directive.
#
# Do NOT simply read the instructions in here without understanding
# what they do.  They're here only as hints or reminders.  If you are unsure
# consult the online docs. You have been warned.  
#
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path.  If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so "logs/foo.log"
# with ServerRoot set to "C:/apache" will be interpreted by the
# server as "C:/apache/logs/foo.log".
#
# NOTE: Where filenames are specified, you must use forward slashes
# instead of backslashes (e.g., "c:/apache" instead of "c:\apache").
# If a drive letter is omitted, the drive on which httpd.exe is located
# will be used by default.  It is recommended that you always supply
# an explicit drive letter in absolute paths to avoid confusion.

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# Do not add a slash at the end of the directory path.  If you point
# ServerRoot at a non-local disk, be sure to point the LockFile directive
# at a local disk.  If you wish to share the same ServerRoot for multiple
# httpd daemons, you will need to change at least LockFile and PidFile.
#
ServerRoot "C:/apache"

#
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the <VirtualHost>
# directive.
#
# Change this to Listen on specific IP addresses as shown below to 
# prevent Apache from glomming onto all bound IP addresses.
#
#Listen 12.34.56.78:80
Listen 80

#
# Dynamic Shared Object (DSO) Support
#
# To be able to use the functionality of a module which was built as a DSO you
# have to place corresponding `LoadModule' lines at this location so the
# directives contained in it are actually available _before_ they are used.
# Statically compiled modules (those listed by `httpd -l') do not need
# to be loaded here.
#
# Example:
# LoadModule foo_module modules/mod_foo.so
#
LoadModule actions_module modules/mod_actions.so
LoadModule alias_module modules/mod_alias.so
LoadModule asis_module modules/mod_asis.so
LoadModule auth_basic_module modules/mod_auth_basic.so
#LoadModule auth_digest_module modules/mod_auth_digest.so
#LoadModule authn_alias_module modules/mod_authn_alias.so
#LoadModule authn_anon_module modules/mod_authn_anon.so
#LoadModule authn_dbd_module modules/mod_authn_dbd.so
#LoadModule authn_dbm_module modules/mod_authn_dbm.so
LoadModule authn_default_module modules/mod_authn_default.so
LoadModule authn_file_module modules/mod_authn_file.so
#LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
#LoadModule authz_dbm_module modules/mod_authz_dbm.so
LoadModule authz_default_module modules/mod_authz_default.so
LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
LoadModule authz_host_module modules/mod_authz_host.so
#LoadModule authz_owner_module modules/mod_authz_owner.so
LoadModule authz_user_module modules/mod_authz_user.so
LoadModule autoindex_module modules/mod_autoindex.so
#LoadModule cache_module modules/mod_cache.so
#LoadModule cern_meta_module modules/mod_cern_meta.so
LoadModule cgi_module modules/mod_cgi.so
#LoadModule charset_lite_module modules/mod_charset_lite.so
#LoadModule dav_module modules/mod_dav.so
#LoadModule dav_fs_module modules/mod_dav_fs.so
#LoadModule dav_lock_module modules/mod_dav_lock.so
#LoadModule dbd_module modules/mod_dbd.so
#LoadModule deflate_module modules/mod_deflate.so
LoadModule dir_module modules/mod_dir.so
#LoadModule disk_cache_module modules/mod_disk_cache.so
#LoadModule dumpio_module modules/mod_dumpio.so
LoadModule env_module modules/mod_env.so
#LoadModule expires_module modules/mod_expires.so
#LoadModule ext_filter_module modules/mod_ext_filter.so
#LoadModule file_cache_module modules/mod_file_cache.so
#LoadModule filter_module modules/mod_filter.so
#LoadModule headers_module modules/mod_headers.so
#LoadModule ident_module modules/mod_ident.so
#LoadModule imagemap_module modules/mod_imagemap.so
LoadModule include_module modules/mod_include.so
#LoadModule info_module modules/mod_info.so
LoadModule isapi_module modules/mod_isapi.so
#LoadModule ldap_module modules/mod_ldap.so
#LoadModule logio_module modules/mod_logio.so
LoadModule log_config_module modules/mod_log_config.so
#LoadModule log_forensic_module modules/mod_log_forensic.so
#LoadModule mem_cache_module modules/mod_mem_cache.so
LoadModule mime_module modules/mod_mime.so
#LoadModule mime_magic_module modules/mod_mime_magic.so
LoadModule negotiation_module modules/mod_negotiation.so
#LoadModule proxy_module modules/mod_proxy.so
#LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
#LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
#LoadModule proxy_connect_module modules/mod_proxy_connect.so
#LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
#LoadModule proxy_http_module modules/mod_proxy_http.so
#LoadModule proxy_scgi_module modules/mod_proxy_scgi.so
#LoadModule reqtimeout_module modules/mod_reqtimeout.so
#LoadModule rewrite_module modules/mod_rewrite.so
LoadModule setenvif_module modules/mod_setenvif.so
#LoadModule speling_module modules/mod_speling.so
#LoadModule ssl_module modules/mod_ssl.so
#LoadModule status_module modules/mod_status.so
#LoadModule substitute_module modules/mod_substitute.so
#LoadModule unique_id_module modules/mod_unique_id.so
#LoadModule userdir_module modules/mod_userdir.so
#LoadModule usertrack_module modules/mod_usertrack.so
#LoadModule version_module modules/mod_version.so
#LoadModule vhost_alias_module modules/mod_vhost_alias.so
LoadModule php5_module "c:/php/php5apache2.dll"

PHPIniDir "C:/php"

<IfModule !mpm_netware_module>
<IfModule !mpm_winnt_module>
#
# If you wish httpd to run as a different user or group, you must run
# httpd as root initially and it will switch.  
#
# User/Group: The name (or #number) of the user/group to run httpd as.
# It is usually good practice to create a dedicated user and group for
# running httpd, as with most system services.
#
User daemon
Group daemon

</IfModule>
</IfModule>

# 'Main' server configuration
#
# The directives in this section set up the values used by the 'main'
# server, which responds to any requests that aren't handled by a
# <VirtualHost> definition.  These values also provide defaults for
# any <VirtualHost> containers you may define later in the file.
#
# All of these directives may appear inside <VirtualHost> containers,
# in which case these default settings will be overridden for the
# virtual host being defined.
#

#
# ServerAdmin: Your address, where problems with the server should be
# e-mailed.  This address appears on some server-generated pages, such
# as error documents.  e.g. admin@your-domain.com
#
ServerAdmin ragnarbr1992@gmail.com

#
# ServerName gives the name and port that the server uses to identify itself.
# This can often be determined automatically, but we recommend you specify
# it explicitly to prevent problems during startup.
#
# If your host doesn't have a registered DNS name, enter its IP address here.
#
#ServerName localhost:80

#
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
#
DocumentRoot "C:/apache/htdocs"

#
# Each directory to which Apache has access can be configured with respect
# to which services and features are allowed and/or disabled in that
# directory (and its subdirectories). 
#
# First, we configure the "default" to be a very restrictive set of 
# features.  
#
<Directory />
    Options FollowSymLinks
    AllowOverride None
    Order deny,allow
    Deny from all
</Directory>

#
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
#

#
# This should be changed to whatever you set DocumentRoot to.
#
<Directory "C:/apache/htdocs">
    #
    # Possible values for the Options directive are "None", "All",
    # or any combination of:
    #   Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
    #
    # Note that "MultiViews" must be named *explicitly* --- "Options All"
    # doesn't give it to you.
    #
    # The Options directive is both complicated and important.  Please see
    # http://httpd.apache.org/docs/2.2/mod/core.html#options
    # for more information.
    #
    Options Indexes FollowSymLinks

    #
    # AllowOverride controls what directives may be placed in .htaccess files.
    # It can be "All", "None", or any combination of the keywords:
    #   Options FileInfo AuthConfig Limit
    #
    AllowOverride None

    #
    # Controls who can get stuff from this server.
    #
    Order allow,deny
    Allow from all

</Directory>

#
# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
#
<IfModule dir_module>
    DirectoryIndex index.html
</IfModule>

#
# The following lines prevent .htaccess and .htpasswd files from being 
# viewed by Web clients. 
#
<FilesMatch "^\.ht">
    Order allow,deny
    Deny from all
    Satisfy All
</FilesMatch>

#
# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here.  If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
ErrorLog "logs/error.log"

#
# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
#
LogLevel warn

<IfModule log_config_module>
    #
    # The following directives define some format nicknames for use with
    # a CustomLog directive (see below).
    #
    LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
    LogFormat "%h %l %u %t \"%r\" %>s %b" common

    <IfModule logio_module>
      # You need to enable mod_logio.c to use %I and %O
      LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio
    </IfModule>

    #
    # The location and format of the access logfile (Common Logfile Format).
    # If you do not define any access logfiles within a <VirtualHost>
    # container, they will be logged here.  Contrariwise, if you *do*
    # define per-<VirtualHost> access logfiles, transactions will be
    # logged therein and *not* in this file.
    #
    CustomLog "logs/access.log" common

    #
    # If you prefer a logfile with access, agent, and referer information
    # (Combined Logfile Format) you can use the following directive.
    #
    #CustomLog "logs/access.log" combined
</IfModule>

<IfModule alias_module>
    #
    # Redirect: Allows you to tell clients about documents that used to 
    # exist in your server's namespace, but do not anymore. The client 
    # will make a new request for the document at its new location.
    # Example:
    # Redirect permanent /foo http://localhost/bar

    #
    # Alias: Maps web paths into filesystem paths and is used to
    # access content that does not live under the DocumentRoot.
    # Example:
    # Alias /webpath /full/filesystem/path
    #
    # If you include a trailing / on /webpath then the server will
    # require it to be present in the URL.  You will also likely
    # need to provide a <Directory> section to allow access to
    # the filesystem path.

    #
    # ScriptAlias: This controls which directories contain server scripts. 
    # ScriptAliases are essentially the same as Aliases, except that
    # documents in the target directory are treated as applications and
    # run by the server when requested rather than as documents sent to the
    # client.  The same rules about trailing "/" apply to ScriptAlias
    # directives as to Alias.
    #
    ScriptAlias /cgi-bin/ "C:/apache/cgi-bin/"

</IfModule>

<IfModule cgid_module>
    #
    # ScriptSock: On threaded servers, designate the path to the UNIX
    # socket used to communicate with the CGI daemon of mod_cgid.
    #
    #Scriptsock logs/cgisock
</IfModule>

#
# "C:/apache/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
#
<Directory "C:/apache/cgi-bin">
    AllowOverride None
    Options None
    Order allow,deny
    Allow from all
</Directory>

#
# DefaultType: the default MIME type the server will use for a document
# if it cannot otherwise determine one, such as from filename extensions.
# If your server contains mostly text or HTML documents, "text/plain" is
# a good value.  If most of your content is binary, such as applications
# or images, you may want to use "application/octet-stream" instead to
# keep browsers from trying to display binary files as though they are
# text.
#
DefaultType text/plain

<IfModule mime_module>
    #
    # TypesConfig points to the file containing the list of mappings from
    # filename extension to MIME-type.
    #
    TypesConfig conf/mime.types

    #
    # AddType allows you to add to or override the MIME configuration
    # file specified in TypesConfig for specific file types.
    #
    #AddType application/x-gzip .tgz
    #
    # AddEncoding allows you to have certain browsers uncompress
    # information on the fly. Note: Not all browsers support this.
    #
    #AddEncoding x-compress .Z
    #AddEncoding x-gzip .gz .tgz
    #
    # If the AddEncoding directives above are commented-out, then you
    # probably should define those extensions to indicate media types:
    #
    AddType application/x-compress .Z
    AddType application/x-gzip .gz .tgz
    AddType application/x-httpd-php .php

    #
    # AddHandler allows you to map certain file extensions to "handlers":
    # actions unrelated to filetype. These can be either built into the server
    # or added with the Action directive (see below)
    #
    # To use CGI scripts outside of ScriptAliased directories:
    # (You will also need to add "ExecCGI" to the "Options" directive.)
    #
    #AddHandler cgi-script .cgi

    # For type maps (negotiated resources):
    #AddHandler type-map var

    #
    # Filters allow you to process content before it is sent to the client.
    #
    # To parse .shtml files for server-side includes (SSI):
    # (You will also need to add "Includes" to the "Options" directive.)
    #
    #AddType text/html .shtml
    #AddOutputFilter INCLUDES .shtml
</IfModule>

#
# The mod_mime_magic module allows the server to use various hints from the
# contents of the file itself to determine its type.  The MIMEMagicFile
# directive tells the module where the hint definitions are located.
#
#MIMEMagicFile conf/magic

#
# Customizable error responses come in three flavors:
# 1) plain text 2) local redirects 3) external redirects
#
# Some examples:
#ErrorDocument 500 "The server made a boo boo."
#ErrorDocument 404 /missing.html
#ErrorDocument 404 "/cgi-bin/missing_handler.pl"
#ErrorDocument 402 http://localhost/subscription_info.html
#

#
# MaxRanges: Maximum number of Ranges in a request before
# returning the entire resource, or one of the special
# values 'default', 'none' or 'unlimited'.
# Default setting is to accept 200 Ranges.
#MaxRanges unlimited

#
# EnableMMAP and EnableSendfile: On systems that support it, 
# memory-mapping or the sendfile syscall is used to deliver
# files.  This usually improves server performance, but must
# be turned off when serving from networked-mounted 
# filesystems or if support for these functions is otherwise
# broken on your system.
#
#EnableMMAP off
#EnableSendfile off

# Supplemental configuration
#
# The configuration files in the conf/extra/ directory can be 
# included to add extra features or to modify the default configuration of 
# the server, or you may simply copy their contents here and change as 
# necessary.

# Server-pool management (MPM specific)
#Include conf/extra/httpd-mpm.conf

# Multi-language error messages
#Include conf/extra/httpd-multilang-errordoc.conf

# Fancy directory listings
#Include conf/extra/httpd-autoindex.conf

# Language settings
#Include conf/extra/httpd-languages.conf

# User home directories
#Include conf/extra/httpd-userdir.conf

# Real-time info on requests and configuration
#Include conf/extra/httpd-info.conf

# Virtual hosts
#Include conf/extra/httpd-vhosts.conf

# Local access to the Apache HTTP Server Manual
#Include conf/extra/httpd-manual.conf

# Distributed authoring and versioning (WebDAV)
#Include conf/extra/httpd-dav.conf

# Various default settings
#Include conf/extra/httpd-default.conf

# Secure (SSL/TLS) connections
#Include conf/extra/httpd-ssl.conf
#
# Note: The following must must be present to support
#       starting without SSL on platforms with no /dev/random equivalent
#       but a statically compiled-in mod_ssl.
#
<IfModule ssl_module>
SSLRandomSeed startup builtin
SSLRandomSeed connect builtin
</IfModule>


View PostTenderfoot, on 22 August 2012 - 10:22 AM, said:

Hope some of you guys read this forum. ^^

Hope you realize we are not at your beck-&-call. If you want instant service, I'll give you my office number, along with an invoice. ^^
Was This Post Helpful? 1
  • +
  • -

#8 Tenderfoot  Icon User is offline

  • D.I.C Head
  • member icon

Reputation: 11
  • View blog
  • Posts: 160
  • Joined: 21-March 12

Re: Setting up Apache Server and PHP (Windows 7 Ultimate 64-bit)

Posted 22 August 2012 - 08:40 AM

View Postno2pencil, on 22 August 2012 - 08:16 AM, said:

View PostTenderfoot, on 22 August 2012 - 10:22 AM, said:

Hope some of you guys read this forum. ^^

Hope you realize we are not at your beck-&-call. If you want instant service, I'll give you my office number, along with an invoice. ^^


You mean to tell me you're not all here to serve my needs? >.<

I know that, though. I just feared I'd been thrown along with my thread to a deserted forum. But yeah, the main reason for why I placed it in PHP to begin with was because I hoped there would be people there who had possibly experienced the same/ or a similar issue before. Because I know that, when I frequent forums, for instance, I tend to stick only to the forum that interests me the most, especially if there's a vast variety of categories. Anywho, I didn't mean to offend anybody by saying what I said, and I appreciate any/all help I get.

Including your reply - speaking of which - I tried replacing the current httpd.conf file with that one, and I get this error (the same one I've been getting):

Quote

Windows could not start the Apache2.2 on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 1.


But thank you once more for taking the time to reply - I do appreciate it, even if it isn't my beck-&-call. :chinese:
Was This Post Helpful? 0
  • +
  • -

#9 no2pencil  Icon User is online

  • Toubabo Koomi
  • member icon

Reputation: 5303
  • View blog
  • Posts: 27,195
  • Joined: 10-May 07

Re: Setting up Apache Server and PHP (Windows 7 Ultimate 64-bit)

Posted 22 August 2012 - 08:43 AM

View PostTenderfoot, on 22 August 2012 - 11:40 AM, said:

Including your reply - speaking of which - I tried replacing the current httpd.conf file with that one, and I get this error (the same one I've been getting):

Quote

Windows could not start the Apache2.2 on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 1.


But thank you once more for taking the time to reply - I do appreciate it, even if it isn't my beck-&-call. :chinese:

So it says "For more information, review the System Event Log." & you post here for help. I can't speak for the others here, but I am unable to read the system event log because it is on your machine. Can you take a look at what it says, &/or provide it here?
Was This Post Helpful? 0
  • +
  • -

#10 Tenderfoot  Icon User is offline

  • D.I.C Head
  • member icon

Reputation: 11
  • View blog
  • Posts: 160
  • Joined: 21-March 12

Re: Setting up Apache Server and PHP (Windows 7 Ultimate 64-bit)

Posted 22 August 2012 - 09:04 AM

View Postno2pencil, on 22 August 2012 - 08:43 AM, said:

View PostTenderfoot, on 22 August 2012 - 11:40 AM, said:

Including your reply - speaking of which - I tried replacing the current httpd.conf file with that one, and I get this error (the same one I've been getting):

Quote

Windows could not start the Apache2.2 on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 1.


But thank you once more for taking the time to reply - I do appreciate it, even if it isn't my beck-&-call. :chinese:

So it says "For more information, review the System Event Log." & you post here for help. I can't speak for the others here, but I am unable to read the system event log because it is on your machine. Can you take a look at what it says, &/or provide it here?


Well - mostly because I assumed it was me screwing up with the input/file renaming or something like that. Thing is, when I got it to work - by putting #'s before the three lines - The PHP test only showed up as text. Or well. No PHP was run that day. But then again, the # I assume is for commenting and those three lines are pretty important. So when I attempted to start Apache with the lines and it didn't run, I assumed it was because the lines were somehow wrong, or because I renamed the wrong file. As opposed to it being some sort of a system error.

On top of that, the message states that if it's not a Microsoft service (which I assume it isn't?) I need to contact the service vendor. And all in all I'm not all that good with system logs.

The log is below in the quote (XML):

Quote

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
<EventID Qualifiers="49152">7024</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2012-08-22T15:54:59.187832600Z" />
<EventRecordID>43558</EventRecordID>
<Correlation />
<Execution ProcessID="708" ThreadID="3128" />
<Channel>System</Channel>
<Computer>My-PC</Computer>
<Security />
</System>
- <EventData>
<Data Name="param1">Apache2.2</Data>
<Data Name="param2">%%1</Data>
</EventData>
</Event>


Thing is, I have no idea what to do with that information - and I still assume that this has more to do with the files/renaming/line input. Then again I'm not very experienced with this.

This post has been edited by Tenderfoot: 22 August 2012 - 09:06 AM

Was This Post Helpful? 0
  • +
  • -

#11 ToshNeox  Icon User is offline

  • D.I.C Head

Reputation: 8
  • View blog
  • Posts: 100
  • Joined: 10-December 11

Re: Setting up Apache Server and PHP (Windows 7 Ultimate 64-bit)

Posted 22 August 2012 - 09:17 AM

As others have said, I think you should just use WAMP (or MAMP for Mac / LAMP for Linux), and just uninstall all the stuff you have going on.

When I installed WAMP, I had a fully featured up-to-date Apache webserver, running with PHP and MySQL, along with pre-installed and working phpMyAdmin.

The only problems I've ever had with WAMP is when I messed with it trying to enable CURL (still, I only get 1 error message and it starts and runs fine) and when trying to manually update PHP. Other than that, it's golden.

Also, as creativecoding said, WAMP's menus are extremely efficient and are real easy to use.

The only thing good I see coming of your manually built setup, is that you will learn how to fix the error(s), should you ever have them again in the future.
Was This Post Helpful? 1
  • +
  • -

#12 no2pencil  Icon User is online

  • Toubabo Koomi
  • member icon

Reputation: 5303
  • View blog
  • Posts: 27,195
  • Joined: 10-May 07

Re: Setting up Apache Server and PHP (Windows 7 Ultimate 64-bit)

Posted 22 August 2012 - 09:29 AM

View PostTenderfoot, on 22 August 2012 - 12:04 PM, said:

Thing is, when I got it to work - by putting #'s before the three lines - The PHP test only showed up as text.

This is because putting the #'s in front comments out those instructions. It's essentially the same as not having them there. Because you request a php file, & apache doesn't know to send a php file to the php engine, it just hands the file over & doesn't process it. Thus you get text.

View PostTenderfoot, on 22 August 2012 - 12:04 PM, said:

On top of that, the message states that if it's not a Microsoft service

You are looking at the Microsoft error messages. You need to find the Apache logs. On a Linux/Unix system these are in /var/logs/httpd/. I don't know where they are stored on a Microsoft server. Find that location in the documentation, find those logs, & I'm fairly certain you will find your error & fix apache.

& for the record, wamp is great & all. But if it's in your project instructions, I will continue to assist you with this & get it running. I've never installed a wamp or lamp before, & I really don't intend to.
Was This Post Helpful? 1
  • +
  • -

#13 Tenderfoot  Icon User is offline

  • D.I.C Head
  • member icon

Reputation: 11
  • View blog
  • Posts: 160
  • Joined: 21-March 12

Re: Setting up Apache Server and PHP (Windows 7 Ultimate 64-bit)

Posted 22 August 2012 - 11:43 AM

View Postno2pencil, on 22 August 2012 - 09:29 AM, said:

You are looking at the Microsoft error messages. You need to find the Apache logs. On a Linux/Unix system these are in /var/logs/httpd/. I don't know where they are stored on a Microsoft server. Find that location in the documentation, find those logs, & I'm fairly certain you will find your error & fix apache.

& for the record, wamp is great & all. But if it's in your project instructions, I will continue to assist you with this & get it running. I've never installed a wamp or lamp before, & I really don't intend to.


I found some logs under 'C:\apache\logs'. These were the following three:

  • access.log
  • error.log
  • install.log


I assumed it might be the error one, but after opening it, I'm still not sure what to make of it.

The contents I'll place in the quote below:

Quote

Starting the Apache2.2 service
The Apache2.2 service is running.
rmine the server's fully qualified domain name, using 5.189.164.137 for ServerName
[Tue Aug 21 20:05:22 2012] [notice] Apache/2.2.22 (Win32) configured -- resuming normal operations
[Tue Aug 21 20:05:22 2012] [notice] Server built: Jan 28 2012 11:16:39
[Tue Aug 21 20:05:22 2012] [notice] Parent: Created child process 5472
httpd.exe: Could not reliably determine the server's fully qualified domain name, using 5.189.164.137 for ServerName
httpd.exe: Could not reliably determine the server's fully qualified domain name, using 5.189.164.137 for ServerName
[Tue Aug 21 20:05:22 2012] [notice] Child 5472: Child process is running
[Tue Aug 21 20:05:22 2012] [notice] Child 5472: Acquired the start mutex.
[Tue Aug 21 20:05:22 2012] [notice] Child 5472: Starting 64 worker threads.
[Tue Aug 21 20:05:22 2012] [notice] Child 5472: Starting thread to listen on port 80.
[Tue Aug 21 20:18:24 2012] [notice] Parent: Received shutdown signal -- Shutting down the server.
[Tue Aug 21 20:18:24 2012] [notice] Child 5472: Exit event signaled. Child process is ending.
[Tue Aug 21 20:18:25 2012] [notice] Child 5472: Released the start mutex
[Tue Aug 21 20:18:26 2012] [notice] Child 5472: All worker threads have exited.
[Tue Aug 21 20:18:26 2012] [notice] Child 5472: Child process is exiting
[Tue Aug 21 20:18:26 2012] [notice] Parent: Child process exited successfully.
httpd.exe: Could not reliably determine the server's fully qualified domain name, using 5.189.164.137 for ServerName
[Tue Aug 21 20:20:21 2012] [notice] Apache/2.2.22 (Win32) configured -- resuming normal operations
[Tue Aug 21 20:20:21 2012] [notice] Server built: Jan 28 2012 11:16:39
[Tue Aug 21 20:20:21 2012] [notice] Parent: Created child process 3588
httpd.exe: Could not reliably determine the server's fully qualified domain name, using 5.189.164.137 for ServerName
httpd.exe: Could not reliably determine the server's fully qualified domain name, using 5.189.164.137 for ServerName
[Tue Aug 21 20:20:21 2012] [notice] Child 3588: Child process is running
[Tue Aug 21 20:20:21 2012] [notice] Child 3588: Acquired the start mutex.
[Tue Aug 21 20:20:21 2012] [notice] Child 3588: Starting 64 worker threads.
[Tue Aug 21 20:20:21 2012] [notice] Child 3588: Starting thread to listen on port 80.
[Tue Aug 21 20:22:39 2012] [error] [client 127.0.0.1] File does not exist: C:/Apache/htdocs/favicon.ico
[Tue Aug 21 20:24:27 2012] [error] [client 127.0.0.1] File does not exist: C:/Apache/htdocs/favicon.ico
[Tue Aug 21 20:25:55 2012] [notice] Parent: Received shutdown signal -- Shutting down the server.
[Tue Aug 21 20:25:55 2012] [notice] Child 3588: Exit event signaled. Child process is ending.
[Tue Aug 21 20:25:56 2012] [notice] Child 3588: Released the start mutex
[Tue Aug 21 20:25:57 2012] [notice] Child 3588: All worker threads have exited.
[Tue Aug 21 20:25:57 2012] [notice] Child 3588: Child process is exiting
[Tue Aug 21 20:25:57 2012] [notice] Parent: Child process exited successfully.
httpd.exe: Could not reliably determine the server's fully qualified domain name, using 5.189.164.137 for ServerName
[Tue Aug 21 20:25:57 2012] [notice] Apache/2.2.22 (Win32) configured -- resuming normal operations
[Tue Aug 21 20:25:57 2012] [notice] Server built: Jan 28 2012 11:16:39
[Tue Aug 21 20:25:57 2012] [notice] Parent: Created child process 1908
httpd.exe: Could not reliably determine the server's fully qualified domain name, using 5.189.164.137 for ServerName
httpd.exe: Could not reliably determine the server's fully qualified domain name, using 5.189.164.137 for ServerName
[Tue Aug 21 20:25:57 2012] [notice] Child 1908: Child process is running
[Tue Aug 21 20:25:57 2012] [notice] Child 1908: Acquired the start mutex.
[Tue Aug 21 20:25:57 2012] [notice] Child 1908: Starting 64 worker threads.
[Tue Aug 21 20:25:57 2012] [notice] Child 1908: Starting thread to listen on port 80.
[Tue Aug 21 20:26:07 2012] [error] [client 127.0.0.1] File does not exist: C:/Apache/htdocs/favicon.ico
[Tue Aug 21 20:31:08 2012] [notice] Parent: Received shutdown signal -- Shutting down the server.
[Tue Aug 21 20:31:08 2012] [notice] Child 1908: Exit event signaled. Child process is ending.
[Tue Aug 21 20:31:09 2012] [notice] Child 1908: Released the start mutex
[Tue Aug 21 20:31:10 2012] [notice] Child 1908: All worker threads have exited.
[Tue Aug 21 20:31:10 2012] [notice] Child 1908: Child process is exiting
[Tue Aug 21 20:31:10 2012] [notice] Parent: Child process exited successfully.


Thing is, it's not August 21 and it contains no errors from the day today. So these must go somewhere else, perhaps. I'll keep looking unless this is it. Thanks for taking your time to help me though.
Was This Post Helpful? 0
  • +
  • -

#14 no2pencil  Icon User is online

  • Toubabo Koomi
  • member icon

Reputation: 5303
  • View blog
  • Posts: 27,195
  • Joined: 10-May 07

Re: Setting up Apache Server and PHP (Windows 7 Ultimate 64-bit)

Posted 22 August 2012 - 06:39 PM

That doesn't look like an error log. What are the file dates?
Was This Post Helpful? 1
  • +
  • -

#15 Tenderfoot  Icon User is offline

  • D.I.C Head
  • member icon

Reputation: 11
  • View blog
  • Posts: 160
  • Joined: 21-March 12

Re: Setting up Apache Server and PHP (Windows 7 Ultimate 64-bit)

Posted 23 August 2012 - 03:15 AM

I found a few lines I tried replacing the old ones with somewhere online. I only edited the path.

#BEGIN PHP INSTALLER EDITS - REMOVE ONLY ON UNINSTALL
PHPIniDir "C:\php"
LoadModule php5_module "C:\php\php5apache2_2.dll"
#END PHP INSTALLER EDITS - REMOVE ONLY ON UNINSTALL



It starts alright. But when I attempt to run a PHP test it only gives me text, still.

And to answer your question - starting the server up seems to have updated the file date from 21. to the 23.

Quote

[Thu Aug 23 10:09:47 2012] [notice] Apache/2.2.22 (Win32) PHP/5.4.6 configured -- resuming normal operations
[Thu Aug 23 10:09:47 2012] [notice] Server built: Jan 28 2012 11:16:39
[Thu Aug 23 10:09:47 2012] [notice] Parent: Created child process 2012
httpd.exe: Could not reliably determine the server's fully qualified domain name, using 5.189.164.137 for ServerName
httpd.exe: Could not reliably determine the server's fully qualified domain name, using 5.189.164.137 for ServerName
[Thu Aug 23 10:09:47 2012] [notice] Child 2012: Child process is running
[Thu Aug 23 10:09:47 2012] [notice] Child 2012: Acquired the start mutex.
[Thu Aug 23 10:09:47 2012] [notice] Child 2012: Starting 64 worker threads.
[Thu Aug 23 10:09:47 2012] [notice] Child 2012: Starting thread to listen on port 80.
[Thu Aug 23 10:10:09 2012] [error] [client 127.0.0.1] File does not exist: C:/apache/htdocs/favicon.ico
[Thu Aug 23 10:10:12 2012] [error] [client 127.0.0.1] File does not exist: C:/apache/htdocs/favicon.ico
[Thu Aug 23 10:10:19 2012] [error] [client 127.0.0.1] File does not exist: C:/apache/htdocs/favicon.ico
[Thu Aug 23 10:10:22 2012] [error] [client 127.0.0.1] File does not exist: C:/apache/htdocs/favicon.ico


Only noticeable error in there seems to be this: "File does not exist: C:/apache/htdocs/favicon.ico"
Was This Post Helpful? 0
  • +
  • -

  • (2 Pages)
  • +
  • 1
  • 2