Wednesday, January 23, 2013 7:06 PM
Running IIS7 as a role on win server 2008
Every once in a while intermittently I get this error. I read the KB article at nausia, checked all permission, there is nothing wrong with permissions on the intepub directories. I know Apache is more stable with PHP but I really prefer IIS for a number of reasons. I checked the PHP configurations and there is nothing wrong there. I know that all of the appropriate PHP FastCGI modules and isapi filters are running
Recently I also installed IIS6 as feature because I needed SMTP installed. Wonder if that is causing issues.
The only script I am running on the server is a PHP script that connects to an IMAP server and retrieves messages and parses the messages for certain information. It has to be done this way, and through PHP and not another email program for a number of reasons. This PHP script auto refreshes every second continuously while the script is running.
Problem is that every so often IIS seams to crash with a 500.0 error for some inexplicable reason. When this happens the functionality of the script ceases and business is lost. If I reload the page manually when this error occurs then the script starts running again with no problems until it crashes again.
Any thoughts on how to prevent this and or cause it to auto refresh the page if an IIS error occurs?
HTTP Error 500.0 - Internal Server Error
C:\php\php-cgi.exe - The FastCGI process exceeded configured activity timeout
</fieldset><fieldset><legend>Detailed Error Information</legend>
Module FastCgiModule Notification ExecuteRequestHandler Handler PHP_via_FastCGI Error Code 0x80070102 Requested URL http://localhost:80/scipt.php?run=yes Physical Path C:\inetpub\wwwroot\script.php Logon Method Anonymous Logon User Anonymous<fieldset><legend>Most likely causes:</legend>
<fieldset><legend>Things you can try:</legend>
- IIS received the request; however, an internal error occurred during the processing of the request. The root cause of this error depends on which module handles the request and what was happening in the worker process when this error occurred.
- IIS was not able to access the web.config file for the Web site or application. This can occur if the NTFS permissions are set incorrectly.
- IIS was not able to process configuration for the Web site or application.
- The authenticated user does not have permission to use this DLL.
- The request is mapped to a managed handler but the .NET Extensibility Feature is not installed.
<fieldset><legend>Links and More Information</legend> This error means that there was a problem while processing the request. The request was received by the Web server, but during processing a fatal error occurred, causing the 500 error.
- Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account.
- Check the event logs to see if any additional information was logged.
- Verify the permissions for the DLL.
- Install the .NET Extensibility feature if the request is mapped to a managed handler.
- Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.
Microsoft Knowledge Base Articles:
Wednesday, January 23, 2013 7:35 PMModerator
You might want to post this question in IIS forum
I do not represent the organisation I work for, all the opinions expressed here are my own.
This posting is provided "AS IS" with no warranties or guarantees and confers no rights.
Whenever you see a helpful reply, click on Vote As Helpful & click on Mark As Answer if a post answers your question.
- Marked As Answer by Cheers ZHANGMicrosoft Contingent Staff, Moderator Wednesday, January 30, 2013 7:15 AM