ID: 37483
Comment by: ferrante at aracnet dot com
Reported By: jneill at gamedaytv dot com
Status: Open
Bug Type: IIS related
Operating System: Windows 2003 SP 1
PHP Version: 5.1.4
New Comment:
I am a software developer and would be happy to provide any additional
information or collect any other diagnostics that would help resolve
this issue, including providing access to a machine on which the
problem occurs that has tools such as WinDbg and the IIS "Debug
Diagnostics Tool" installed.
Please let me know how I can help out, and thanks for all your efforts.
Previous Comments:
------------------------------------------------------------------------
[2006-07-12 18:29:06] ferrante at aracnet dot com
These are related issues in the bug database that seem to be describing
the same problem:
Bug #36853 Worker process crashes after application pool recycle
Bug #33373 IIS worker Process continually restarts
Bug #37575 Faulting application w3wp.exe
Bug #35263 Crash during IIS Restart
We have the situation where the access violation appears when the
process is restarted. We followed the advice above to minimize error
messages by putting the PHP app into its own application pool and not
letting the app pool get recycled. However, on iisreset or stop/restart
of the application pool, the access violation is generated, even on the
snapshot code as recent as php5.2-win32-200607120630.
Data Execution Prevention (DEP) was implicated in Bug #36853 and on one
of our servers we were able to mask the error by added an DEP exception
for the w3wp.exe executible. However on another server this did not
work.
Bug #36853 also mentions changing the dynamic extensions load order
around, but in our case it did not seem to help since we are able to
reproduce the problem with PHP installed, no dynamic extensions
enabled, with a simple echo("hello world"); php file. If the app pool
is recycled or iisreset occurs, the php5ts.dll will generate an
exception on unload.
Bug #36853 also mentions that recompiling php from source with a Visual
Studio 2005 can fix the issue also. We have not yet tried that step.
Hopefully this information helps to resolve the issue. Thanks.
------------------------------------------------------------------------
[2006-06-30 06:50:22] danielm at deekora dot tv
I suspect the reason it occurs when no one is using the web site is
because the warning appears when the application pool is recycled.
After disabling automatic pool recycling the warning has not appeared.
to replicate the problem:
> Open a php site that uses the isapi module
> run the following script
======================================
'Recycle all application pools on server strComputer
strComputer = "your server name in here"
Set objWMIService =
GetObject("winmgmts:{authenticationLevel=pktPrivacy}\\" & strComputer &
"\root\microsoftiisv2")
Set colItems = objWMIService.ExecQuery("Select * From
IIsApplicationPool")
For Each objItem in colItems
objItem.Recycle
Next
wscript.echo "Done!"
======================================
> Check iis logs
------------------------------------------------------------------------
[2006-06-28 15:34:51] [EMAIL PROTECTED]
Please don't add any comments to this report if you have nothing to say
except for "me too".
------------------------------------------------------------------------
[2006-06-28 15:13:42] admin at dhosting dot co dot uk
Same issue
Win 2003 SP1
PHP 5.1.4
MySQL 5.0.22
Reproduced on 5 servers, production and test environment, new installs
etc
Only way to resolve is to revert back to 5.1.2
Any news on a fix yet?
------------------------------------------------------------------------
[2006-06-28 11:15:01] gauthier at datas dot com
Same problem here with Windows Server 2003 SP1, IIS 6, .NET 1.1 , PHP
5.1.4 (tested also 5.1.3 & 5.2.0-dev) using ISAPI: start WWW Publishing
Service then load any PHP page (w/ phpinfo() directive for example) then
stop WWW Publishing Service -> the error is thrown. Had to downgrade to
PHP 5.1.2 to make the error go away...
------------------------------------------------------------------------
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/37483
--
Edit this bug report at http://bugs.php.net/?id=37483&edit=1
