Partner and Community Forums
Windows Cache Extension for PHP
FastCGI Handler error after install
Last post Jan 10, 2010 03:39 AM by don.raman
Jan 08, 2010 07:55 PM|LINK
We are sorry for the trouble. PHP and PHP applications install using WebPI was affected because
http://windows.php.net went down for maintenance. Both PHP and wincache were getting downloaded from
http://windows.php.net. We just updated WebPI to pick PHP and wincache installers from sourceforge.net. You should be able to install PHP applications using WebPI now.
Jan 09, 2010 01:33 AM|LINK
I hope that you are able to install PHP along with WINCACHE and JOOMLA after the broken link bug was fixed in WPI. Please do let us know in case you are still having problems. We are here to help you out. Regarding my role in Microsoft, I am a Software Design
Engineer in Test responsible for IIS FastCGI/PHP on IIS/WINCACHE. I do partner with WPI team for all of the above mentioned product as well as PHP applications and MySQL.
Let me now explain some of the technical reason behind your frustration apart form the broken link problem. PHP MSI is dependent on a script named fcgiext.js (if the user asks the MSI to configure IIS FastCGI which is a typical scenario). PHP MSI uses this
script on IIS5.1/6.0 to add index.php to the default document section as well as create script mapping for handling .php extension. On IIS7.0+ the same thing is achieved by a command named appcmd.exe. In order to make PHP work properly IIS FastCGI should be
configured properly. IIS FastCGI comes as a seperate download for IIS5.1/6.0 and is builtin within OS for IIS7.0 onwards. But IIS FastCGI is not configures as part of default OS installation. So now you know PHP MSI may fail if these are not configured properly.
Also, all the above steps (adding index.php in default document and configuring script mapping for .php extension) is carried as part of custom action in PHP MSI. I believe there is no good way for failing the MSI if any of the custom action fails. So PHP
MSI is unable to point to you the failure. However these failures will be definitely logged in the MSI log. You can use MSIEXEC to install PHP MSI and pass a parameter where log files can be created From an elevated command prompt you can type 'msiexec.exe
/i <path to MSI> /l <path to log file>. Type 'msiexec.exe /?' for details). You can later visualize the log file for errors. I understand not a great way but at least you will know what went bad rather than being in the dark.
There has been genuine bugs in the PHP MSI where script mapping for .php extension is not done/missed or not done properly. I have filed PHP bug for this at
http://bugs.php.net/bug.php?id=50527. However these bugs are specific to IIS5.1/6.0 and hence for Windows7 PHP MSI should not fail for the reasons mentioned above. Please do let me know in case it fails to
create script mapping on Windows7.
You can also troubleshoot your PHP installation. I have written a blog which gives you step by step approach to do this. The blog can be found at
Hope the explaination helps you in understanding what's going behind to some extent and lessens the pain.
Jan 09, 2010 01:37 AM|LINK
I can understand the pain here. And believe me we are trying to fix these things. It would be good if you can let me know any other problem in installing PHP/WINCACHE/FastCGI/MySQL/PHP applications (apart from the one mentioned above in my post) and I will
bring it to everyone's attention in our feature team meeting.
Jan 09, 2010 03:48 AM|LINK
What I end up doing was disable Win 7 Pro firewall, disabled the always pain in the neck pop-ups of sure you want to do this task windows :-), then install PHP 18.104.22.168, Mysql, and then used the link from WPI to install the Joomla. I'll have to look and see
if the link to the Wincache is working, as I have not been able to locate the file else where. Even without the Wincache, all three of my web site are up and running. I was a slight bump in the road when trying to install the second and third joomla from the
WPI. Due to having to seach all the directories for the IIS Manager Control panel .exe, installing it to function with Win 7. I think that service from the old control panel should have been left in the new version of Windows.
One thing that I had to work around tonight is the use of JTT fuctions and the use of Apache, and Apache TomCat. Once I added Apache and Tomcat to the mix, Win 7, IIS 7 is just kicking fast. Don't know what is making the difference but FastCgi, PHP, Mysql,
MyPHPadmin, all are running Great!!.. Thanks for getting back to me as fast as you did. Now I'm wishing for luck on using ioncube with IIS 7 and SilverLight. :-)
Ok Thanks again..
Jan 10, 2010 03:39 AM|LINK
I am glad to know that you were able to install Joomla from Microsoft Web platform installer. WPI makes PHP application installation really easy and I hope you find that too.
Since you installed Joomla from WPI, WINCACHE should have got added as a dependency and installed too. I think this is the reason you are seeing substantial increase in speed. Please check your extension folder of PHP and see if there is a DLL named php_wincache.dll.
If it is there and you have a line:
in your PHP.INI file, you are running WINCACHE. The other useful files can be found at "C:\Program Files\IIS\Windows Cache for PHP". You will be interested particularly in the file named WINCACHE.PHP which shows you nice statistics with regard to caching.
You can copy this file somewhere under your site's DOCUMENT_ROOT, change the default password and access it in the browser. This will show you live cache statistics.