Apache Service Could Not Start Error Code 1
Contents |
ID: 20007|Last Revised: July 22, 2016 Tweet In cases where the ESET Remote Administrator Web Console (ERA Web Console) is not running, check whether the Apache Tomcat service service specific error code 1 apache is running (open a Rundialog, typeservices.msc, clickOK, locate theApache Tomcatservice, and windows could not start the apache 2.2 on local computer error code 1 then verify that Running is listed in theStatuscolumn); if it is not, try to start the service manually
Windows Could Not Start The Wampapache On Local Computer Error Code 1
by selecting it and clicking Start. While trying to start theservice, you might receive the following error message, which may result from a Java update: "Windows could not start
Windows Could Not Start The Apache2.2 On Local Computer
the Apache Tomcat 7 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 the service-specific error code 1." If you receive this error while attempting to start the Apache Tomcat service, follow the step-by-step instructions below to resolve your issue: Navigate to your%TOMCAT_HOME%\bindirectory (for service specific error code 1 tomcat example,C:\Program Files\Apache Tomcat\Tomcat7\bin) and double-clicktomcat7w.exe. Figure 1-1 Click the image to view larger in new window Click the Java tab, select the check box next toUse defaultand then clickOK. Figure 1-2 Startthe Apache Tomcat service. The service should start without issue. Was this information helpful? Languages This article is available in the following languages: DeutschItalianoEspañol Tools Printer Friendly Rate this Page Additional Assistance Malware DescriptionsTools and UtilitiesSubmit a Case Online Community ESET User Forum Visit us on Facebook Follow us on Twitter ESET KB on YouTube ESET Products and SolutionsSupport Cart United States Select your ESET Knowledgebase language: Čeština Deutsch English (International) English (United States) Español Français Italiano Magyar Nederlands Polski Português Русский Slovensky Türkçe ไทย (Thai) עברית (Hebrew) Or visit the ESET home page. Facebook Twitter YouTube LinkedIn Contact Privacy Legal Information Return Policy Sitemap ESET © 2008–2016 ESET North America. All rights reserved. Trademarks used herein are trademarks or registered trademarks of ESET spol. s r.o. or ESET North America. All other names and brands are registered trademarks of their respectiv
not start [SOLVED] in my case Posted by: nesomis (---.dynamic.isp.telekom.rs)Date: February 06, 2011 01:34AMHi,when try to start wapmapache servis got massage:Windows could not start the wampapache on Local Computer. For more informattion, review the System Event Log. If this is a non-Microsoft
Service Specific Error Code 4
service, contact the service vendor, and refer to service-specific error code 1.Log error windows could not start apache 2.4 on local computer xampp fileStarting the Apache2.2 serviceThe Apache2.2 service is running.] Apache/2.2.17 (Win32) configured -- resuming normal operations[Tue Nov 23 18:57:59 2010] windows could not start the service on local computer error 1 incorrect function [notice] Server built: Oct 18 2010 01:58:12[Tue Nov 23 18:57:59 2010] [notice] Parent: Created child process 4476[Tue Nov 23 18:57:59 2010] [notice] Child 4476: Child process is running[Tue Nov 23 18:57:59 http://support.eset.com/kb5550/?viewlocale=en_US 2010] [notice] Child 4476: Acquired the start mutex.[Tue Nov 23 18:57:59 2010] [notice] Child 4476: Starting 64 worker threads.[Tue Nov 23 18:57:59 2010] [notice] Child 4476: Starting thread to listen on port 80.What to do?Also try from cmd promptMicrosoft Windows XP [Version 5.1.2600](C) Copyright 1985-2001 Microsoft Corp.C:\>c:\wamp\bin\apache\apache2.2.17\bin\httpd.exe(OS 10048)Only one usage of each socket address (protocol/network address/port)is normally permitted. : make_sock: could not http://forum.wampserver.com/read.php?2,70986,70987,quote=1 bind to address 0.0.0.0:80no listening sockets available, shutting downUnable to open logsEdited 2 time(s). Last edit at 02/06/2011 02:35AM by nesomis.Options:Reply•QuoteRe: apache can not start Posted by: nesomis (---.dynamic.isp.telekom.rs)Date: February 06, 2011 02:34AMsorry for bad english!Solved !!!!I killed process by process with task manager and restarting apache service each time. Also each time i repeat in cmd prompt netstat -ao.when I see that port 80 is free, I know wich process cause that. Check which application start process and remove.Options:Reply•QuoteRe: apache can not start Posted by: nureiman11 (203.82.87.---)Date: March 07, 2011 02:12PMi got same message when i try to start wampapache. can i install wamp in windows server 2003?Options:Reply•QuoteRe: apache can not start [SOLVED] in my case Posted by: tusharkas (117.239.190.---)Date: October 15, 2013 03:33PMWe are facing same issue.Options:Reply•QuoteRe: apache can not start [SOLVED] in my case Posted by: RiggsFolly (---.as13285.net)Date: October 15, 2013 04:11PMThen you have something else using port 80.Doleft click the wampmanager icon in the system tray -> Apache -> Service -> Test port 80What does it report?Options:Reply•QuoteGo to:Forum List•Message List•Search•Log InSorry, only registered users may post in this forum.Click here to login
contribution towards the costs, the time and effort that's going in this site and building. Thank You! Steffen Apache Lounge https://www.apachelounge.com/viewtopic.php?p=8855 is not sponsored by anyone.Your donations will help to keep this site alive and well, and continuing the building of the binaries. Window could not start the Apache 2 on local computer... Apache Forum Index -> Apache View previous topic :: View next topic Author Message yskw@carillongroup.com.auJoined: 19 Sep 2007Posts: 3 Posted: Wed could not 19 Sep '07 10:31 Post subject: Window could not start the Apache 2 on local computer... My Apache 2 is in window xp. Few days back the services stop running, so I have tried to restart the services but it say Window could not start the Apache 2 on local computer, for more information, review the System could not start Event Log, if this is non-Microsoft Service, contact the service vendor and refer to service specific error code 1. All local connections are OK. Window Event Log has no specific indication of the problems either. and I checked root -webserver -logs-error, I found the record below as: [Wed Sep 12 14:47:42 2007] [error] [client 127.0.0.1] File does not exist: D:/Web/WebServer/Apache2/htdocs/themes, referer: http://localhost/phpmyadmin/tbl_structure.php?db=news&token=c0814a14776dea536bf6e420a07b0907&table=aggregation_feed [Wed Sep 12 14:48:05 2007] [error] [client 127.0.0.1] File does not exist: D:/Web/WebServer/Apache2/htdocs/themes, referer: http://localhost/phpmyadmin/tbl_structure.php?db=news&token=c0814a14776dea536bf6e420a07b0907&table=aggregation_feed [Wed Sep 12 14:48:39 2007] [error] [client 127.0.0.1] File does not exist: D:/Web/WebServer/Apache2/htdocs/themes, referer: http://localhost/phpmyadmin/db_create.php Anyone have any idea what the problems might be? Appreciate it very much if you could have any Back to top tdonovanModeratorJoined: 17 Dec 2005Posts: 610Location: Milford, MA, USA Posted: Wed 19 Sep '07 18:10 Post subject: Presuming you are running Apache version 2.2.{something?} - in a DOS window, try going to your Apache \bin directory and start Apache with this command: Code: httpd.exe -w -e debug This may give you a more informative error messa