Menu
I'm using XAMPP, and I can start Apache, but, MySQL (phpMyAdmin) start!
When I start, I get this error;
10:07:49 [Apache] Error: Apache shutdown unexpectedly. 10:07:49 [Apache] This may be due to a blocked port, missing dependencies, 10:07:49 [Apache] improper privileges, a crash, or a shutdown by another method. 10:07:49 [Apache] Press the Logs button to view error logs and check 10:07:49 [Apache] the Windows Event Viewer for more clues 10:07:49 [Apache] If you need more help, copy and post this 10:07:49 [Apache] entire log window on the forums I search on it, and, change the port of Apache in Config -> Service and Port setting. I have;
Service name: Apache 2.4 Main port: 122 SSL port: 444 I also uninstall Skype (Windows 8/10/Metro version). Nothing is working. In the httpd.conf file I have;
Listen 122 ServerName localhost:122 I start it via apache_start.bat and get;
(OS 10013)An attempt was made to access a socket in a way forbidden by its access permissions. : AH00072: make_sock: could not bind to address [::]:445 (OS 10013)An attempt was made to access a socket in a way forbidden by its access permissions. : AH00072: make_sock: could not bind to address 0.0.0.0:445 AH00451: no listening sockets available, shutting down AH00015: Unable to open logs Please note that all the log files don’t exists! Skype is uninstalled.
466
The most common cause for the XAMPP Apache server not starting issue is because the default port no 80 may already be in use by another program like Skype, Teamviewer etc. For example, in my previous blog post with the solution for XAMPP and Windows User Account Control warning message issue, Mr.
First, navigate to xampp's directory (default is c:\xampp) and double click apache_start. bat. This will open up a comand line and return more detailed errors about why apache can't run.
1. Resolve Apache Port Conflicts. If Apache cannot start, you won't be able to access your XAMPP dashboard or any sites you have installed on the platform. A port conflict may be the underlying problem.
Update: 15th May, 2018:
The latest Windows 10 update (re-)activated the World Wide Web Publishing Service (in German: WWW-Publishingdienst). This might depend on the options you select during the configuration of the update you can make afterwards.
Update: 4th August, 2015:
If you have done clean installation of Windows 10, you may not have the Word Wide Web Publishing Service. In that case, simple WAMP/XAMPP installation should work fine.
If it doesn't, try installing Visual C++ Redistributable and then re-install WAMP/XAMPP.
I was facing a similar problem with WAMP. In Windows 10 TP, the Word Wide Web Publishing Service comes pre-installed. This is related to IIS and you can remove it if you don't need it.
This blocks the port 80, making Apache act weirdly. You can do the following and try again.
This should make port 80 free and restarting WAMP/XAMPP should get you up and running!
There are other ways to do fix this. See Make WAMP Work On Windows 10.
84
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
