Bug #16362 Updated: IIS stops serving .php pages after a time period
| From: | develop at dnet dot net | Date: | Tue, 02 Apr 2002 14:11:10 +0000 |
| Subject: | Bug #16362 Updated: IIS stops serving .php pages after a time period | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-3824@lists.php.net to get a copy of this message | ||
ID: 16362
Updated by: develop@dnet.net
Reported By: develop@dnet.net
Status: Open
Bug Type: IIS related
Operating System: Win2k build 2195/XP
PHP Version: 4.1.2
New Comment:
so does this mean that there is nothing I can do, or can this problem
be remedied by changing something in IIS or in the php.ini?
I can't find anything very helpful at microsoft. Which I can't
understand. Why wouldn't they offer help to someone wanting to use a
product that is in direct competition with one of theirs?
Previous Comments:
------------------------------------------------------------------------
[2002-04-01 16:07:46] jtate@php.net
Have to revise my last comment. It did it for me too, using a build
from Thursday's CVS. Event viewer had the following to say.
The HTTP server encountered an unhandled exception while processing the
ISAPI Application '
php4ts!zend_strndup + 0x2B
+ 0x17469F70
'.
For additional information specific to this message please visit the
Microsoft Online Support site located at:
http://www.microsoft.com/contentredirect.asp.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
------------------------------------------------------------------------
[2002-04-01 14:54:55] develop@dnet.net
Executable: c:\php\php4isapi.dll
Extenstion: .php
Verbs: All Verbs
Script Engine: checked
Check that file exists: checked
--DEFAULT WEB SITE PROPERTIES--
Execute Permissions: Scripts only
App Protection: Medium (pooled)
Script source access
Read
Write
Log visits
Index this resourse
--VIRTUAL DIRECTORY PROPERTIES--
Execute Permissions: Scripts only
Application Protection: Low (IIS Process)
Read
Log visits
Index this resource
---------------------------------
it seems to be more stable when I put the virtual directory application
protection on 'Low'
------------------------------------------------------------------------
[2002-04-01 10:44:42] jtate@php.net
How long is a while? I left mine for 4 days and didn't have the same
problem. How do you have the .php extension configured?
------------------------------------------------------------------------
[2002-03-31 12:57:49] develop@dnet.net
IIS will not serve my ASP files correctly either.
sometimes it will serve them correctly. then after hitting refresh it
will give this output:
-2147417842 (0x8001010e)
With source code of:
<html>-2147417842 (0x8001010e)</body></html>
then if I refresh a couple more times it will work again.
refresh too much... 10 or 15 times and then I get this error:
HTTP 403.9 - Access Forbidden: Too many users are connected
Internet Information Services
then, IIS will no longer serve any pages ASP or PHP until I restart the
computer.
here is my complete source for the ASP file.
<HTML>
<HEAD>
<TITLE>Test Write Permission</TITLE>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html;
charset=iso-8859-1">
</HEAD>
<BODY BGCOLOR="#FFFFFF" TEXT="#000000">
<%
Response.Write "ASP"
%>
</BODY>
</HTML>
Still not serving PHP pages consistently either.
------------------------------------------------------------------------
[2002-03-31 01:32:29] develop@dnet.net
my browser seems to be serving php files on one virtual directory now
and not another. even though they are both configured exactly the
same. [browser is now just 'opening page' endlessly.] is there any way
this could be something to do with where I've placed my .dll's? I left
php4isapi.dll in c:/php/sapi and php4ts.dll is in c:/php is this where
they should be?
c:/inetput/wwwroot is set to be the doc_root incedentaly.
does php just have problems on a Win2k box on IIS? should I download
apache? is it more stable that IIS? would a reinstall of PHP help?
thanks again,
-js
------------------------------------------------------------------------
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/16362
--
Edit this bug report at http://bugs.php.net/?id=16362&edit=1