Apache Friends Support Forum

I have installed XAMPP 1.7.1. on Windows XP

Admnistrative Tools -> Servce -> Apache2.2 and clicked "Start"
And message says: Could not start the apache2.2 service on Local Computer
Error 1067: the process terminated unexpectedly.

and appears: Apache HTTP Server has encountered a problem and needs to close. We are sorry for the inconvenience.

What is wrong here ?

What is wrong here ?

Read the Windows event log.

Computer Management -> Application
Right Clicked on the Error and the description says:
Faulting application httpd.exe, version 2.2.11.0, faulting module libapr-1.dll, version 1.3.3.0, fault address 0x000084ad.

What does that mean ?

mickdeman wrote:Computer Management -> Application
Right Clicked on the Error and the description says:
Faulting application httpd.exe, version 2.2.11.0, faulting module libapr-1.dll, version 1.3.3.0, fault address 0x000084ad.

What does that mean ?

I guess it means no one knows, or is too busy to answer. Your post has been up for a week with no attempt at a responce. I'm running into the same problem with this newest install of XAAMP. Can't get Apache to start, and the ports are free, and nothing running on port 80. I have an older install .exe of XAAMP somewhere, which ran with no problems. I have searched and tried all the different suggestions on this forum, and Apache still will not run on XP Pro with this newest release. This is a fresh install of XP Pro, with the latest release of XAAMP. Then again, I may just dump XAAMP altogether, and run a virtual install of Linux, or a dual boot with Linux, and get the real deal. A lot of the answers to some of the newbies on this forum seem to be a little short.

Same problem here. I downloaded the latest version of XAMPP for Windows and have tried to load it on XP Pro with a brand new machine. I have installed and unistalled it five different times and have also tried the Lite version. Every installation has the same problem - Apache runs for a brief moment, then drops off and won't restart.

I have read many threads on this topic. I am certain that there is no conflict on Port 80. I have also tried to start it using the command line and apache.exe, but I can't find apache.exe. In past versions, it was in the xampp/apache/bin subdirectory, but that file does not exist in the latest revision. Makes it awfully tough to trouble shoot this version.

I'm going to try reverting to an older version that has worked for me on a different system (17.0 I believe). If anyone else can resolve this problem, I'd really appreciate a heads-up.

Also the same problem. I have read the readme under the instalation notes and it says:
* System Requirements:

+ 128 MB RAM
+ 256 MB free fixed disk
+ Windows 2000, XP (Server 2003), Vista (Server 2008)
+ all systems 32 bit (64 bit not tested)

Does it mean that Xampp won't work unless my Windows XP Proffesionel has Server 2003? I'm a noob so please bear with me

travismlc wrote:Same problem here

Aqina wrote:Also the same problem

You two also have this message:

mickdeman wrote:Faulting application httpd.exe, version 2.2.11.0, faulting module libapr-1.dll, version 1.3.3.0, fault address 0x000084ad.

I experienced the same problem with a reference to php5ts.dll instead.
It appears that the installer for PHP 5.3.1 will add to the end of the the httpd.conf -file at C:\Program Files\Apache Software Foundation\Apache2.2\conf:

#BEGIN PHP INSTALLER EDITS - REMOVE ONLY ON UNINSTALL
PHPIniDir "C:/Program Files/PHP/"
LoadModule php5_module "C:/Program Files/PHP/php5apache2_2.dll"
#END PHP INSTALLER EDITS - REMOVE ONLY ON UNINSTALL

Reverting to the backup file named httpd.conf.bak will allow the Apache service to start.

I haven't been able to find a fix yet but perhaps someone else will?

you may need to use the windows distribution (install fast-cgi) for windows 2008 server

http://windows.php.net

use the 5.2.11... 5.3 is still under transition for many webhosting companies...

try using the wamp or else try using the lower stable version of the xampp.
1.7.1 has some issues which has been fixed on 1.7.2.
if u want to try use the version 1.5.5 which is quite stable version