Apache Error 1
Contents |
Analytics 8.0x Symptoms Symptoms The copy of Apache installed by Webtrends fails to start using the services control panel, the apache.exe file, or by restarting the Webtrends - User interface service. You may also see one or more of the following error apache start error 1 messages: The Webtrends - Apache service terminated with service-specific error 1 (0x1). The Apache service
Apache Error 1 0x1
named reported the following error: >>> Unable to open logs. Starting Apache.exe manually from the bin directory may yield one or more
Couldn T Start Apache
the following errors: The Apache service named reported the following error: >>> no listening sockets available, shutting down. The Apache service named reported the following error: >>> The port number "pdxfasteenn02:" is outside the appropriate range
Service Terminated With Service Specific Error 1
(i.e., 1..65535). The Apache service named reported the following error: >>> Syntax error on line 222 of C:/Program Files/Webtrends/common/apache/conf/httpd.conf: You have tried renaming the Apache and Tomcat directories and doing a modified installation to create them from scratch and the issue remains unresolved. Cause Cause Resolution Resolution 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) apache error 1 windows 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 chec
the Apache2.2 Service apache error code 1 fails to start. In looking at the event log apache unable to open logs windows 7 I see the following error msg.. The Apache2.2 service terminated with service-specific error 1 service specific error code 1 apache (0x1). Any idea on what went wrong and how I get the Apache Server running again. Thanks for any help. Dave Brandt http://kb.webtrends.com/articles/Problem/Apache-fails-to-start-with-service-specific-error-1 Dan_Grossman 2010-01-07 18:00:33 UTC #2 There are lots of things that can cause that error. Is there nothing in Apache's error log file (not the Windows event log)? dklynn 2010-01-07 20:51:48 UTC #3 Dave, First, Welcome to SitePoint's Apache forum. As Dan said, there are MANY https://www.sitepoint.com/community/t/apache-service-fails-to-start/5787 things which could have caused the problem. Failure to start is generally a sign that your httpd.conf has some bad syntax in it but a power failure is not a likely source of an error like that. From the lack of any further information, I'd think the problem is that, when you installed Apache, you didn't PREVENT IIS from starting with WinDoze. Check Start | Run and services.msc to see whether IIS has confiscated port 80. If not, then you probably have corrupt files (and a damaged HD) due to the power surges when the power came back on. Sorry for that news. Regards, DK linux7802 2010-01-12 16:49:18 UTC #4 Have you tried config test...? Home Categories FAQ/Guidelines Terms of Service Privacy Policy Powered by Discourse, best viewed with JavaScript enabled Shop Versioning Reference Articles Premium
ID: 20007|Last Revised: July 22, 2016 Tweet In cases where the ESET Remote Administrator Web Console (ERA http://support.eset.com/kb5550/?viewlocale=en_US Web Console) is not running, check whether the Apache Tomcat service is running (open a Rundialog, typeservices.msc, clickOK, locate theApache Tomcatservice, and then verify http://forum.wampserver.com/read.php?2,91044,91064 that Running is listed in theStatuscolumn); if it is not, try to start the service manually by selecting it and clicking Start. While trying error 1 to start theservice, you might receive the following error message, which may result from a Java update: "Windows could not start 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 apache error 1 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 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 P
WampApache - error code 1 (Windows 7) Posted by: ICIT (---.dyn.iinet.net.au)Date: October 24, 2012 09:40AMIn Windows 7, the WAMP tool in the system tray cannot start Apache.If I try to start wampapache using services,msc, I receive the following error:Windows could not start the wampapache 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 service-specific error code 1I am not running Skype, and nothing is using port 80. WAMP tells me this in WAMP > Apache > Service > Test Port 80.How can I resolve this? Thanks.Options:Reply•QuoteRe: Can't start WampApache - error code 1 (Windows 7) Posted by: RiggsFolly (---.ppp.as43234.net)Date: October 24, 2012 05:46PMLook in the system event log and if you cannot see the problem post the relevant info here.Control Panel -> Administrative Tools -> Event ViewerOptions:Reply•QuoteRe: Can't start WampApache - error code 1 (Windows 7) Posted by: ICIT (---.dyn.iinet.net.au)Date: October 25, 2012 03:53AMThanks RiggsFolly.Log Name: SystemSource: Service Control ManagerDate: 25/10/2012 9:52:17 AMEvent ID: 7024Task Category: NoneLevel: ErrorKeywords: ClassicUser: N/AComputer: WebsiteDescription:The wampapache service terminated with service-specific error Incorrect function..Event Xml: