IIS 5 & IIS 6
Errors with w3wp.exe and fcgiext.dlll since the installation of FastC...
Last post Mar 09, 2011 03:30 AM by Samual007
May 10, 2010 03:45 PM|LINK
We were not ale to make mosy out of the dumps you provided. Apparently we thought that the dump was collected when php-cgi.exe already crashed/went away. So we do not have a solution here.
It's good that you confirmed that MonitorChangesTo is the root cause of the problem you are seeing as commenting that feature is allowing you to work well without crashes.
Any chance of getting a good dump.
May 10, 2010 03:52 PM|LINK
On a side note with the release of WINCACHE 1.1 Beta2 you no longer need to do the below:
For the WinCache PHP files notifications, I use the wincache_refresh_if_changed() function. In the php.ini file I have also set wincache.chkinterval = 0 and wincache.ttlmax = 0 . Is there a link between the error and WinCache ?
As we have introduced the concept of FIle Change Notification. You can get rid of this and use default values. Details at
http://blogs.iis.net/donraman/archive/2010/04/29/file-change-notification-support-on-wincache-1-1-beta2.aspx. Please change it back to default values or comment out these entries if your file system supports File Change Notification.
May 10, 2010 04:20 PM|LINK
Thanks for your answer Don.
Do you want I try to collect a new dump file after enabling MonitorChangesTo ?
The MonitorChangesTo was a very useful function for me. It's a pity.
Yes, I have read last week the release notes about WinCache 1.1 beta 2. I do not install it for the moment because my server is under production but the new file change notification mechanism is a very good news! After installing the 1.1 final version (any
date estimated ?), I will remove the settings I have added in effect.
Other good news, I have seen that the problem I reported you concerning web garden has been fixed. I will be able to reactive this function on my server. Great!
May 10, 2010 06:27 PM|LINK
Yes, please try creating the dumps again.
I would say Beta2 is worth trying. Try it for few days (it's pretty stable) and will also help us having a more stable final release. Otherwise you may encounter a bug when moving to final released bits. So trying it now for few days is not a bad idea.
We are planning to do the final release by end of June or early July.
Mar 09, 2011 03:30 AM|LINK
We all know that the IIS team has released some new thing to web the FastCGI Extension 1.5 for IIS 6.0 and IIS 5.1. This version is depend on FastCGI Extension 1.0 and we can say that its a advance version of it. it is officially supported by Microsoft,
that is its a Microsoft product. This are the some common errors which occurs many times, so what to do is we have to take the stable release of PHP 5.3 out for a while, the only procefure to install PHP 5.3 on IIS is through a CGI Handler. PHP 5.2 and earlier
allowed us to run PHP using ISAPI, but that option has been deprecated. For those of us intending to move forward, we would have to use CGI from now on. We’ll go over installing the FastCGI handler on IIS 6.0. hope it will help!!!