ID:               21688
 Updated by:       [EMAIL PROTECTED]
 Reported By:      [EMAIL PROTECTED]
-Status:           Open
+Status:           Feedback
 Bug Type:         IIS related
 Operating System: win2k advanced server
 PHP Version:      4.3.0
 New Comment:

Please try using this CVS snapshot:

  http://snaps.php.net/php4-STABLE-latest.tar.gz
 
For Windows:
 
  http://snaps.php.net/win32/php4-win32-STABLE-latest.zip




Previous Comments:
------------------------------------------------------------------------

[2003-02-06 10:05:18] [EMAIL PROTECTED]

ok, on my workstation I have Visual Studio and thus I know the
CGI-version of PHP actually crashed.

Here is the CGI-IIS-error:

'CGI Error
The specified CGI application misbehaved by not returning a complete
set of HTTP headers. The headers it did return are:'

Here the popup's:
Application popup: php.exe - Application Error : The instruction at
"0x1b00997b" referenced memory at "0x1b00997b". The memory could not be
"read".

Application popup: php.exe - Application Error : The instruction at
"0x10030727" referenced memory at "0x01790dd8". The memory could not be
"read".

------------------------------------------------------------------------

[2003-02-06 09:43:29] [EMAIL PROTECTED]

It seems that when the buffer contents is very small (when using output
buffering ?? or under normal usage, still looking into that) doens't
return headers and/or body/wrong headers (don't know which one).

The CGI-interface of IIS doesn't know how to handle it anyway.

Hope this was usefull.

------------------------------------------------------------------------

[2003-01-16 09:21:48] [EMAIL PROTECTED]

I'm using php 4.3.0 and IIS 5, Win2kadv

As already a couple of others found out, PHP misbehaves, when installed
as CGI under Win2k advanced server. the scripts more than often time
out and the server announces the following error message - sometimes
the server even hangs totally - but in any case there are a lot of
php.exe processes in the server's memory left after shutting IIS down:

The script /xxx/index.php with parameters '' has not responded within
the configured timeout. The HTTP server is terminating the script.
For additional information please visit micro$oft website bla bla
bla...

Who knows a cure for this IIS version? As I don't have any problem
under apache for windows 

Somebody posted a registry hack how to stop that. Could you repost
that?


------------------------------------------------------------------------


-- 
Edit this bug report at http://bugs.php.net/?id=21688&edit=1

Reply via email to