PHP 5.3 on IIS gives 404 error in CGI mode

cgiiisPHP

Slowly losing my mind here. I had PHP 5.2 working fine
(ISAPI) under IIS, but for some extension I needed 5.3. So
no worries, I installed this but it turns out ISAPI is not
supplied anymore.

I followed the install tutorials for fastcgi and ended up
with a 500 internal server error for every PHP page served.

So my current situation is:
I have fastcgi removed.
In my websites I have added PHP (head, get, post) and routed
them to c:\php\php-cgi.exe.

Result: every PHP page I try (even the ones with just text)
gives 404 not found error. Any HTML file I put in the same
folder, serves without a hitch.

Who can help me please… How hard can something like this
be right? For me apparently very hard.

Extra information:

ran the installer as suggested below. Set it to use fastcgi.
my fcgiext.ini file looks like this now:
[types]
php=c:\php\php-cgi.exe
[c:\php\php-cgi.exe]
exepath=c:\php\php-cgi.exe
from the command-line a 3 line PHP file with just phpinfo(); works fine
from the server the same PHP file with just phpinfo(); results in the internal server 500 error.
from the server a PHP file with just text works fine
when changing the document types in IIS management console and point the PHP extension directly to c:\php\php-cgi.exe results in 404 for every PHP file
the php.ini is the php.ini.production file which came in the distribution. No edits were made.

Setting the IIS PHP handler directly to PHP (not via
fastcgi) c:\php\php-cgi.exe results in the following:

display a PHP page with only text….works fine
display a page with only phpinfo(); results in 404 not found

Best Answer

I found the problem. In the php.ini there are some values which need to be set for CGI and IIS. The force_redirect needs to be 0. Furthermore, the PHP extension needs to be added in the webextensions sections of IIS.

Those things fixed the problems.

Related Solutions

How to Show PHP Error Messages on IIS 7

With IIS7, it doesn't pass the errors through by default. It's "existingResponse" that needs to be set.

You can set it by running the following (make sure to replace {sitename} with your site name).

c:\windows\system32\inetsrv\appcmd.exe set config "{sitename}" -section:system.webServer/httpErrors /existingResponse:"PassThrough" /commit:apphost

Php – IIS/PHP/FCgi wrong setup – No page no error

I recently implemented a similar setup:

Windows Server 2003 Web Edition
IIS / FastCGI (http://www.iis.net/expand/fastcgi)
PHP 5.3.1 (installed via zip file into c:\php)

From my deployment notes, the install steps were:

Download PHP 5.3.1 zip (http://windows.php.net/download/, note the "Which version do I choose?" section)
Install into c:\php
Test php -v works on the command line (in c:\php)
Associate .php with FastCGI: IIS Manager -> machine -> Web Sites -> site -> right click, choose properties -> choose "Home Directory" tab, click "Configuration", Mappings tab. Config for .php looks like:

alt text

Configure FastCGI's config file (C:\WINDOWS\system32\inetsrv\fcgiext.ini) with at least:

    [Types]
    php=PHP

    [PHP]
    ExePath=c:\php\php-cgi.exe

Append/change the following to c:\php\php.ini. Without this config, my config bounces between giving blank pages and not loading at all (I guess this is your problem):

    fastcgi.impersonate = 1
    fastcgi.logging = 0
    cgi.fix_pathinfo=1
    cgi.force_redirect = 0

Set
```
display_errors
```
on in c:\php\php.ini and uncomment extension=php_mysql.dll.
Restart IIS for the site (click the stop/play buttons)

In this config, you've essentially got two components, the plumbing between IIS-FastCGI-PHP, and PHP itself. I'd recommend isolating which of these isn't working:

Temporarily edit fcgiext.ini and point the PHP ExePath to something different, e.g. c:\php\nothere.exe. If the server starts returning "The FastCGI executable could not be found" for PHP requests, then I'd FastCGI was working correctly, and PHP is at fault.
Run PHP with its default config, the fastcgi/cgi changes above and display_errors on. You'll need to restart IIS (and possibly kill off any php-cgi processes) for the site you're restarting for the changes to be recognised.
Run PHP on the command line with a simple phpinfo(); script, to check basic operation, and note where the loaded php.ini is. This checks a rogue config file (e.g. in c:\, c:\windows etc) is not being used.

These steps confirm (at least) the PHP executable is being invoked, with the most basic config.

hope this helps,

Lockie

Related Topic