I found this also – no mapping for a .php etension. In what way does that qualify as an instal?

Salman’s solution here fixed it for me – so thanks!

I had previously installed PHP (isapi) sucessfully on my XP box by hand. It was a mission but I’d managed it. I had also installed MySQL and WordPress. Agins, two more missions,with dodgy instals and undocumnted features, but it worked.

I ran across this MS WPI thing and it worked a treat on a W2008 box so I tried it on my XP box to instal a new WordPress instance. I figured I should do it the Microsoft Way, not fight the oer etc.

It didn’t take so I figured there’s a mismatch and attempted to clean off all the previous versions. Subsequent execution of the WPI, once I had really convinced it that I had removed PHP from my box, left the instal without this mapping. I guess WPI works on a clean instal but anything left behind confuses it totally.

In IIS Management Console:
1. Open properties of Default Web Site.
2. Select the Home Directory and click Configuration button.
3. Click Add on the Mappings tab, browse for C:\WINDOWS\system32\inetsrv\fcgiext.dll, set Extension to “.php”, set Limit to “GET,HEAD,POST”, check Script engine
4. Click OK
5) Restart IIS

Additionally, on IIS6 and later, you need to “enable” this CGI extension.

To get PHP working you may need to create a mapping from .php extension to fcgiext.dll

msexec /i php-5.2.10-nts-Win32-VC6-x86.msi /l* C:\install.log

After that, open the C:\install.log file and look for strings “error” and “fail”.

Best regards

What’s the actual error behavior that you see? Do you see any error messages?