ID: 28740 User updated by: colorprint at mail dot ru 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:
It seems fixed in last CVS :) I get last build at http://snaps.php.net/ and there are no more "Access violation" errors :) Previous Comments: ------------------------------------------------------------------------ [2004-07-15 00:39:36] sluster at josephpartners dot com I recently installed a 4.x version of php on IIS6 / Windows 2003 without problems. Today I upgraded to PHP 5 Final, and started having the same errors mentioned above. I did some of my own troubleshooting, after exhausting all of my searches for fixes. I used the php.ini-recommended and it seemed to work fine. No Access errors. However the images generated on the phpionfo page were not working as intended. I experimented with a few different settings for 'output_buffering =' , and finally settled on 1024 which seemed to make the phpinfo page work as intended. I am not absilutely sure that this is the perfect method for fixing whatever is causing this error, but I would be interested to see others try this method and let me (and others) know if you encounter any issues with test code. I do not have any production php to try right now to verify that everything will work ok, but personally I find it daunting that I would have to make so many security changes and buffer size changes to get this to work. 4.x PHP worked as-is with little editing of the php.ini. For troubleshooting purposes, I am using the PHP 5.0 Final release, with no extra modules. ------------------------------------------------------------------------ [2004-07-14 11:17:48] colorprint at mail dot ru This bug is still in PHP 5.0.0 final build too! I think it was not good idea to release final version with this actual bug :( ------------------------------------------------------------------------ [2004-07-13 17:55:08] justin at jphil dot net 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. ------------------------------------------------------------------------ [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 ------------------------------------------------------------------------ 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
