Please Note This does NOT work on IIS 7. 5 or R2. You will get a LOCK VIOLATION due to changes in security in the newer version. Please use the URL Rewrite 2. 0 method. Learn, download, and discuss IIS7 and more on the official Microsoft IIS site for the IIS. NET development community. This article describes how to configure the FastCGI module and PHP to host PHP applications on IIS 7 and above. IMPORTANT This article provides instruction. Troubleshoot IIS7 errors like a pro. So you just moved your application to an IIS7 server, and now you are getting an error when you make a request to it.   This seems to be a popular theme on IIS. NET forums these days, and after answering a hundred or so of these posts, I figured I should do something to help people track down and fix their issues with a little less frustration.   Update We recently launched a service that significantly helps you understand, troubleshoot, and improve IIS and ASP. NET web applications. If you regularly troubleshoot IIS errors, manage Windows Servers, or tune ASP. NET performance, definitely check out the demo at www. Server software, and web servers specifically, are very complex and highly configurable systems that support multi tier applications using a variety of technologies and subsystems, and endure further complexity due to security, performance, and reliability demands, so its a wonder it all works as well as it does in the end.   IIS7 strives to improve the experience of diagnosing and solving problems when they do occur, so knowing how to use the new IIS7 diagnostics features can come a long way in helping you become a pro at troubleshooting server problems. The article describes how to redirect HTTP to HTTPS using URL Redirect 2. 0 for IIS 7. Very simple easy to follow stepbystep manual. First things first whats the problem I often find myself asking this question on the forums when someone posts something like Help, I moved to IIS7 and now my application doesnt work.   Huh, what doesnt work When your site stops working, the first thing you need to do is determine what the error actually is before we can move any further.   IIS7 has much better error messages that will often tell you exactly what the problem is, and help you fix it. Unfortunately, sometimes getting to this error is the main challenge.   Lets look at a few things you may need to do to get there 1 Disable IE Friendly HTTP error messagesIE will by default replace the actual error messages coming from the server with a friendly error message, which hides the error contents we need to see.   For example, for a 4. Not Found error, you may instead see the following To disable this and see the real error coming from the server, you need to go to Tools Internet Options, choose the Advanced tab, and clear the Show friendly HTTP error messages checkbox.   Then, close the browser, open it again, and re request the page. Now, suppose you are still seeing the generic cannot display the webpage or page not found error. This is typically caused by IE failing to connect to your website, so there is no server error message to look at here.   I have a detailed guide to troubleshooting this condition here Where did my IIS7 server go Troubleshooting server not found errors. An aside If you dont want to mess with IE for troubleshooting especially if you suspect you are getting cached pages, due to IEs super aggressive caching, the best thing to do is break out a trusty simple http tool of choice and make the request with it.   I recommend WFETCH, which is included in the IIS6 Resource Kit tools you can install on XPWindows 2. VistaLHS box. 2 Enable IIS7 detailed errors. IIS7 introduces a new custom errors feature, which by default hides the error responses issued by the server to remote clients, replacing them with a basic error message.   This is critical for security of your site, as errors frequently contain sensitive information that you dont want others to see, but makes getting to the bottom of the problem harder since you cannot see those very error details. So, if you are requesting your site from another machine, you may still get a basic error that looks like this You have two options here 1 Make the request locally from the server machine.   By default, you will get the detailed error. Enable detailed errors for remote clients. First, if your error is an ASP. NET exception you can tell if it says Runtime Error and has the framework version, please be aware that ASP. NET overrides the IIS custom error mechanism with its own implementation of custom errors, so you should turn the ASP. NET custom errors off to see detailed ASP. NET exceptions.   You DO NOT have to configure IIS7 custom errors for ASP. NET exceptions it would be silly to have to do it in two places.   To turn off ASP. NET custom errors, place the following in your web. Errors modeOff lt system. If the error is not an ASP. NET error, turning off IIS7 custom errors will allow error responses from your application to be sent to remote clients without being censored by the IIS7s custom errors module. You can do this from the IIS7 Admin tool by running Start Run inetmgr. Error Pages icon, clicking Edit Feature Settings action, and then selecting Detailed Errors. You can alternatively do this from an elevated command line prompt Run as Administrator windirsystem. Default Web Siteyourapp section http. Errors error. Mode Detailed. Where Default Web Site should be replaced with your sites name if different, and yourapp with the virtual path youd like to enable detailed errors for. NOTE When you are done debugging, please return the settings back to custom errors for remote requests, or the security of your website may be compromised.   Here is how to do it with App. Cmd windirsystem. Default Web Siteyourapp section http. Errors error. Mode Detailed. Local. Only Now, you should be getting detailed errors back for example, the error I was getting before now looks like this this is the Vista error page Longhorn Server and Vista SP1 error pages will look much nicer, see this for an example Notice that this error contains quite a bit of useful information 1 The heading contains the substatus code, 4. IIS specific code that further describes the problem.   The majority of common errors has a unique lt statuscode. lt substatuscode combination that you can easily google for additional information. The page indicates what module IIS Web Core, and in what notification Map. Request. Handler an error occurred.   This information is critical whenever you are debugging server problems, especially on the IIS7 world when most of them occur in one of the modules that take part in the processing of the request. The page shows you some useful request information, such as the requested url and the physical path to which it resolved.   Most 4. The most likely causes and what you can try sections offer the most likely explanation for the error and what you can do about it.   They are dead on for the majority of common IIS7 errors. NOTE When you are coming to the forums with an error, we expect you to have gotten this far and that you will provide the detailed error to help us with your problem.   For more information about the custom errors support in IIS7, check out http www. IIS7Managing IIS7Diagnostics in IIS7Deciphering Error MessagesHow to Use HTTP Detailed Errors in IIS7. Detour the 5. 03 Service Unavailable error. Sometimes, you will get an error that looks like this This error most likely either indicates a critical misconfiguration of the server that is causing IIS to fail to start a worker processprocess your request, or a system overload condition that is causing requests to be rejected early, so no further error information will be available in the response.   If you are getting this error, please follow my detailed guide Where did my IIS7 server go Troubleshooting service unavailable errors. Hosting ASP. NET in IIS7 gives Access is denied This is what happened to me Get Post is ok. Working well. When I try to use Options verb, the server return error like that. Then, beware with url. Scan. I add OPTIONS verb to urlscan configuration. To check if urlscan is installed or not, open your iis manager, and open ISAPI FILTERS url scan should appear at the list.