ID: 37575 Comment by: nishant dot nigam at hkdigitalonline dot com Reported By: richardvernooij at yahoo dot com Status: No Feedback Bug Type: IIS related Operating System: Windows 2003 server PHP Version: 5.1.4 Assigned To: pajoye New Comment:
Hii, I am also facing the same annoying problem from the past few days I'm using PHP 5.2.5 IIS 6 WIN 2k3 and Sql Server as backend Andd while performinng some databbase task i get "PHP has encountered an access violation at ........" After restarting the IIS it gets away for some time and then it returns. Willl Apache solve my problem or is this cozz i'm using some sql server cconnection exteensions in my application. Any help will be appreciated.. Previous Comments: ------------------------------------------------------------------------ [2008-10-31 01:00:01] php-bugs at lists dot php dot net No feedback was provided for this bug for over a week, 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". ------------------------------------------------------------------------ [2008-10-23 15:52:42] paj...@php.net Thank you for this bug report. To properly diagnose the problem, we need a backtrace to see what is happening behind the scenes. To find out how to generate a backtrace, please read http://bugs.php.net/bugs-generating-backtrace.php for *NIX and http://bugs.php.net/bugs-generating-backtrace-win32.php for Win32 Once you have generated a backtrace, please submit it to this bug report and change the status back to "Open". Thank you for helping us make PHP better. I would also suggest to use FastCGI instead (fcgi is available for IIS 6 and 7). ------------------------------------------------------------------------ [2008-10-23 14:11:04] roberto at v-servers dot it I forgot to add to my previous comment that this happen using php 5 as ISAPI, I am not sure if it happen also using it as CGI like I have done on the other server so maybe is a bug that happen only when PHP 5 is installed as ISAPI. This should be fixed because ISAPI run much faster than CGI also CGI use much more of the server CPU resources which can be a problem when you have many websites run on php. ------------------------------------------------------------------------ [2008-10-23 13:46:04] roberto at v-servers dot it Hi, I have the same problem with w3wp.exe crashing after a website run page in php 5.2.6 On this website I have Joomla 1.5 installed, the website work but the web server which is IIS6 on windows 2003 server enterprise report all these errors every time a website with php run. Event Type: Error Event Source: Application Error Event Category: (100) Event ID: 1000 Date: 20/10/2008 Time: 18.01.11 User: N/A Computer: VSS Description: Faulting application w3wp.exe, version 6.0.3790.3959, faulting module w3core.dll, version 6.0.3790.3959, fault address 0x000201b4. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 41 70 70 6c 69 63 61 74 Applicat 0008: 69 6f 6e 20 46 61 69 6c ion Fail 0010: 75 72 65 20 20 77 33 77 ure w3w 0018: 70 2e 65 78 65 20 36 2e p.exe 6. 0020: 30 2e 33 37 39 30 2e 33 0.3790.3 0028: 39 35 39 20 69 6e 20 77 959 in w 0030: 33 63 6f 72 65 2e 64 6c 3core.dl 0038: 6c 20 36 2e 30 2e 33 37 l 6.0.37 0040: 39 30 2e 33 39 35 39 20 90.3959 0048: 61 74 20 6f 66 66 73 65 at offse 0050: 74 20 30 30 30 32 30 31 t 000201 0058: 62 34 b4 Is there any way to fix this or a PHP version that work without problem on IIS6? I am using php 4 on windows 2000 since 4 years without any problems. ------------------------------------------------------------------------ [2008-04-15 12:55:52] pranay dot vanjare at zenithinfotech dot com I HAVE WINDOWS 2003 SERVER RC2 WITH 4G.B RAM XEON SYSTEM. I REGULARLY GET ONE ERROR IN W3WP.EXE FILE (REFERANCE MEMORY AT 0x01e7e8fo MEMORY COULD NOT BE READ) CAN U PLEASE HELP ME IN THAT BECAUSE THIS SERVER IS VERY CRITICAL FOR US. ------------------------------------------------------------------------ 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/37575 -- Edit this bug report at http://bugs.php.net/?id=37575&edit=1
