• Install Windows Server 2012 R2
• Mantis Bug Tracker

Recently we had to work on a Windows server 2008 (web edition) machine with IIS 7.0 and we ran into the strangest of errors. The server stops running the script with this message:Server Error500 – Internal server error.There is a problem with the resource you are looking for, and it cannot be displayed.Cause:This error happens on the default configuration of windows server 2008. The server logs do not say a lot except for the fact that the php file is causing an error. This happens for the following reasons on the server:. PHP Fatal error (Something that you did or didn’t do caused the server to run into a fatal error). PHP errorreporting is on and there are some errors (Anything from a NOTICE or WARNING can cause this)How to rectify:Obviously the best way to resolve the error is find out what is wrong with the PHP code. But how do you do this if the server won’t show you what the error is?

We have a VPS Windows Server 2008, R2 site. I can access the MantisBT web page and have even set up a generic user and project without. Installing PHP MySQL and PHPMyAdmin on Windows Server 2008 R2 - Duration: 8:46. Randystech 154,841 views. Mantis Bug Tracker Installation (MS SQL Server and IIS) Configure IIS and PHP to work together This assumes that IIS is already installed on the web server. First, create a new folder on the web server to store the PHP web files. Click Start - Settings - Control Panel. Double-click Administrative Tools.

One of the best ways to find what is wrong with your PHP script is to try to login to the machine via RDP. This works only if you have remote desktop access. Once in RDP try to go to the same URL but using the server’s Internet explorer.

Install Windows Server 2012 R2

Accessing the server locally will avoid the 500 Internal Server Error and show you what is wrong with the PHP file as on a development environment. The server just shows you the PHP error messages and the rest of your script output is not shown.Change IIS 7.0 SettingAlternatively to the above, you can always change the configuration using the Configuration Editor of IIS 7.0. You will find this under the Section system.webServer/httpErrors. You have to change errorMode to Detailed from the usual DetailedLocalOnly and then click on Apply.This is a good security measure as it will not accidentally show your PHP errors to the users of your system.

Mantis Bug Tracker

– Note –I had the 500 internal error on a form post.On SHARED hosting i.e. With Fasthosts, you CANNOT change the access to the folders as this would inherantly give you access to the other folders.I had a problem with this and the only solution was to switch to Linux hosting, Fasthosts were telling me the it was a ‘script error’ however the script worked fine on one of my other servers (which was linux) after a couple of arguements with so called support in the philipeans they admitted that the php access permission on shared hosting cause problems! No Sh.t.Switched to Linux – Problems Solved. When I built a windows 2008 web server R2, I simply loaded PHP via windows platform installer. It will configure the server to use Fast CGI and it works seamlessly. You can also set up IIS on win2008 to use trace and identify errors. The Event logs are your friend, so ensure you look through those.

I have been playing with IIS and PHP MYSQL for years. If a 500 error appears all of a sudden, its probably due to recent changes or some module not started. If you make changes, remember to stop the web site and restart it.

Microsoft and Technet have IIS issue forums and there are MANY knowledgable people there, just presnt facts and hope they have an answer!Gary K.