ID: 28740 Comment by: justin at jphil dot net Reported By: colorprint at mail dot ru Status: Bogus Bug Type: IIS related Operating System: Windows Server 2003 PHP Version: 4.3.7 New Comment:
I can confirm that with PHP5 running as ISAPI on IIS 6 on Windows Server 2003 SE the access violation "bug" if indeed that's what it is, is present: "PHP has encountered an Access Violation at 016F73DD" appears at the end of every page. Previous Comments: ------------------------------------------------------------------------ [2004-07-01 13:25:58] jmertic at ncscredit dot com Is someone looking into this? It's obviously a bug in PHP itself since it's been confirmed on several different sites where and upgrade from 4.3.6 or older to 4.3.7 is giving this error ( and also is in the 5.0 series according to some of the comments ). It also seems to be related to using MySQL; is this limited to PHP's builtin MySQL support or does it also encompass the PEAR DB module? This is going to hurt PHP 5 adoption on Windows if this isn't taken care of. ------------------------------------------------------------------------ [2004-06-29 11:44:31] fidanza at uniroma3DOT dot it PHP5 RC3, windows xp pro IIS 5.1 Access Violation: every time at the same memory address, on every page same problem on WIN 2000 ------------------------------------------------------------------------ [2004-06-26 15:05:07] renato at ostorero dot it Same problem here since upgrade to 4.3.7 ... I'm moving back to 4.3.6 ------------------------------------------------------------------------ [2004-06-23 12:55:34] michiel at techconnect dot nl We have same problem now on our webserver. Win2003/MySQL and PHP 4.3.7 http://www.techconnect.nl/info.php the info.... problem exists sometimes (but not always) on: www.tcmagazine.net, www.tcdsl.nl, www.nk-halo.nl and www.gameconnect.nl ------------------------------------------------------------------------ [2004-06-21 14:25:37] magnus2 at nova dot nu Same here. I've always gotten this error (PHP has encountered an Access Violation at xxxxxxx) when running PHP 4.3.x (any version and for both CGI and ISAPI) on Windows 2000 or Windows 2003 that connects to MySQL. I have other sites on same machines connecting to MSSQL that works fine. In Windows 2003 I've isolated the servers in different applications pools (to be able to restart them seperately) and it's only sites using MySQL where this error occur. It can be a few hours between but sometimes it's days. For example on same machine I've set up two phpbb (http://www.phpbb.com) forums, one using a MySQL 4.0.16 database and the other a MSSQL 2000 SP3 database. Both sites in different application pools. Rest of the config is identical (Win 2003, PHP 4.3.5, ISAPI) and it's only the forum site using MySQL that will get this error every couple of days. I've read on other posts that it could be related to pconnect() or that PHP gets "unloaded" but I don't know what that is supposed to mean. Seems to be an issue when you combine IIS,PHP,MySQL on Windows. I've never seen a final soultion for this. ------------------------------------------------------------------------ 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/28740 -- Edit this bug report at http://bugs.php.net/?id=28740&edit=1
