#8434 [Com]: PHP has encountered an Access Violation at 01292466

ID: 8434 Comment by: julien@touslesdrivers.com Reported By: svanpoeck@mailplanet.net Status: Bogus Bug Type: IIS related Operating System: Win 2K Server PHP Version: 4.0.4 New Comment: <b>Copy of the e-mail I send to the php team:</b> Hello, I am the webmaster of the website Touslesdrivers.com. I use php 4.3.0 ISAPI under Windows 2000 Server SP3 / IIS 5.0 and an error often appears: PHP has encountered an Access Violation at 0109388E When this error appears, the execution of the php code seems to be stopped and juste the half of the page is displayed with the error :( This error appears randomly on all the website and I think it's a bug in the ISAPI module of php. In CGI mode, it doesn't appears but performances are very bad :/ It's a very inconvenient bug, snif snif. I have seen that I am not the only person which have this error: Per exemple here: http://bugs.php.net/bug.php?id=8434 I tried a lot of parameters in the php.ini but nothing resolves the problem. I signal so the bug to you. I think it will be perhaps better if I signal it on the http://bugs.php.net/ but I try before to mail it to you directly. Sorry for the "bad" english and I hope you will be abble to resolve this bug in the next release. Thanks you very much. PS: You can go on http://www.touslesdrivers.com and after 5/6 pages you will probably have the error... Previous Comments: ------------------------------------------------------------------------ [2002-06-18 18:17:10] sniper@php.net Thank you for taking the time to report a problem with PHP. Unfortunately your version of PHP is too old -- the problem might already be fixed. Please download a new PHP version from http://www.php.net/downloads.php If you are able to reproduce the bug with one of the latest versions of PHP, please change the PHP version on this bug report to the version you tested and change the status back to "Open". Again, thank you for your continued support of PHP. ------------------------------------------------------------------------ [2002-04-18 08:56:19] thomasp@gmx.at we're having nearly the same problem in our company. we're using iis 4 with nt, not 2k... shortly after a reboot the whole iis crashes (sort of). we are using asp and php in different webs. asp is down if the iis crashes. after deactivating mysql the server will work again... that's what we've encountered here today. i would be glad if someone could mail me some more information regarding this ACCESS VIOLATION topic... ------------------------------------------------------------------------ [2001-04-16 06:33:56] jmoore@php.net ANother Access violation in IIS bug. -James ------------------------------------------------------------------------ [2001-01-08 10:05:52] svanpoeck@mailplanet.net Well, that _is_ a good question: I have absolutely no idea which instruction causes the problem ! As said in my report, the error can appear on any of my 30+ scripts on the site. The error does not have a preference for any of the scripts either. It just appears _randomly_ on any of the scripts at a random time and at random frequency. I sometimes have the error 2 to 5 times a day, and sometimes it will not appear for 2 days at all. I know that doesn't help you much, but that's about as precise as I can be. That's why I gave you all the information necessary to rebuild an exact copy of 1 of my scripts and see _if_ you get the error at all. It will be necessary though that you test it on the same platform as I run it: Win 2K Server with IIS 5.0 and PHP-4.0.4 as ISAPI (php4isapi.dll). The database runs on a separate server (Win NT4 Server SP6). Hope you find a clue where to start looking (as a novice, I'd say in the .DLL). If you need any further information, do not hesitate ! Greetings, Steven ------------------------------------------------------------------------ [2001-01-08 08:59:28] dbeu@php.net can you please cut down the code to the min. needed to reproduce it? ------------------------------------------------------------------------ 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/8434 -- Edit this bug report at http://bugs.php.net/?id=8434&edit=1