I have the same problem.  However, I even unloaded all extensions and the Optimizer thinking that they had to do with it but it still crashes.

Hi there,

we've got the same problem too. Even on older Versions of PHP it appeares from time to time. 4.1.1 creates the same SysLog-Message on W2k Sp2, but we only use ODBC.
Only NET STOP IISADMIN solves the problem, but from time to time you need to reboot the machine.

Using the Zend Optimizer or not is not the problem, it is re-creatable without Zend...

One thing to mention is, that it only appears on querys that are quite time consuming.

regards,
Bernd

I was experiencing this type of crashing over and over myself with win2k SP2.  The solution was to add the ISAPI DLL in the ISAPI Filters list as well as the App Mappings.  After this ISAPI has been rock solid.  This is the same solution as in this bug report: http://bugs.php.net/bug.php?id=15324 .  

Note: I did not do this at first because the PHP Manual specifically said that I should not do so (http://www.php.net/manual/en/install.iis.php) unless I needed it for HTTP Authentication.  Maybe someone should place some errata in the documentation?

We already had the php4isapi.dll als ISAPI-Filter included, but nevertheless it does not work at all.

The crashes are gone for sure, but the new flavour ist that sporadically the connection to an Oracle Database get's lost somehow, somewhere, and all my scripts do not work anymore.

The problem occures more often after the server has had a heavy load.

Point is: PHP does not crash anymore, but in order to have a working DB connection I have to restart the iisadmin-service.

regards,
Bernd

As normal with these kinda bugs my ISAPI/IIS is rock solid so its very difficult to track this down. Im moving this bug to critical as it affects quite a few people. If any of you can compile on your webservers I would be interested to see if you compile what happens. Also make sure you always use the latest version of PHP as we are always fixing Thread Safety issues (To the best of my knowledge this is probably what is causing this).

Hopefully we can gradually improve performance of the ISAPI extension. If you have any other information or a short script that seems to cause it a lot then please add information about it in this bug report.

Also please try unloading extensions from PHP and testing without that as it might be a thread safety issue in that extension.

Basically until we can get some more concerete information about this lack of stability its very difficult to track down so anything that may help is very welcome.

- James

Please try using this CVS snapshot:

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

There were some thread-safety issues fixed just recently in CVS so please try the snapshot.

Jani.. Im using latest CVS.

Anyway. A bit more of a probe and I have come up with the following stack trace (Caused when IIS is under heavy load using the script 

<?php 
for($i = 0; $i < 5000; $i++)
	echo microtime();  

?>

and doing lots and lots of requests

NTDLL! 77f7d293()
_emalloc(unsigned int 256, char * 0x013b7a80 `string', unsigned int 27, char * 0x00000000, unsigned int 0) line 154 + 62 bytes
zend_stack_init(_zend_stack * 0x018f2ce0) line 27 + 30 bytes
zend_init_compiler_data_structures(void * * * 0x018f1fe0) line 73 + 21 bytes
init_compiler(void * * * 0x018f1fe0) line 100 + 9 bytes
zend_activate(void * * * 0x018f1fe0) line 588 + 9 bytes
php_request_startup(void * * * 0x018f1fe0) line 835 + 9 bytes
HttpExtensionProc(_EXTENSION_CONTROL_BLOCK * 0x00814888) line 756 + 12 bytes
WAM! 5a857a91()
WAM! 5a858634()
W3SVC! 5aa51473()
W3SVC! 5aa51385()
W3SVC! 5aa40a38()
W3SVC! 5aa40bc2()
W3SVC! 5aa4ad47()
W3SVC! 5aa3a6c9()
W3SVC! 5aa39187()
W3SVC! 5aa39416()
ISATQ! 65f18599()
ISATQ! 65f19630()
e877e317()

Havnt particularly looked at this in any depth yet but will do... Back to critical as IIS is unstable.. although its not critical for all systems it is for IIS & Windows so its certainly not a show stopper but needs to be kept in mind and worked on gradually..