Not enough information was provided for us to be able
to handle this bug. Please re-read the instructions at
http://bugs.php.net/how-to-report.php

If you can provide more information, feel free to add it
to this bug and change the status back to "Open".

Thank you for your interest in PHP.


We really need more information to be able to do anything with this. We know the ISAPI module is less stable then the Unix stuff, and that\'s because there are very little developers checking this out.

Derick

I've been using the ISAPI module (php4isapi.dll) for a while, and it
seems that the module from 4.1.2 is much more stable than the one from
4.2.1 Most crashes happen with big scripts, like phpmyadmin. php gives
than an acces violation. Sometimes it's enough to wait untill all
connections are closed, but in most cases, IIS has to restart. However,
ASP and other ISAPI modules haven't crashed, so the php ISAPI module
doesn't affect any other modules, despite what's told in the readme.

Some detailed information:

Windows 2000 server, all patches and security updates in place,
AMD Athlon 1700+ XP
256 MB DDR ram
41 Processes running, 600-700 threads.
MySQL 4.1
php 4.2.1

IIS 5.0
IIS Config: Running on TCP port 1501, Time-Out: 900s, No ISAPI filters in use, Security set to normal, files with extension .php being processed by the ISAPI module, php4isapi.dll, Server extensions not installed.

Can you provide a minimal sample script that causes it to crash consistently?  What PHP modules are you using?  Have you tried using the low security setting?  See bug 15333.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

I have the same probleme with a Windows XP.NET, IIS and SQL server 2000. In a phpBB forum... No bug with the CGI filter... but it is more slow...