ID: 25863
Comment by: scott at decisivecommunications dot com
Reported By: salmanarshad2000 at yahoo dot com
Status: Closed
Bug Type: CGI related
Operating System: win32 only
PHP Version: 4CVS, 5CVS, 6CVS..
New Comment:
I had tons of problems getting php5 to work in IIS 5.1. So many reports
have you just check phpinfo(); to see if it is working after an install,
but once you run something with more complex (Wordpress) code it all
goes to hell. I'm not pointing fingers I don't know where the bug lies,
PHP, IIS, MySQL???
For myself some problems (like blank pages that shouldn't be) we fixed
by using the CGI instead of ISAPI.
But then I got CGI crashing on the WordPress login.
I started over again with PHP 4.3.8 CGI installer and everything is now
apprently working smoothly.
Some boards reported turning of Zend Optimzation in the 5.0.1 PHP ini
but I didn't even have that setting.
Previous Comments:
------------------------------------------------------------------------
[2004-06-29 12:03:00] closedbolt at gmx dot de
Seems like php.exe in php 5 rc3 does not prepend any headers.
--> cgi error in IIS
php-cgi.exe does... --> works fine for me now.
Example:
test.php
<? echo "hi"; ?>
C:\php>php.exe test.php
hi
C:\php>php-cgi.exe test.php
Content-type: text/html
X-Powered-By: PHP/5.0.0RC3
hi
C:\php>
------------------------------------------------------------------------
[2004-06-23 18:38:14] tincanmann at hotmail dot com
Hi, thanks for all the other posts and hopefully this can help someone
else!
I also struggled with this problem of getting PHP to run on IIS. I
solved it slightly differently on my development server to the live
production server, both running Win2003 Server (production being more
patched, secure, etc).
1) Ensure anonymous access not allowed by editing the website details
in IIS.
This solved my one server but not the other. However, it all seems to
stem from the security and permissions.
2) Try access the website using https:// instead of http:// ...
strange, I know, but it worked for the production server (and saved me
having to rewrite in ASP).
Gareth
------------------------------------------------------------------------
[2004-05-26 15:36:11] onderoz at zmail dot sk
PHP5 Release candidate 2 + IIS5 on W2K Advanced Server.
Still having the same problem.. The damned CGI misbehaved bla bla bla..
I need a complete SOLUTION for this, not WORKAROUND, if we're talking
about a complete language.
What i did :
1.. Downloaded *latest* version of the PHP (5 RC2)
2.. Expanded zip file to the directory C:\PHP5\
3.. added paths to PATH as C:\PHP5;C:\PHP5\EXT as in folder tree.
4.. added extension .php and .php5 with c:\php5\php.exe %s %S
5.. added extension to HKEY_CLASSES_ROOT
6.. added pathinfo to HKEY_LOCAL_MACHINE
7.. gave permissions -full control- to IUSR_*, IWAM_*, EVERYONE on
C:\PHP5 and c:\inetpub\wwwroot\PHP5SCRIPTS
8.. edited php.ini file
a. cgi.force_redirect=0
b. ;doc_root=
so.. what's next?!?
1.. how should I get this system working with PHP?
2.. do I have to mess with these with every new
installation/upgrade/system change?
thanks folks, for *not* helping us newbies by not providing an
automated system for the installation process.
Onder
------------------------------------------------------------------------
[2004-05-08 20:20:53] dmeeking at shaw dot ca
I found that excluding c:\php\ from my (Norton) virus scanner fixed the
problem. Some comments led me to believe that windows was getting
grumpy when multiple requests were being handled by php.exe. This made
me wonder if the antivirus was locking the file, since it was set to
scan every exe upon execution. Turning off scanning on the PHP folder
has fixed this problem for me (iis5 / PHP 4.3.6).
------------------------------------------------------------------------
[2004-04-28 18:19:25] david dot blair at nsi1 dot com
I need to retract my earlier statement of:
"After the reset, the CGI errors occurred only once per page."
3 days in and we've had a couple reoccurring page errors...the
frequency is going down, or people aren't getting back to me on the
problem...the latter is most likely the case here.
I should also state that we are running IIS 6 on 2003(I previously
wrote 2000...my fault)
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/25863
--
Edit this bug report at http://bugs.php.net/?id=25863&edit=1
