| Author |
|
GeoffreyB
Joined: 09 Oct 2006
Posts: 12
Location: Mornington, Victoria, Australia
|
 Posted: Mon 09 Oct '06 4:14 Post subject: Apache 2.2.3 won't load PHP module |
 |
|
I am extremely frustrated. I have had development server set up on my PC (running on XP Professional Service Pack 2) using Apache 1.3 and PHP 4.4.3.
I have downloaded the Zend Framework with the view of using this as a core set of functions to build my apps. Framework requires PHP5 so I set about installing PHP5 and thought I would upgrade the server as well to Apache 2.2.
I installed from the most recent ".msi " available from Apache.org and install worked fine. Next I alter httpd.conf to load PHP
| Code: | LoadModule php5_module "c:/php-5/php5apache2.dll"
AddType application/x-httpd-php .php
PHPIniDir "C:/php-5" |
Whenever I start the server I get the following error message:
| Code: | | httpd: Syntax error on line 116 of C:/Program Files/Apache Software Foundation/Apache2.2/conf/httpd.conf: Cannot load C/php-5/php5apache2.dll into server: The specified module could not be found |
even though the ".dll" is exactly where it is supposted to be.
Please help I have wasted many hours trying to get this happening.  |
|
| Back to top |
|
James Blond
Moderator
Joined: 19 Jan 2006
Posts: 7373
Location: Germany, Next to Hamburg
|
| Posted: Mon 09 Oct '06 9:40 Post subject: |
|
|
| php 5.1.6 php5apache2.dll is not designed for Apache 2.2.x But you can download that dll from http://www.apachelounge.com/download/ and replace that in your php folder. Than it should work |
|
| Back to top |
|
GeoffreyB
Joined: 09 Oct 2006
Posts: 12
Location: Mornington, Victoria, Australia
|
| Posted: Mon 09 Oct '06 10:30 Post subject: Thank you! Now have other problem |
|
|
I have done this thanks. In the meantime I have also downloaded the Apache build from Apache Lounge. Now I am having another problem which I cannot fix due to my ignorance of port allocation.
When I test httpd I get the following message:
| Code: | <OS 10048>Only on usage of each socket address (protocol/network address/port) is normally permitted. : make_sock: could not bind to address 0.0.0.0:80 no listening sockets available, shutting down
Unable to open logs |
How do I find out what is assigned to what port?  |
|
| Back to top |
|
CanUuRead
Joined: 18 Sep 2006
Posts: 38
|
| Posted: Mon 09 Oct '06 10:43 Post subject: |
|
|
From DOS/Command Prompt:
netstat -b
Did you un-install the previous Apache installation? Some dude named pnllan wrote something interesting about Apache Software Foundation MSI files, pertaining to uninstalls...It might be worth a read:
http://www.apachelounge.com/viewtopic.php?t=570
You can also check the properties of the Apache service to make sure it's pointing to the correct location.
There are a variety of Intenet Apps that like to 'snag' Port 80 (default HTTPD port). Netstat can give you the info quickly...it will show port and the Application Using It...include the actual executable.
Hope this helps. |
|
| Back to top |
|
GeoffreyB
Joined: 09 Oct 2006
Posts: 12
Location: Mornington, Victoria, Australia
|
| Posted: Tue 10 Oct '06 2:54 Post subject: netstat -b does not report anything for port 80 |
|
|
I have run netstat -b and it does not report anything connected to Port 80. Any other suggestions  I'm going nuts here!  I've lost too much production time  |
|
| Back to top |
|
CanUuRead
Joined: 18 Sep 2006
Posts: 38
|
| Posted: Tue 10 Oct '06 6:49 Post subject: |
|
|
Have you checked the Services.msc to see if Apache2 is running before trying to start the AL version of Apache? Have you checked the properties of Apache2 service to see if it is pointing to the correct binary? I ask this last question since most her at AL who use the AL version setup the Apache root at C:\Apache2.
Ok, you said you downloaded and installed the latest MSI from Apache. Then you said that you downloaded Apache from here. Did you uninstall the MSI file? or did you overwrite the MSI with the AL version? Just curious since you switched 'mid-stream'.
Again, take a look at:
http://www.apachelounge.com/viewtopic.php?t=570
Many people here who have had problems say that it has helped get them up and running. |
|
| Back to top |
|
GeoffreyB
Joined: 09 Oct 2006
Posts: 12
Location: Mornington, Victoria, Australia
|
| Posted: Tue 10 Oct '06 7:38 Post subject: Still No Go |
|
|
I have carried out these instructions at http://www.apachelounge.com/viewtopic.php?t=570 to the letter.
I started my system in safe mode with networking which allowed me to install the service but not start it.
What next? |
|
| Back to top |
|
CanUuRead
Joined: 18 Sep 2006
Posts: 38
|
| Posted: Tue 10 Oct '06 8:52 Post subject: |
|
|
Why start in Safe Mode with Networking? This does not make any sense.
What happens when you try to start Apache? Same error with regards to Ports?
Error messages?
Any events in the Event Viewer?
If Apache will not start, it will bring up a dialog box stating so. You can then go to the Event Viewer to see what the error(s) is/are.
Just a note: You seem irritated. Realize that the people here are not in any way affliated with Apache Software Foundation. We are simply Apache HTTPD users who try our best to help others. When you state something like it will not start - think about how vague that is. |
|
| Back to top |
|
GeoffreyB
Joined: 09 Oct 2006
Posts: 12
Location: Mornington, Victoria, Australia
|
| Posted: Tue 10 Oct '06 11:40 Post subject: An apology |
|
|
I am sorry if I have come across in an offensive manner. This is certainly not my intent. I am extremely appreciative of the assistance that you are providing. I am however frustrated, with nothing other than my ignorance of Windows XP operating system and my inability to solve this issue.
These are the messages from the event viewer for any attempt to start httpd:
| Code: | The Apache service named reported the following error:
>>> (OS 10048)Only one usage of each socket address (protocol/network address/port) is normally permitted. : make_sock: could not bind to address 0.0.0.0:80 |
| Code: | The Apache service named reported the following error:
>>> no listening sockets available, shutting down |
| Code: | The Apache service named reported the following error:
>>> Unable to open logs |
I am fairly sure that this is not an Apache issue and that it is something else that is occupying port 80. Which is why I start in safe mode to see if I got the same errors. In safe mode I could install the service with no errors but you cannot start the service (any service I presume) in safe mode.
I really do appreciate your time and guidance and if there is any other suggestions I will try them and report back.  Thanks |
|
| Back to top |
|
Brian
Joined: 21 Oct 2005
Posts: 209
Location: Puyallup, WA USA
|
| Posted: Tue 10 Oct '06 14:55 Post subject: |
|
|
I have not duplicated this myself in safe mode, but I have to believe that Apache will NOT work, that even with networking functionality, it is very limitted in safe mode.
And I also ask, why would you run a server in safe mode?
Have you attempted to boot the computer up not in safe mode? |
|
| Back to top |
|
CanUuRead
Joined: 18 Sep 2006
Posts: 38
|
| Posted: Tue 10 Oct '06 17:50 Post subject: |
|
|
In addition to Brian's comments, be aware that there are a variety of Internet Application that like to use Port 80. Hence, the netstat request on my part. Next, there is the Windows Firewall that likes to block port 80 by default. Another culprit could be certain Anti-Virus apps have 'security components' built into them that will block port 80. Finallly, some spyware apps attempt to keep other apps from opening a connection to port 80. If you do a search here at AL you notice that others have encountered this problem too. Skype has been reported as a nuisance in this regard. I think I covered the most common port 80 issues.
Out of curiousity, What are you using for the following Apache directives in your Configuration file (httpd.conf)?:
Listen ____
&
ServerName _________________
Please answer this: Did you uninstall the MSI for Apache? You have not indicated that you have - when assisting in troubleshooting I prefer not to rely on supposition. Thanks Mate. |
|
| Back to top |
|
GeoffreyB
Joined: 09 Oct 2006
Posts: 12
Location: Mornington, Victoria, Australia
|
| Posted: Wed 11 Oct '06 1:07 Post subject: Problem solved |
|
|
Thank you to all who contributed to me getting this issue resolved. It was something else grabbing port 80 before httpd. I am not sure what it was, probably Skype. Server is now up and running. It is however not serving PHP pages yet. I know there is plenty of info about that in this forum so I'll push on with that.
Thanks again to all. |
|
| Back to top |
|
CanUuRead
Joined: 18 Sep 2006
Posts: 38
|
| Posted: Wed 11 Oct '06 6:54 Post subject: |
|
|
| Good for you - teach a man to fish... |
|
| Back to top |
|
nitesh
Joined: 22 Jan 2008
Posts: 1
Location: Gurgaon
|
| Posted: Tue 22 Jan '08 4:47 Post subject: Thanks |
|
|
Thanks for posting useful replies over this place. In my case, it was Skype and stopping Skpe solved the problem.
If still someone is facing the problem, you may have to identify which other services are using port 80 which you can accomplish by stopping suspected services one by one. |
|
| Back to top |
|
ianetche
Joined: 24 Jan 2008
Posts: 1
|
| Posted: Thu 24 Jan '08 16:48 Post subject: Skype here too |
|
|
Thanks - on a new install I could not get XAMPP to run - netstat did not show it snagging port 80 - on the advice above I closed it down and lo & behold ....
Thanks to all who contributed. |
|
| Back to top |
|
