ID: 16773 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] -Status: Feedback +Status: No Feedback Bug Type: IIS related Operating System: Windows 2000 Server PHP Version: 4.2.0 New Comment:
No feedback was provided for this bug for over 2 weeks, 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". Previous Comments: ------------------------------------------------------------------------ [2002-10-09 11:31:52] [EMAIL PROTECTED] 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 ------------------------------------------------------------------------ [2002-04-23 22:12:38] [EMAIL PROTECTED] That is the most common problem with the ISAPI filter of PHP. I would just run it as CGI. ------------------------------------------------------------------------ [2002-04-23 18:38:42] [EMAIL PROTECTED] Loaded modules are php_mssql.dll and php_socket.dll Under the Home Directory tab, clicking "Unload" will return things to normal. As this appears to be a flaw in the memory management, would unticking "Cache ISAPI Applications" help? ------------------------------------------------------------------------ [2002-04-23 18:33:26] [EMAIL PROTECTED] Sorry for the unhelpful title, but the PHP ISAPI filter dies, leaving the below messages in the logs. One page would not load, and then subsequent pages were "PHP has encountered an Access Violation at 77FCB2A7". The page always loads fast - all it does are a couple of MS SQL queries via an abstraction library (namdal-ms.php). open_database() calls mssql_pconnect() Application protection is "Low" as recommended in bug #15333. PHP error log: [24-Apr-2002 10:21:54] PHP Fatal error: Cannot redeclare open_database() (previously declared in namdal-ms.php:39) in namdal-ms.php on line 38 [24-Apr-2002 10:22:16] PHP Fatal error: Maximum execution time of 30 seconds exceeded in namdal-ms.php on line 68 Windows Event Viewer (System): Event Type: Error Event Source: WAM Event Category: None Event ID: 204 Date: 24/04/2002 Time: 10:21:54 a.m. User: N/A Computer: ... Description: The HTTP server encountered an unhandled exception while processing the ISAPI Application ' php4ts!php_execute_script + 0x16A '. Event Type: Error Event Source: WAM Event Category: None Event ID: 204 Date: 24/04/2002 Time: 10:21:54 a.m. User: N/A Computer: ... Description: The HTTP server encountered an unhandled exception while processing the ISAPI Application ' php4ts!php_request_startup + 0x1F0 + 0xFBBE824 '. Event Type: Error Event Source: WAM Event Category: None Event ID: 204 Date: 24/04/2002 Time: 10:21:54 a.m. User: N/A Computer: ... Description: The HTTP server encountered an unhandled exception while processing the ISAPI Application ' php4ts!php_execute_script + 0x16A '. Event Type: Error Event Source: WAM Event Category: None Event ID: 204 Date: 24/04/2002 Time: 10:21:54 a.m. User: N/A Computer: ... Description: The HTTP server encountered an unhandled exception while processing the ISAPI Application ' ntdll!RtlSizeHeap + 0x78 ntdll!RtlFreeHeap + 0x100 php4ts!shutdown_memory_manager + 0x1BC '. Event Type: Error Event Source: WAM Event Category: None Event ID: 204 Date: 24/04/2002 Time: 10:22:16 a.m. User: N/A Computer: ... Description: The HTTP server encountered an unhandled exception while processing the ISAPI Application ' php4ts!php_execute_script + 0x16A '. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=16773&edit=1
