*Updated April 2016 The customErrors attribute is used when the .net code is throwing an exception (404, 403, 500 etc) and the httpErrors attribute is used when IIS itself is throwing an exception. /myfakeextensionslessurl –> httpErrors 404 /myfakeaspsx.aspx –> customErrors 404 /myfakeimage.jpg –> httpErrors 404 /throw500.apx –> customErrors 500 /throw500 –> customErrors 500 There are … Read more
I have come to the same problem and fixed the same way as Alex K. So if “Send Errors To Browser” is not working set also this: Error Pages -> 500 -> Edit Feature Settings -> “Detailed Errors” Also note that if the content of the error page sent back is quite short and you’re … Read more
ASP.NET 4 was not registered in IIS. Had to run the following command in the command line/run 32bit (x86) Windows %windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -ir 64bit (x64) Windows %windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -ir Note from David Murdoch’s comment: That the .net version has changed since this Answer was posted. Check which version of the framework is in the %windir%\Microsoft.NET\Framework64 directory and … Read more
The ApplicationPoolIdentity is assigned membership of the Users group as well as the IIS_IUSRS group. On first glance this may look somewhat worrying, however the Users group has somewhat limited NTFS rights. For example, if you try and create a folder in the C:\Windows folder then you’ll find that you can’t. The ApplicationPoolIdentity still needs … Read more
The 2nd option is the one you want. In your web.config, make sure these keys exist: <configuration> <system.webServer> <validation validateIntegratedModeConfiguration=”false”/> </system.webServer> </configuration>