如何从IIS 7.5中的PHP页面诊断内部服务器错误（HTTP 500） [英] How to diagnose an internal server error (HTTP 500) from a PHP page in IIS 7.5

问题描述

我正在尝试获取在我的本地开发计算机上运行的aMember成员资格管理系统的试用版，该计算机是带有IIS 7.5的Windows 7 64位。我有MySQL 5.5.10和PHP 5.3.6，后者是我使用Windows安装程序包安装的。它似乎很好。

I am trying to get a trial copy of the aMember membership management system running on my local dev machine, which is Windows 7 64-bit with IIS 7.5. I have MySQL 5.5.10 and PHP 5.3.6, the latter which I installed using the Windows installer package. It seems fine.

aMember软件包有一个我运行的tester.php脚本，它给出了一个'OK'结果，尽管它的输出充满了与相关的错误消息函数eregi（）已弃用。然后我运行了setup.php脚本，它似乎运行正常。它花了我一两个屏幕收集，例如MySQL的登录信息，然后表示已完成，并提供了一些aMember管理页面的链接。这些链接都不起作用，单击其中任何一个都会导致内部服务器错误（HTTP 500）：服务器尝试完成请求时遇到意外情况。

The aMember package has a tester.php script which I ran, and it gave an 'OK' result, despite its output being full of error messages related to Function eregi() is deprecated. I then ran the setup.php script, which seemed to run properly. It took me through one or two screens of gathering e.g. login information for MySQL, and then said it was completed and offered me links to some aMember admin pages. None of these links work, and clicking any of them results in an Internal Server error (HTTP 500): An unexpected condition was encountered while the server was attempting to fulfill the request.

如果没有在php页面中放置大量诊断写入，我可以做些什么来进一步诊断此错误？我可以使用的工具是Aptana Studio和Visual Studio，虽然我怀疑后者在这里有用。我已经通过aMember支持记录了这个问题，他很快就询问了我的服务器日志，然后就消失了。

What can I do to further diagnose this error, short of placing lots of diagnostic writes in the php pages themselves? Tools at my disposal are Aptana Studio and Visual Studio, although I doubt the latter is any use here. I have logged the issue with aMember support, who quickly asked for my server logs, and then disappeared.

推荐答案

aMember试用软件使用编码的PHP，需要IonCube进行解码。我安装了这个，但似乎安装失败，因为后续安装解决了这个问题。我最初难倒，因为在安装IonCube后，我运行了aMember测试脚本，告诉我安装了IonCube。 aMember支持回复说：

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:

遗憾的是，测试器脚本无法正确处理动态加载情况。
来自5版本的PHP如果这些库不在php lib文件夹中，则不允许动态加载库。所以你必须将IonCube或Zend安装到服务器php.ini '

我不知道为什么不能在测试脚本中建立警告。

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

这篇关于如何从IIS 7.5中的PHP页面诊断内部服务器错误（HTTP 500）的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！