Windows Vista Basic + Apache 2.2.6 + PHP 5.2 what goes wrong?

[geoplant]

I've gone through many forums about this same subject and until now I haven't found a satisfying answer so I decided to post the problem myself.

As some of you already know, the actual IIS Service is unavailable in Windows Vista Home Basic and in fact I don't have it so I decided to install Apache 2.2 Webserver into Vista. Everything goes fine. I've created a virtual host and using localhost (port 80) I can view normal html pages.

Ok, now it's time to install PHP 5.2. I install it as Apache 2.2 module. Everything seem to gone nice and smooth, but when I restart Apache service and run simple test.php like:

<?print "hello";?>

I get blank page! Even if i look the source output, that also is blank! But I can see html pages.

When I run httpd in debug mode (command httpd -w -e debug) I get an error message: Only one usage of each socket address <protocol/network address/port> is normally permitted. : make_sock: could not bind to address 127.0.0.1:80 no listening sockets available, shutting down. blaah blaah... :(

This indicates that there is some software listening port 80(webserver, or some other)I can assure you that no program is listening port 80 like Skype or any VOIP software. I've checked this with netstat and TCPView programs.

This is my system configuration:

Windows Vista Home Basic
Apache 2.2.6
PHP 5.2

Apache installed in C:\Apache
PHP installed in C:\PHP
virtual host's root is C:\www

So what can be wrong? Please, help! I've fought this already for hours!

[g1smd]

I have had no end of grief trying to get this stuff working with Vista.

It is a right royal pain.

I have also set up an FTP service to allow me to upload the site to the /www folder. After uploading test files for the site, the site isn't visible in Apache. Using Windows Explorer, I see that the /www folder remains empty even though the FTP view of that folder shows the files as being there.

After much searching, I see that Windows has actually put the uploaded FTP files into some folder under "Application Data" where they remain invisible to Apache.

[jdMorgan]

The usual cause of a "can't bind to socket" problem on Windows is that the bundled IIS server is installed and enabled, and is binding to port 80. When Apache starts and tries to bind to the same port, you get that error.

Uninstall the IIS service Using Add or Remove Programs->Windows Components or disable it using the Administrator Tools->Services dialog.

Jim

[geoplant]

Hi jdMorgan, I have IIS disabled and also WWW Service, but the problem still occurs.. ok I am going to uninstall everything connected to IIS and I get back to you as soon as I've tried it.