I installed Apache on Windows 7 (localhost) and it worked fine. Then I went to download some other stuff and later noticed that the Apache server stopped. I went to command prompt (as administrator) and typed
net start apache2
It says «The Apache2 service is starting.» But before it finishes, I get the error
A service specific error occurred: 1.
It says that you can type in «NET HELPMSG 3547» for more info, but that doesn’t help at all.
Things I have tried:
- Quit Google Drive Sync
- Quit any and all programs using port 80 (port my server is on)
- Tried changing the port of the server and got same error message, so I don’t think it has anything to do with something else being in the port
None of those things have worked. I am confused at why it worked earlier, but now it won’t work.
random♦
14.6k9 gold badges54 silver badges58 bronze badges
asked Jun 10, 2014 at 21:48
2
You should check the Event Viewer for whatever shows up in the Windows Logs. Under the Application section there should be a list of errors with more details about what was exactly going wrong.
Recent example found:
The Apache service named reported the following error:
>>> Syntax error on line 523 of C:/Program Files/Apache Software Foundation/Apache2.2/conf/httpd.conf:
In the above example it was because a referenced drive was no longer on the system and Apache could not find it.
You can usually (at least in Windows Vista) find Event Viewer along the lines of:
Control Panel → Administrative Tools → Event Viewer
This should highlight any thing touching the system that you may have overlooked and provide further details and hints about what to tweak or change instead of just uninstalling everything.
answered Dec 19, 2015 at 18:06
random♦random
14.6k9 gold badges54 silver badges58 bronze badges
2
Apache server wouldn’t start after I downloaded coldfusion and added it to the server. I just uninstalled apache and coldfusion and reinstalled apache and it works fine now. The official error was that I added an extension(coldfusion) to apache and for some reason apache didn’t recognize it.
answered Jun 12, 2014 at 18:39
user2297366user2297366
1793 gold badges4 silver badges9 bronze badges
1
You must log in to answer this question.
Not the answer you’re looking for? Browse other questions tagged
.
Not the answer you’re looking for? Browse other questions tagged
.
There is some other program listening on port 80, usual suspects are
- Skype (Listens on port 80)
- NOD32 (Add Apache to the IMON exceptions’ list for it to allow apache to bind)
- Some other antivirus (Same as above)
Way to correct it is either shutting down the program that’s using the port 80 or configure it to use a different port or configure Apache to listen on a different port with the Listen directive in httpd.conf. In the case of antivirus configure the antivirus to allow Apache to bind on the port you have chosen.
Way to diagnose which app, if any, has bound to port 80 is run the netstat with those options, look for :80 next to the local IP address (second column) and find the PID (last column). Then, on the task manager you can find which process has the PID you got in the previous step. (You might need to add the PID column on the task manager)
C:\Users\vinko>netstat -ao -p tcp
Conexiones activas
Proto Dirección local Dirección remota Estado PID
TCP 127.0.0.1:1110 127.0.0.1:51373 TIME_WAIT 0
TCP 127.0.0.1:1110 127.0.0.1:51379 TIME_WAIT 0
TCP 127.0.0.1:1110 127.0.0.1:51381 ESTABLISHED 388
TCP 127.0.0.1:1110 127.0.0.1:51382 TIME_WAIT 0
TCP 127.0.0.1:1110 127.0.0.1:51479 TIME_WAIT 0
TCP 127.0.0.1:1110 127.0.0.1:51481 TIME_WAIT 0
TCP 127.0.0.1:1110 127.0.0.1:51483 TIME_WAIT 0
TCP 127.0.0.1:1110 127.0.0.1:51485 ESTABLISHED 388
TCP 127.0.0.1:1110 127.0.0.1:51487 TIME_WAIT 0
TCP 127.0.0.1:1110 127.0.0.1:51489 ESTABLISHED 388
TCP 127.0.0.1:51381 127.0.0.1:1110 ESTABLISHED 5168
TCP 127.0.0.1:51485 127.0.0.1:1110 ESTABLISHED 5168
TCP 127.0.0.1:51489 127.0.0.1:1110 ESTABLISHED 5168
TCP 127.0.0.1:59264 127.0.0.1:59265 ESTABLISHED 5168
TCP 127.0.0.1:59265 127.0.0.1:59264 ESTABLISHED 5168
TCP 127.0.0.1:59268 127.0.0.1:59269 ESTABLISHED 5168
TCP 127.0.0.1:59269 127.0.0.1:59268 ESTABLISHED 5168
TCP 192.168.1.34:51278 192.168.1.33:445 ESTABLISHED 4
TCP 192.168.1.34:51383 67.199.15.132:80 ESTABLISHED 388
TCP 192.168.1.34:51486 66.102.9.18:80 ESTABLISHED 388
TCP 192.168.1.34:51490 74.125.4.20:80 ESTABLISHED 388
If you want to Disable Skype from listening on port 80 and 443, you can follow the link http://www.mydigitallife.info/disable-skype-from-using-opening-and-listening-on-port-80-and-443-on-local-computer/
Сообщение от svsw
lawliet93, посмотрите что пишется в error.log и в виндовый журнал
да я смотрел, но это не помогло
вот error.log
Кликните здесь для просмотра всего текста
Starting the Apache2.2 service
The Apache2.2 service is running.
rmine the server’s fully qualified domain name, using 192.168.14.48 for ServerName
[Mon Mar 18 14:26:16 2013] [notice] Apache/2.2.22 (Win32) configured — resuming normal operations
[Mon Mar 18 14:26:16 2013] [notice] Server built: Jan 28 2012 11:16:39
[Mon Mar 18 14:26:16 2013] [notice] Parent: Created child process 3576
httpd.exe: Could not reliably determine the server’s fully qualified domain name, using 192.168.14.48 for ServerName
httpd.exe: Could not reliably determine the server’s fully qualified domain name, using 192.168.14.48 for ServerName
[Mon Mar 18 14:26:17 2013] [notice] Child 3576: Child process is running
[Mon Mar 18 14:26:17 2013] [notice] Child 3576: Acquired the start mutex.
[Mon Mar 18 14:26:17 2013] [notice] Child 3576: Starting 64 worker threads.
[Mon Mar 18 14:26:17 2013] [notice] Child 3576: Starting thread to listen on port 80.
[Mon Mar 18 14:26:27 2013] [error] [client 127.0.0.1] File does not exist: C:/server/apache/htdocs/favicon.ico
[Mon Mar 18 15:40:20 2013] [warn] pid file C:/server/apache/logs/httpd.pid overwritten — Unclean shutdown of previous Apache run?
[Mon Mar 18 15:40:20 2013] [notice] Apache/2.2.22 (Win32) PHP/5.2.16 configured — resuming normal operations
[Mon Mar 18 15:40:20 2013] [notice] Server built: Jan 28 2012 11:16:39
[Mon Mar 18 15:40:20 2013] [notice] Parent: Created child process 1892
[Mon Mar 18 15:40:21 2013] [notice] Child 1892: Child process is running
[Mon Mar 18 15:40:21 2013] [notice] Child 1892: Acquired the start mutex.
[Mon Mar 18 15:40:21 2013] [notice] Child 1892: Starting 64 worker threads.
[Mon Mar 18 15:40:21 2013] [notice] Child 1892: Starting thread to listen on port 80.
[Mon Mar 18 15:43:36 2013] [error] [client 127.0.0.1] File does not exist: C:/server/www/favicon.ico
[Mon Mar 18 15:44:41 2013] [error] [client 127.0.0.1] File does not exist: C:/server/www/favicon.ico
[Mon Mar 18 22:24:05 2013] [error] [client 127.0.0.1] File does not exist: C:/server/www/favicon.ico
[Mon Mar 18 22:31:29 2013] [notice] Parent: Received shutdown signal — Shutting down the server.
[Mon Mar 18 22:31:29 2013] [notice] Child 1892: Exit event signaled. Child process is ending.
[Mon Mar 18 22:31:30 2013] [notice] Child 1892: Released the start mutex
[Mon Mar 18 22:31:31 2013] [notice] Child 1892: All worker threads have exited.
[Mon Mar 18 22:31:36 2013] [notice] Child 1892: Child process is exiting
[Mon Mar 18 22:31:36 2013] [notice] Parent: Child process exited successfully.
httpd.exe: Could not reliably determine the server’s fully qualified domain name, using 192.168.14.174 for ServerName
[Mon Mar 18 22:35:13 2013] [notice] Apache/2.2.22 (Win32) PHP/5.2.16 configured — resuming normal operations
[Mon Mar 18 22:35:13 2013] [notice] Server built: Jan 28 2012 11:16:39
[Mon Mar 18 22:35:13 2013] [notice] Parent: Created child process 2700
httpd.exe: Could not reliably determine the server’s fully qualified domain name, using 192.168.14.174 for ServerName
httpd.exe: Could not reliably determine the server’s fully qualified domain name, using 192.168.14.174 for ServerName
[Mon Mar 18 22:35:13 2013] [notice] Child 2700: Child process is running
[Mon Mar 18 22:35:13 2013] [notice] Child 2700: Acquired the start mutex.
[Mon Mar 18 22:35:13 2013] [notice] Child 2700: Starting 64 worker threads.
[Mon Mar 18 22:35:13 2013] [notice] Child 2700: Starting thread to listen on port 80.
[Mon Mar 18 23:08:34 2013] [error] [client 127.0.0.1] File does not exist: C:/server/www/Client
[Mon Mar 18 23:09:03 2013] [error] [client 127.0.0.1] File does not exist: C:/server/www/Client
[Mon Mar 18 23:09:06 2013] [notice] Parent: Received shutdown signal — Shutting down the server.
[Mon Mar 18 23:09:06 2013] [notice] Child 2700: Exit event signaled. Child process is ending.
[Mon Mar 18 23:09:07 2013] [notice] Child 2700: Released the start mutex
[Mon Mar 18 23:09:11 2013] [notice] Child 2700: All worker threads have exited.
[Mon Mar 18 23:09:11 2013] [notice] Child 2700: Child process is exiting
[Mon Mar 18 23:09:11 2013] [notice] Parent: Child process exited successfully.
httpd.exe: Could not reliably determine the server’s fully qualified domain name, using 192.168.14.254 for ServerName
[Tue Mar 19 13:45:22 2013] [notice] Apache/2.2.22 (Win32) PHP/5.2.16 configured — resuming normal operations
[Tue Mar 19 13:45:22 2013] [notice] Server built: Jan 28 2012 11:16:39
[Tue Mar 19 13:45:22 2013] [notice] Parent: Created child process 3616
httpd.exe: Could not reliably determine the server’s fully qualified domain name, using 192.168.14.254 for ServerName
httpd.exe: Could not reliably determine the server’s fully qualified domain name, using 192.168.14.254 for ServerName
[Tue Mar 19 13:45:23 2013] [notice] Child 3616: Child process is running
[Tue Mar 19 13:45:23 2013] [notice] Child 3616: Acquired the start mutex.
[Tue Mar 19 13:45:23 2013] [notice] Child 3616: Starting 64 worker threads.
[Tue Mar 19 13:45:23 2013] [notice] Child 3616: Starting thread to listen on port 80.
[Tue Mar 19 13:53:09 2013] [notice] Parent: Received shutdown signal — Shutting down the server.
[Tue Mar 19 13:53:09 2013] [notice] Child 3616: Exit event signaled. Child process is ending.
[Tue Mar 19 13:53:10 2013] [notice] Child 3616: Released the start mutex
[Tue Mar 19 13:53:11 2013] [notice] Child 3616: All worker threads have exited.
[Tue Mar 19 13:53:16 2013] [notice] Child 3616: Child process is exiting
[Tue Mar 19 13:53:16 2013] [notice] Parent: Child process exited successfully.
httpd.exe: Could not reliably determine the server’s fully qualified domain name, using 192.168.14.208 for ServerName
[Wed Mar 20 12:21:09 2013] [notice] Apache/2.2.22 (Win32) PHP/5.2.16 configured — resuming normal operations
[Wed Mar 20 12:21:09 2013] [notice] Server built: Jan 28 2012 11:16:39
[Wed Mar 20 12:21:09 2013] [notice] Parent: Created child process 4452
httpd.exe: Could not reliably determine the server’s fully qualified domain name, using 192.168.14.208 for ServerName
httpd.exe: Could not reliably determine the server’s fully qualified domain name, using 192.168.14.208 for ServerName
[Wed Mar 20 12:21:10 2013] [notice] Child 4452: Child process is running
[Wed Mar 20 12:21:10 2013] [notice] Child 4452: Acquired the start mutex.
[Wed Mar 20 12:21:10 2013] [notice] Child 4452: Starting 64 worker threads.
[Wed Mar 20 12:21:10 2013] [notice] Child 4452: Starting thread to listen on port 80.
[Wed Mar 20 13:31:14 2013] [error] [client 127.0.0.1] File does not exist: C:/server/www/favicon.ico
[Wed Mar 20 13:37:36 2013] [notice] Parent: Received shutdown signal — Shutting down the server.
[Wed Mar 20 13:37:36 2013] [notice] Child 4452: Exit event signaled. Child process is ending.
[Wed Mar 20 13:37:37 2013] [notice] Child 4452: Released the start mutex
[Wed Mar 20 13:37:38 2013] [notice] Child 4452: All worker threads have exited.
[Wed Mar 20 13:37:43 2013] [notice] Child 4452: Child process is exiting
[Wed Mar 20 13:37:43 2013] [notice] Parent: Child process exited successfully.
httpd.exe: Could not reliably determine the server’s fully qualified domain name, using 192.168.14.147 for ServerName
[Wed Mar 20 16:33:48 2013] [notice] Apache/2.2.22 (Win32) PHP/5.2.16 configured — resuming normal operations
[Wed Mar 20 16:33:48 2013] [notice] Server built: Jan 28 2012 11:16:39
[Wed Mar 20 16:33:48 2013] [notice] Parent: Created child process 4164
httpd.exe: Could not reliably determine the server’s fully qualified domain name, using 192.168.14.147 for ServerName
httpd.exe: Could not reliably determine the server’s fully qualified domain name, using 192.168.14.147 for ServerName
[Wed Mar 20 16:33:48 2013] [notice] Child 4164: Child process is running
[Wed Mar 20 16:33:48 2013] [notice] Child 4164: Acquired the start mutex.
[Wed Mar 20 16:33:48 2013] [notice] Child 4164: Starting 64 worker threads.
[Wed Mar 20 16:33:48 2013] [notice] Child 4164: Starting thread to listen on port 80.
[Wed Mar 20 17:09:07 2013] [notice] Parent: Received shutdown signal — Shutting down the server.
[Wed Mar 20 17:09:07 2013] [notice] Child 4164: Exit event signaled. Child process is ending.
[Wed Mar 20 17:09:08 2013] [notice] Child 4164: Released the start mutex
[Wed Mar 20 17:09:16 2013] [notice] Child 4164: All worker threads have exited.
[Wed Mar 20 17:09:21 2013] [notice] Child 4164: Child process is exiting
[Wed Mar 20 17:09:21 2013] [notice] Parent: Child process exited successfully.
httpd.exe: Could not reliably determine the server’s fully qualified domain name, using 192.168.14.201 for ServerName
[Mon Mar 25 16:25:57 2013] [notice] Apache/2.2.22 (Win32) PHP/5.2.16 configured — resuming normal operations
[Mon Mar 25 16:25:57 2013] [notice] Server built: Jan 28 2012 11:16:39
[Mon Mar 25 16:25:57 2013] [notice] Parent: Created child process 5052
httpd.exe: Could not reliably determine the server’s fully qualified domain name, using 192.168.14.201 for ServerName
httpd.exe: Could not reliably determine the server’s fully qualified domain name, using 192.168.14.201 for ServerName
[Mon Mar 25 16:25:57 2013] [notice] Child 5052: Child process is running
[Mon Mar 25 16:25:57 2013] [notice] Child 5052: Acquired the start mutex.
[Mon Mar 25 16:25:57 2013] [notice] Child 5052: Starting 64 worker threads.
[Mon Mar 25 16:25:57 2013] [notice] Child 5052: Starting thread to listen on port 80.
а вот что в журнале виндовса
Кликните здесь для просмотра всего текста
The Apache service named reported the following error:
>>> (OS 10013)Сделана попытка доступа к сокету методом, запрещенным правами доступа. : make_sock: could not bind to address 0.0.0.0:80 .
The Apache service named reported the following error:
>>> no listening sockets available, shutting down .
The Apache service named reported the following error:
>>> Unable to open logs .
Служба «Apache2.2» завершена из-за внутренней ошибки Неверная функция..
Perform the steps below to resolve this issue.
To refresh the Webtrends Apache HTTP configuration:
1. Ensure the Webtrends — MySQL (or MS SQL system database) and the Webtrends — User interface service are running. If the User interface has not started, you will be unable to proceed until they do.
2. Open the following file in a text editor:
\Webtrends\common\apache\conf\httpd.conf
3. Find the line that reads similar to the following:
#Listen 12.34.56.78:80.
4. On the line below, paste the following:
Listen 7099
5. Find the a line similar to «ServerName pdxfasteenn02:» (pdxfasteenn02 should be the name of the Webtrends server).
6. Replace it with the following:
ServerName pdxfasteenn02:7099
Ensure both the Listen line and the ServerName line do not contain a ‘#’.
7. Save the httpd.conf file.
8. Open a command prompt and navigate to the following folder:
Webtrends\common\apache\bin
9. Type the following, and then press enter:
apache.exe
The command window may appear as if it has hung or locked up but this is the expected behavior.
10. Open the Windows Services snap-in and verify that Apache is started.
11. If necessary, start the Tomcat service.
Do not stop and then start Webtrends — User interface service. If you do, it will overwrite the changes made to the httpd.conf file with faulty data.
12. Log into Webtrends and click Administration > System Management > Hosts > UI Server.
13. If the box for «Enable HTTP» is not checked, check it. If it is checked, uncheck and then recheck it, also check or uncheck the box for Enable Tomcat logging (making this change will force a write to the configuration file; you can go back and undo the Tomcat logging change later).
14. In the «Apache Port» box, type 7099, and then click Save.
15. If you are prompted to restart the Webtrends services, click Restart Services.
The Apache service should now start normally. If you made a change to the Tomcat logging settings in step 13, go back and undo that change now.
I have installed xampp. When i open xampp control panel, mysql and filezilla services are running, but not apache. When i click to start apache it gives me this
ERROR:error:apache service not started [-1]
I have even blocked firewalls for this.
Why this is happeneing and how can i start apache services.I have installed xampp in my E: directory.
Simon Dugré
18k11 gold badges57 silver badges73 bronze badges
asked Apr 30, 2011 at 3:09
saplingProsaplingPro
20.8k53 gold badges137 silver badges196 bronze badges
here is the steps which will make apache work normally without such errors
- Firstly, make sure that Apache is stopped
- Make sure, Svc check box is unchecked
- Now! go to your XAMPP Folder (
C:\xampp\apache\– I installed the xampp in C:) - Now! double click on “
apache_uninstallservice.bat” which is available in apache folder. - After above step, now open your XAMPP Control Panel again and click on Start button which is beside Apache, and make sure that you will not check the Svc checkbox provided.
such errors my happen in old operation systems for example win XP or Vista…
and the latest versions of xampp may not have the corresponding configurations
kazinix
29k33 gold badges107 silver badges157 bronze badges
answered Jun 9, 2012 at 19:40
I found this page looking for a solution to this problem after downloading xampp lite.
I solved this as follow:
The installed service for apache from xampp uses the standalone installation path for apache; c:\program files\apache2.x\...etc and not the local path in xampp folder.
Just modify all registry keys that include the wrong path for apache service in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Apache2.x and it should work.
Bot
11.9k11 gold badges76 silver badges131 bronze badges
answered Jun 27, 2012 at 22:57
ammaamma
212 bronze badges
There could be many causes.
Make sure you have no other applications using the port that apache is using. From the XAMPP control panel there is a button you can press to run a tool to check which ports are in use. Applications which I know to conflict with Apache are Skype and Panda Media; there could be others.
answered Apr 30, 2011 at 3:20
ExtrakunExtrakun
19.1k21 gold badges82 silver badges129 bronze badges
2
Unselect the Svc box in the XAMPP control panel and try to restart it. Should work.
answered Jun 19, 2012 at 10:02
