We are running win2k and IIS. we used the with isapi module. It seemed that running php crashed the IIS. the service then had to be restarted. We did a swich from isapi to cgi. The only changes made in php.ini where:
_SERVER["GATEWAY_INTERFACE"] CGI/1.1
GATEWAY_INTERFACE CGI/1.1
Is there anything else that needs to be changed?
It looks like php is running as things like include() work, but it's not passing variables and is not reading php functions/commands like phpinfo(). What's going on?
Which version of PHP are you running? I had similar problems with IIS and PHP 4.2.x, but since upgrading to 4.3 the isapi module works fine. Just make sure you aren't using the php installer, use the zip file.
Out of interest, and at the unintended risk of hijacking this thread, what's the advantage of running PHP as ISAPI over CGI? I've had PHP running very successfully as CGI on IIS5 in various versions (now up to 4.3). Am I missing some additional functionality or something?
If PHP runs as ISAPI, will my browser be able to report the document size correctly? At the moment it simply says 'Not available' in the document properties box.
as far as I know the main difference is the way the web server instantiates PHP. When running in ISAPI mode, PHP is treated like a dll and will only be loaded into memory once. Hence, if anything goes wrong: the entire thing will crash.
CGI on the other hand loads an instance of PHP for each script, if one crashes it only affects this one instance, not the entire webserver.
Performance-wise, ISAPI should be faster, because the server doesn't need to load it again and again.
There may be more differences/advantages/disadvantages but this - if true - seems to be the one main difference.
T