Oh, one thing I forgot to mention: The technology test page for CWP tests normal. So I know the PHP install is working.
Have you tried accessing the page using a browser on the server? There's a switch in IIS (I forget what it's called) that will display more info about the error than an external user will see if you access the page locally. This has helped me a few times when I've been stumped by the 500 error.
Hey, Mark. Thanks for the tip. Believe it or not, it works on the server. But I get the 500 from a client. How weird is that?
1 of 1 people found this helpful
Now that's just strange. Can't say I've seen that before.
This might be useful:
The part about editing web.config might do the trick for you.
Oops. Looks like I missed an important detail. I didn't realize I was looking at (url).htm on the server, but (url).php on the client. Turns out HTML pages work fine on both, and PHP pages break on both. So it's not a client / server thing; it's a PHP is broke thing.
I looked in the logs, and there's no apparent difference between the PHP pages that don't work and the FileMaker test page.
This ... is ... weird.
Okay, we got it figured out. The ISAPI handler was set wrong down inside the web site (on the specific folders). Set to php.dll; should have been php-cgi.exe. Combine that with the need to turn off the CGI forced redirect, and we're in business.
OMG, Mike, I went thru this agony you are suffering now...
My client ended up buying a MacPro for me....
I actually got that bit working... and it was permissions...something to do with the anonymous user belonging to the IiS group.... Sorry I can't remember more but it was so traumatic. (We had further permissions problems using a PHP-triggered import into a container field.)
Every time I have to do anything in IiS it is a joke... Such a sucky piece of web server software!
Sent from my iPad
11th Hour Group Pty Ltd
Amen to that!