PHP handler mapping on IIS 7.5 1

[Geates]

I'm having an issue getting PHP installed on IIS7.5. I receive the following error.

--------------------------
Error Summary

HTTP Error 404.4 - Not Found
The resource you are looking for does not have a handler associated with it. Detailed Error Information

Module IIS Web Core

Notification: MapRequestHandler
Handler: Not yet determined
Error Code: 0x80070002

Requested URL:

http://localhost:80/index.php

Physical Path: G:\Development\Websites\index.php
Logon Method: Anonymous
Logon User: Anonymous

Most likely causes:
•The file extension for the requested URL does not have a handler configured to process the request on the Web server.
---------------------------

This error is cryptic to me because I already have a Handler Mapping of *.php to the IsapiModule. I have tried configuring the mapping to an optional executable of c:\php\php5isapi.dll with no luck.

Is there an additional mapping I've left out? Has anyone had troubles/success with installing PHP on IIS7.5?

-Geates

 

[mrdenny]

Are you running x86 or x64 OS?

Denny
MVP
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / SQL 2005 BI / SQL 2008 DBA / SQL 2008 DBD / SQL 2008 BI / MWSS 3.0: Configuration / MOSS 2007: Configuration)
MCITP (SQL 2005 DBA / SQL 2008 DBA / SQL 2005 DBD / SQL 2008 DBD / SQL 2005 BI / SQL 2008 BI)

My Blog

 

[Geates]

Windows 7x64 RC1 build 7100.

-Geates

 

[mrdenny]

Did you download the 64bit build of PHP, or the 32bit?

Is your application pool running in 64bit mode or 32?

Denny
MVP
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / SQL 2005 BI / SQL 2008 DBA / SQL 2008 DBD / SQL 2008 BI / MWSS 3.0: Configuration / MOSS 2007: Configuration)
MCITP (SQL 2005 DBA / SQL 2008 DBA / SQL 2005 DBD / SQL 2008 DBD / SQL 2005 BI / SQL 2008 BI)

My Blog

 

[Geates]

I will readdress my issue with this consideration in mind. I completely overlooked system architecture as a potentional issue. The last time I had to worry about that was in 1998 trying to get a qbasic program to run on my new 32-bit machine.

-Geates

 

[Geates]

I changed the advance properties of my Application Pool so "Enable32bitAppOnWin64" = "true". A few other mild configurations and my localhost began to run. Thanks for pointing out system architecture.

This begs the question. Is PHP x64 stable enough for web development?

-Geates

 

[mrdenny]

I'm running 3 wordpress blogs on it on 64bit machines without issue.

(All three blogs are run on 2 web servers with a load balancer in front.)

Denny
MVP
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / SQL 2005 BI / SQL 2008 DBA / SQL 2008 DBD / SQL 2008 BI / MWSS 3.0: Configuration / MOSS 2007: Configuration)
MCITP (SQL 2005 DBA / SQL 2008 DBA / SQL 2005 DBD / SQL 2008 DBD / SQL 2005 BI / SQL 2008 BI)

My Blog

 

[Geates]

Even though I finally was able to configure IIS to run php, I am getting a dumbfounding error I didn't observe before.

My default document list contains 'index.php' and 'index.html'

Going to

http://localhost/

generates a 404.4
Going to

http://localhost/index.php

works.

Kind of makes a default document list pointless. What could be wrong?

-Geates

 

[Geates]

it's worse. IIS doesn't seems to recognize any *.php file.

 

[mrdenny]

Sounds like your handler isn't setup correctly.

You are pointing the handler to php5isapi.dll right?

You've got the application pool set for the correct setup (x64 vs x86)?

Denny
MVP
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / SQL 2005 BI / SQL 2008 DBA / SQL 2008 DBD / SQL 2008 BI / MWSS 3.0: Configuration / MOSS 2007: Configuration)
MCITP (SQL 2005 DBA / SQL 2008 DBA / SQL 2005 DBD / SQL 2008 DBD / SQL 2005 BI / SQL 2008 BI)

My Blog

 

[Geates]

I do suspect that may be the issue. I'm running IIS 7.5 in 32-bit mode using 32-bit PHP on a Win7x64 system. I have a handler mapping for *.php. The handler mapping is the IsapiModule and the executable is php5isapi.dll. However, I noticed that the IsapiModule in the managed modules list is linking to %windir%\system32\inetsrv\isapi.dll. It's confusing when two thing are both called IsapiModule.

To add, I also have the standard handlers that get configured when adding the isapi component to IIS (ASPClassic, ISAPI-dll, CGI-exe, SecurityCertificate)

-Geates

 

[Geates]

Over the course of last evening, my IIS issues subsided. It now works expectedly.

-Geates