The service 'wampapache64' is NOT started EXIT error code:1066
Posted by: chrishellas (---.access.hol.gr)
Date: September 19, 2022 08:03AM

Hello everybody. This is the message i have when i am trying to run wampserver
Please help me.
Thankw in advance

1) The message in print screen --> [ibb.co]

State of services:

The service 'wampapache64' is NOT started
EXIT error code:1066
Help message for error code 1066 is:Η υπηρεσία επέστρεψε έναν κωδικό σφάλματος που αφορά συγκεκριμένη υπηρεσία.
>>> AH00526: Syntax error on line 428 of C:/wamp64/bin/apache/apache2.4.23/conf/httpd.conf: .
>>> TypesConfig takes one argument, the MIME types config file .

The service 'wampmysqld64' is started
Service Session : LocalSystem

WampServer (Apache, PHP and MySQL) will not function properly if any service
'wampapache64'
'wampmysqld64'
is not started.

all services BINARY_PATH_NAME are OK

--- Do you want to copy the results into Clipboard?
--- Press the Y key to confirm - Press ENTER to continue...

Options: ReplyQuote
Re: The service 'wampapache64' is NOT started EXIT error code:1066
Posted by: Otomatic (Moderator)
Date: September 19, 2022 08:43AM

Hi,

> >>> AH00526: Syntax error on line 428 of C:/wamp64/bin/apache/apache2.4.23/conf/httpd.conf: .
The error is very clear!
What are lines 425 to 435 in the httpd.conf file?
Please indicate which line 428 is.

Also, Apache 2.4.23 and PHP 5.6.25 are very old versions. You are advised to upgrade these versions.

---------------------------------------------------------------
Documentation Apache - Documentation PHP - Documentation MySQL - Wampserver install files & addons

Options: ReplyQuote
Re: The service 'wampapache64' is NOT started EXIT error code:1066
Posted by: chrishellas (---.access.hol.gr)
Date: September 21, 2022 06:19PM

Thank you very much Otomatic (Moderator) for your responce.
Here is my httpd.conf file from line 420 till the end.
I ve opened the httpd.conf file with word pad and i was counting the lines by hand, with the down arrow of my keyboard.

420#
LogLevel warn

<IfModule log_config_module>
#
425 # 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
435 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 "${INSTALL_DIR}/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 [www.example.com]

#
# 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/ "${INSTALL_DIR}/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 cgisock
</IfModule>

#
# "c:/Apache24/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
#
<Directory "${INSTALL_DIR}/cgi-bin">
AllowOverride None
Options None
Require all granted
</Directory>

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

Options: ReplyQuote
Re: The service 'wampapache64' is NOT started EXIT error code:1066
Posted by: Otomatic (Moderator)
Date: September 22, 2022 08:52AM

Hi,

> I ve opened the httpd.conf file with word pad

WordPad is absolutely not a text editor and can create errors in text files such as httpd.conf, just by opening the file.

You need to use a real text editor like Notepad++ or UltraEdit. There are others, but Notepad++ is free. I strongly advise you to install Notepad++ and to set it as default text editor for Wampserver.
Notepad++

To set it as the default editor for Wampserver, you have to modify the lines : editor= and logviewer= of the file wampmanager.conf to put the paths to notepad++.exe and replacing the backslashes by slashes, like the example below, of course using Notepad++ to do it and especially not WordPad
;Path of the Text Editor used by Wampserver
;May be modfied with the absolute path of the Text Editor exe file
;(Use / instead of \)
editor ="E:/Util/Texte/Notepad++/notepad++.exe"
logviewer ="E:/Util/Texte/Notepad++/notepad++.exe"

As for the error mentioned above, I don't see anything special.

I advise you to switch to a newer version of Apache.

See : WAMPserver 3 - All you need to know

---------------------------------------------------------------
Documentation Apache - Documentation PHP - Documentation MySQL - Wampserver install files & addons

Options: ReplyQuote


Sorry, only registered users may post in this forum.