WampServer

Hello, I tried everything you recommended, but nothing solved the issue.

Apache service does not start after windows 10 update to build 18362.

Need help, please!

Error Log:

[Thu Sep 19 11:19:10.831717 2019] [mpm_winnt:notice] [pid 5448:tid 748] AH00422: Parent: Received shutdown signal -- Shutting down the server.
[Thu Sep 19 11:19:13.237965 2019] [mpm_winnt:notice] [pid 7280:tid 700] AH00364: Child: All worker threads have exited.
[Thu Sep 19 11:19:15.253597 2019] [mpm_winnt:notice] [pid 5448:tid 748] AH00430: Parent: Child process 7280 exited successfully.
[Thu Sep 19 15:30:59.509506 2019] [mpm_winnt:notice] [pid 6980:tid 796] AH00455: Apache/2.4.39 (Win64) PHP/7.3.7 configured -- resuming normal operations
[Thu Sep 19 15:30:59.509506 2019] [mpm_winnt:notice] [pid 6980:tid 796] AH00456: Apache Lounge VC15 Server built: Mar 28 2019 11:59:33
[Thu Sep 19 15:30:59.509506 2019] [core:notice] [pid 6980:tid 796] AH00094: Command line: 'e:\\wamp64\\bin\\apache\\apache2.4.39\\bin\\httpd.exe -d E:/wamp64/bin/apache/apache2.4.39'
[Thu Sep 19 15:30:59.555826 2019] [mpm_winnt:notice] [pid 6980:tid 796] AH00418: Parent: Created child process 7880
[Thu Sep 19 15:31:00.555781 2019] [mpm_winnt:notice] [pid 7880:tid 608] AH00354: Child: Starting 64 worker threads.
[Fri Sep 20 10:20:04.185713 2019] [mpm_winnt:notice] [pid 6980:tid 796] AH00422: Parent: Received shutdown signal -- Shutting down the server.
[Fri Sep 20 10:20:06.467030 2019] [mpm_winnt:notice] [pid 7880:tid 608] AH00364: Child: All worker threads have exited.
[Fri Sep 20 10:20:07.935746 2019] [mpm_winnt:notice] [pid 6980:tid 796] AH00430: Parent: Child process 7880 exited successfully.
[Mon Sep 23 13:59:07.768425 2019] [core:warn] [pid 8184:tid 616] AH00098: pid file E:/wamp64/bin/apache/apache2.4.39/logs/httpd.pid overwritten -- Unclean shutdown of previous Apache run?
[Mon Sep 23 13:59:19.830748 2019] [core:warn] [pid 9540:tid 676] AH00098: pid file E:/wamp64/bin/apache/apache2.4.39/logs/httpd.pid overwritten -- Unclean shutdown of previous Apache run?
[Mon Sep 23 14:00:14.939718 2019] [core:warn] [pid 10132:tid 648] AH00098: pid file E:/wamp64/bin/apache/apache2.4.39/logs/httpd.pid overwritten -- Unclean shutdown of previous Apache run?
[Mon Sep 23 14:00:39.064596 2019] [core:warn] [pid 10004:tid 688] AH00098: pid file E:/wamp64/bin/apache/apache2.4.39/logs/httpd.pid overwritten -- Unclean shutdown of previous Apache run?



Edited 1 time(s). Last edit at 09/23/2019 04:50PM by Otomatic.

Hi,

Si vous voulez déposer une question sur le forum francophone, il faut impérativement écrire en Français.

I repeat what needs to be done after the big Windows updates, in this case, the version changes.

- 1 - VC+++ packages may have been modified or even uninstalled:

- Verify that all VC ++ packages are installed and with the latest versions.
To do this, use the tool:
Checks VC++ packages installed
Do not use a previously loaded tool. Make a new download to make sure you are using the correct version.
To download missing packages, do not rely on Microsoft links, they are not reliable, download packages on http://wampserver.aviatechno.net in section Visual C++ Redistribuable Packages
Do not forget that if you have a 64 bit Windows, you must install both 32 and 64 bit versions of each package.
You must install each package "as an administrator", so right-click the exe file and then run as Administrator.

All packages should be checked, even those that are theoretically installed and "Repair" if already installed.

- If it is not already done, apply Update 3.1.9 to your version of Wampserver
Wampserver update 3.1.9

- 2 - The Wampmanager services (Apache, MySQL, MariaD are no longer valid and must be reinstalled.
One or more services may not have been deleted by the Windows update, in which case it must be done manually by opening a command window, as an administrator and typing the commands below:

sc delete wampapache
sc delete wampmysqld
sc delete wampmariadb
sc delete wampapache64
sc delete wampmysqld64
sc delete wampmariadb64

Close the command window and launch Wampserver. Of course the icon will not be green.

Left-Click -> Apache -> Service administration -> Install service
Left-Click -> MySQL -> Service administration -> Install service
Left-Click -> MariaDB -> Service administration -> Install service

Left-Click -> Start All Services

Important: Remember that some previously disabled parameters or applications may have been reactivated, so see items 03 and 08 of TROUBLESHOOTING TIPS

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



Edited 1 time(s). Last edit at 09/23/2019 06:46PM by Otomatic.

Thanks for the reply!

1- I installed all VC++ packages, but the check keeps telling me, that they are not installed.

2 - I had version 3.1.9, but installed the update again.

3 - I deleted wampapache64 manually and reinstalled it before. (did not make any changes on wampmariadb64 service which also worked after the windows update.)


Error remains: [Mon Sep 23 19:50:50.585573 2019] [core:warn] [pid 8828:tid 644] AH00098: pid file E:/wamp64/bin/apache/apache2.4.39/logs/httpd.pid overwritten -- Unclean shutdown of previous Apache run?

Hi,

> 1- I installed all VC++ packages, but the check keeps telling me, that they are not installed.

If the tool tells you that some VC++ packages are not installed, it means they are not installed. There is no record of installations in the Windows registry.

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

But in Windows Control Panel -> Software: all packages are listed as installed.

I really don't know, what else to do...

Hi,

Since it is the Apache service that does not start, you can check some "tricks" with the tools integrated in Wampmanager:

- Right-Click -> Tools -> Test port 80

- Right-Click -> Tools -> Check httpd.conf syntax

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

I did everything you suggested. I carefully went through each step:
- I reinstalled all VC++ packages. Now the testing tool says everything is ok.
- I checked that neither Skype nor IIS are active. The port-test-tool also says everything is ok. I also tried other ports, with the same result.
- I reinstalled the WAMP services wampapache64 and wampmariadb64.
- I updated WAMP to the most current version.
- httpd.conf syntax check says everything is ok.
Still, it does not work.

The strangest thing ist: Apache itself seems to work!
If I start it using cmd => e:/wamp64/bin/apache/apache2.4.41/bin/httpd.exe, the server normally starts.

The problem seems to be just with the wampapache64 service. In the system event log, it says “The wampapache64 service terminated with service-specific error Incorrect function.”

Hi,

I don't understand what's going on.

We're going to try a procedure that I'm going to run in real time on my 64-bit Wampserver, under Windows 10 which - lucky for you and me - is installed in E:\wamp64.
Wampserver must not be started, so eventually Quit Wampmanager.

Open a command window as an administrator, the word "Administrator" must appear in the title bar of this command window.
You must delete the service in question, therefore, in this command window type:
sc delete wampapache64

c:\Windows\System32>sc delete wampapache64
[SC] DeleteService réussite(s)

c:\Windows\System32>

My Windows 10 system being only in French, "réussite" means success.
You can check via the Service Manager (services.msc) that the wampapache64 service no longer exists.

In the command window already opened, we will go to the bin folder of the Apache version used by the command:
cd /d e:\wamp64\bin\apache\apache2.4.39\bin

c:\Windows\System32>cd /d e:\wamp64\bin\apache\apache2.4.39\bin

e:\wamp64\bin\apache\apache2.4.39\bin>

Then we will create the wampapache64 service without any interference with Wampmanager since it is closed.
So, type the command:
httpd.exe -k install -n wampapache64

e:\wamp64\bin\apache\apache2.4.39\bin>httpd.exe -k install -n wampapache64
Installing the 'wampapache64' service
The 'wampapache64' service is successfully installed.
Testing httpd.conf....
Errors reported here must be corrected before the service can be started.

e:\wamp64\bin\apache\apache2.4.39\bin>

There, everything goes well, there is no error to display and, in addition, there is a check of the httpd.conf syntax.

It is possible to check, still in the service manager, possibly by refreshing, that the service has been created.

But this service was created in automatic start and must be passed in manual start by the command:
sc config wampapache64 start= demand
Be careful, it is "start=" without space before the equal sign.

e:\wamp64\bin\apache\apache2.4.39\bin>sc config wampapache64 start= demand
[SC] ChangeServiceConfig réussite(s)

e:\wamp64\bin\apache\apache2.4.39\bin>

Once there, you can check, still in the command window, that the service starts correctly with the command:
net start wampapache64

e:\wamp64\bin\apache\apache2.4.39\bin>net start wampapache64
Le service wampapache64 démarre.
Le service wampapache64 a démarré.


e:\wamp64\bin\apache\apache2.4.39\bin>

From French :
Le service wampapache64 démarre.
Le service wampapache64 a démarré.
means
The wampapache64 service starts.
The wampapache64 service has started.

and there's no error.

Before launching Wampserver, it is necessary to stop the service so that this Wampserver that starts it, therefore commands:
net stop wampapache64

e:\wamp64\bin\apache\apache2.4.39\bin>net stop wampapache64
Le service wampapache64 s’arrête.
Le service wampapache64 a été arrêté.


e:\wamp64\bin\apache\apache2.4.39\bin>

From French :
Le service wampapache64 s’arrête.
Le service wampapache64 a été arrêté.
means
The wampapache64 service stops.
The wampapache64 service has been stopped.

If there have been no errors in response to previous commands, you can close the command window and launch Wampserver.

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

Thank you for your help. I did everything as you said, but it only worked up to “net start wampapache64”. This command did not work; I got error 1067 there.
My system is in German; the message means:
“wampapache64 is starting.
wampapache64 could not be started.
A system error occurred.
System error 1067 occurred.
The process has unexpectedly been terminated.”

So, after all, I understand it really is a problem with Apache rather than with Wamp.
However, see the last line: Here, httpd.exe starts without problems and I can access localhost in my browser afterwards.



Edited 1 time(s). Last edit at 09/26/2019 02:06PM by TeWe.

Hi,

See if there is a file :

e:\wamp64\bin\apache\apache2.4.39\logs\httpd.pid

If yes, delete this file.

> However, see the last line: Here, httpd.exe starts without problems and I can access localhost in my browser afterwards.

try also to start Apache with the service :

httpd.exe -n wampapache64 -k start

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

> See if there is a file :
> e:\wamp64\bin\apache\apache2.4.39\logs\httpd.pid
> If yes, delete this file.
There was no such file.

> try also to start Apache with the service :
> httpd.exe -n wampapache64 -k start
This seemingly does not work. There is no output (such as an error message), but the program immediately exists after starting. It works, however, when removing the “-k start” part.

Hi,

Now I really don't know where and what to offer you.
As a last resort, I can suggest that you install the Apache 2.4.41 addon, then, once installed, switch to this new version:
Left-click -> Apache -> Version -> Apache 2.4.41
This performs the following operations:
- Apache Service Shutdown 2.4.39
- Deleting Apache service 2.4.39
- Switch to new version 2.4.41
- Apache service installation 2.4.41
- Starting the Apache service 2.4.41

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

I already had installed the newest version of Apache. However, I finally could spot the problem: On my system (which is complex), I first had to take control over the service as a user (https://appuals.com/how-to-fix-error-1067-the-process-terminated-unexpectedly/); it seems that I otherwise had no right to start the service. Everything is fine/green now. Thank you much for your help.

Hi,

> it seems that I otherwise had no right to start the service
The services are installed as an administrator and can only be launched in an administrator session.

However, there is a possibility to start the services as a standard user:

Hello,

This is a translation of a contribution that I had posted on the French forum Wampserver.

I have test launching of WampServer - thus starting wampapache and wampmysqld services - in a "standard" user session that is to say without administrator privileges, and it works on my session W7 or W10 Pro 64-bit with two users:
- "Dominique" administrator
- "Otomatic" standard user

Everything that follows is to be performed in an administrator session:
This means that if you want to do this on a workstation that is part of an enterprise network, you will need to call your network administrator or IT manager.

Download the utility "Setacl.exe" the free version from the command line on the website [helgeklein.com]
This version:
Administrators: Download the EXE version of SetACL 3.0.6 for 32-bit and 64-bit Windows.

Unzip the file, which will create a folder: SetACL (executable Version)\ in which there are two other folder for 32 bit and 64 bit versions.
Open a command window into the 32 or 64 bits folder depending on the version of Windows. If you have a Windows 64-bit, it is imperative to run the 64-bit version of setacl.
In the command window, we will give the rights to a user to start, stop and read wampapache, wampmysqld and wampmariadb services, in my case the user without rights "Otomatic."
Generic command is:

setacl -on "service_name" -ot srv -ace "n:user_name_without_rights;p:start_stop,read" -actn ace

which gives the following two commands for WampServer:

setacl -on "wampapache" -ot srv -ace "n:Otomatic;p:start_stop,read" -actn ace
setacl -on "wampmysqld" -ot srv -ace "n:Otomatic;p:start_stop,read" -actn ace
setacl -on "wampmariadb" -ot srv -ace "n:Otomatic;p:start_stop,read" -actn ace

Of course:
- you replace Otomatic by the name of the user you want to allow to start the services.
- you replace service names by wampapache64, wampmysqld64 and wampmariadb64 if uou use Wampserver 64 bit.
The user account must exist before performing the commands.

By connecting with Otomatic session, I can start WampServer, which starts the services and pass the icon green with access to localhost and phpMyAdmin.

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

I had a similar problem and found out that the update to windows 10 still kept WAMPP running while it was being updated, and when the computer restarted, MySQL, Apache, and the WAMPP manager was still running, but the green icon in the system tray wasn't showing and it was assumed that WAMPP was stopped, but when I tried to run WAMPP from the desktop icon, 2 consoles briefly flashed, then vanished, and still no tray icon, so I looked in the task manager and saw that mysqld, apache and the WAMPP manager were still running, so I un-tasked all of them and now I can run it under win10 with no problems.