IIS 7.5, 8.0, 8.5 HTTP Error 403.14 - Forbidden after Clean Windows Install
I am running an Asp.Net site under IIS 7.5 - win 7, IIS 8.5 - win 8.1. I have 2 development machines that run it fine.
-
Steps to Recreate Environment After a fresh install of Win 7 on another machine. All updates installed
Added IIS function with
- .Net extensebility
- Asp
- CGI
- ISAPI extensions
- ISAPI Filters
Registered .Net framework 4.0 with IIS (aspnet_regiis -i / aspnet_regiis -ir)
Added correct application pool to website.
Set the path to the bin folder of the project.
in the web.config set:
<system.webServer>
<modules runAllManagedModulesForAllRequests="true"/>
</system.webServer>
IIS / IIS_USRS entered read-write permissions on a specific folder
* Note: I don't need directory browsing support
- Problem
- All new OS installations do not have any win version (7, 8, 8.1 or 10 Preview). I got the same error **** HTTP Error 403.14 - Forbidden The web server is configured to not display the contents of this directory. ****
If anyone can help because I am running out of places to find the problem.
* Note. The same setup works on 3 win 7 development machines and server 2008. If I propagate a post, it works fine. (Containing pages .aspx)
thank
source to share
As I said in my comment below by the OP, I've tried everything on the list of common suspects. Having literally lost days of my life struggling with this problem, this is what fixed it for me: -
For some reason it is best to know the malevolent forces of dotNet, publishing my web application configuration Precompile the time of publication (found in File Publish Settings in the Settings in the publication dialog in VS 2012) made some of the MVC application using the wrong handler. It was like IIS had "forgotten" that they were MVC applications.
Small text file:
PrecompiledApp.config
was created in the root directory of the faulty application.
Deleting this text file and then publishing it without configuring precompilation resulted in the failing applications returning to normal.
I have no idea why this option would have such a detrimental effect, but that seems to be the reason.
(I've also set all MVC dependency references to "copy locally", but that's on the "common suspect" list to do.)
Like most things about dotNet, puzzling problems like these require days of one foot bumping into a wall, randomly changing settings until you change the situation. There is usually no logical reason or documented example of the error in question and you are simply left with voodoo, rumors and trawlers like SO for an answer.
Open source Gimme any day ...
source to share
On Windows 8.1 IIS 8.5, I got the same error.
I found google and found this video: https://www.youtube.com/watch?v=OmQlO0daduE&feature=youtube_gdata
My Default.aspx was Defeult.aspx with a-> e typeo - fixed it. And now it works.
Tho, I figured this is still a strange error. Mabi should have been something like "Couldn't find any of the default start pages defined in the" Default Document "and how to change the link"
source to share