How to diagnose an internal server error (HTTP 500) from a PHP page in IIS 7.5

纵然是瞬间 提交于 2019-12-06 06:37:23

My first port of call here would be to enable Failed Request Tracing:

Troubleshooting Failed Requests Using Tracing in IIS 7
Troubleshoot with Failed Request Tracing

I am also suspicious about your PHP install. As a rule of thumb never use the installers. They never seem to do the right thing.

I would tear down your PHP install and start from scratch using these steps:

Using FastCGI to Host PHP Applications on IIS 7

FastCGI + the Non-threadsafe build of PHP (5.2 or 5.3) is the definitive way to install and configure PHP on IIS7.

The aMember trial software uses encoded PHP which requires IonCube to decode. I had installed this, but it seems the installation had failed, as a subsequent installation remedied the problem. I was initially stumped because after installing IonCube, I ran the aMember test script which told me IonCube was installed. aMember support responded that:

unfortunately tester script is not handle situation with dynamic loading correctly. PHP from 5 version do not allow to load libraries dynamically if these libraries are not in php lib folder. So you have to install IonCube or Zend into server php.ini'

I don't know why that can't build a warning into the test script.

标签
易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!