ID: 39163
Updated by: [EMAIL PROTECTED]
Reported By: tony dot stone at gmail dot com
-Status: Open
+Status: Feedback
Bug Type: Documentation problem
Operating System: Windows Vista RC 1 Build 5600
PHP Version: 5.2.3
New Comment:
What exactly and where should be documented?
Previous Comments:
------------------------------------------------------------------------
[2007-07-22 23:20:06] [EMAIL PROTECTED]
On second thought, this needs better documenting. Reclassified as such.
------------------------------------------------------------------------
[2007-07-22 23:19:12] [EMAIL PROTECTED]
See above comments how to fix it.
------------------------------------------------------------------------
[2007-05-09 15:05:44] FreakTrap at gmail dot com
sneakers05's modification of the Application Pool's 32-bit setting also
corrected the problem I was having with the php5isapi.dll.
For those of us getting the 'Calling LoadLibraryEx on ISAPI filter
"C:\PHP\php5isapi.dll" failed' error after an attempted manual install:
1) *Start with a fresh IIS installation with both ISAPI filters and
extensions enabled.
2) Under the main settings [at the very top of your IIS Manager's
hierarchy view, above Application Pools], add the following in this
order:
2.1) an ISAPI Filter for php5isapi.dll
2.2) a ISAPI and CGI Restriction entry for php5isapi.dll
2.3) a Handler Mapping for php5isapi.dll
3) Go to the application Pools section.
4) Right-click on Default Application Pool and select Advanced
Settings.
5) Set the second option [Enable 32-Bit...] to True.
Now everything should work...
* Also, it is important that your 'Default Website' not have any unique
settings from the top-level configurations. This was causing my ISS to
exhibit some pretty strange behavior, which is why I recommend that you
first delete your default website and create a new one.
------------------------------------------------------------------------
[2007-05-04 10:02:55] gruddzr at yahoo dot com
i also have the same problem, using vista premium here
------------------------------------------------------------------------
[2007-04-13 23:14:50] sneakers05 at optusnet dot com dot au
I had similar probs running php4isapi.dll with IIS7 on Vista x64
Ultimate. Moving to php5 isn't an option for me because I'm developing
for a particular machine running php4.
I can't get the isapi version of php running, but after a bit (lot!) of
messing around have got the php.exe version working sweet. :)
Here's what I did:
1. Remove all ISAPI filters for PHP.
2. Ensure you have a handler mapping for PHP as follows:
*.php
c:\php\php.exe (or whatever path you are using)
3. Under Application Pools in IIS Manager, right clicked DefaultAppPool
and went to Advanced Settings. Ensure "Enable 32-bit applications" is
set to True. I also set Process Orphaning:Enabled to True, even though I
have *no* idea what it is for!
4. Ensured php.ini was in my c:\windows folder and the
cgi.force_redirect is set to 0 and uncommented.
I also did the following which may or may not be required:
1. Right clicked the PHP folder and selected Properties, Security.
2. Clicked on Advanced, Edit, Add.. and for the object name to select,
entered: IUSR.
3. Clicked OK and gave IUSR full control to the folder.
4. Repeated steps 2 and 3 but for IIS_IUSRS.
5. Applied the changes and clicked on OK to exit the PHP folder
properties window.
I also did the following which probably isn't needed:
1. Copied php4ts.dll into my c:\windows\system32 folder
2. Stood on one foot while chanting to the rain gods and focussing my
mental energy on my "power animal" - the llama. :)
Hope this helps others, even if it doesn't resolve the isapi side of
things!
-Damo
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/39163
--
Edit this bug report at http://bugs.php.net/?id=39163&edit=1
