| Bug #37575 | Faulting application w3wp.exe | ||||
|---|---|---|---|---|---|
| Submitted: | 24 May 2006 8:03am UTC | Modified: | 18 Oct 2009 1:00am UTC | ||
| From: | richardvernooij at yahoo dot com | Assigned to: | pajoye | ||
| Status: | No Feedback | Category: | IIS related | ||
| Version: | 5.2 | OS: | Windows 2003 server | ||
| Votes: | 50 | Avg. Score: | 4.7 ± 0.8 | Reproduced: | 45 of 46 (97.8%) |
| Same Version: | 22 (48.9%) | Same OS: | 42 (93.3%) | ||
[24 May 2006 8:03am UTC] richardvernooij at yahoo dot com
[24 May 2006 8:13am UTC] derick@php.net
Not enough information was provided for us to be able to handle this bug. Please re-read the instructions at http://bugs.php.net/how-to-report.php If you can provide more information, feel free to add it to this bug and change the status back to "Open". Thank you for your interest in PHP.
[24 May 2006 11:56am UTC] richardvernooij at yahoo dot com
ok i tested the following versions: 5.0.5 5.1.3 5.1.4 5.2-dev all have the same problem I tried this on 2 different servers running win2003 /IIS6 ASP.NET 1+2 Mysql 5.0 open ssl etc.. now i installed php4.4.2 and the problem does not appear anymore. now i wonder, is it save still to use version 4 or will i get problems in future?
[24 May 2006 5:34pm UTC] tony2001@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.
[1 Jun 2006 1:00am UTC] 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".
[21 Jun 2006 4:38pm UTC] chihwen dot yang at gmail dot com
I have the same problem, but my DBMS is SQL Server 2000 (SP4).
[12 Jul 2006 9:45am UTC] ferrante at aracnet dot com
I believe this is related to Bug #36853 Worker process crashes after application pool recycle. There are some detailed posts at the bottom of that bug suggesting changing the extensions load order in the php.ini file or disabling DEP for the w3wp.exe process.
[26 Jul 2006 7:57pm UTC] jeep85 at gmail dot com
This error started to appear for me after I upgraded to PHP 5.1.4 Once I downgraded back to PHP 5.1.1 the errors went away. Wasn't sure if that would help isolate the problem. I'm running IIS6 on W2K3 SP1.
[6 Apr 2007 6:02am UTC] chrisjx at gmail dot com
Having the very similar problems. Now have Server 2003 sp2 installed still a problem. The variation I'm having is that I get the error perhaps 6 times whenever I re-boot. Then all is well and everything seems to work fine. I went into PHP.INI and commented out the only extension I had, php_mysql.dll, rebooted and the problem no longer occurs. However w/o this extension installed all is kaput... I know, I see the note not to say "this is how I solved it" or "this might help you" and I suppose you might delete this, but I had to try. I've had this problem since I installed 5.1.4 and I doubt it is "bogus". Event Log: Reporting queued error: faulting application w3wp.exe, version 6.0.3790.3959, faulting module unknown, version 0.0.0.0, fault address 0x01d45c80.
[28 Dec 2007 9:25pm UTC] masssheltie at hotmail dot com
Found this posting buried on a development web site. David Wang et al possibly figured out the reason for the problem. >This is a bug in the PHP ISAPI DLL during DLL unload. It is trying to > double-free a piece of memory. When you recycle the Application Pool, > it causes the w3wp.exe to shutdown and unload all ISAPI DLLs, hence > triggering the PHP bug. > > The crash happen regardless of the IIS Application Pool identity. > > This should just be reported to PHP as a bug. You can recreate the problem by accessing any PHP script, and then recycling the applications pool associated with the web page in IIS. The recycling will cause the error, and will log same in the Event Viewer. I've not heard any formal plans to cope with this as of yet.
[15 Apr 2008 12:55pm UTC] 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.
[23 Oct 2008 1:46pm UTC] 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.
[23 Oct 2008 2:11pm UTC] 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.
[23 Oct 2008 3:52pm UTC] pajoye@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).
[31 Oct 2008 1:00am UTC] 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".
[10 Oct 2009 12:38pm UTC] nishant dot nigam at hkdigitalonline dot com
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..
[10 Oct 2009 1:41pm UTC] pajoye@php.net
Please use the NTS build of PHP 5.2.11 and try again with FastCGI and not the ISAPI sapi. The ISAPI is deprecated and not maintained anymore, FastCGI is the recommended way to use PHP with IIS (by php.net and MS).
[18 Oct 2009 1:00am UTC] 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".
