Reputation: 3409
I have a ASP.NET MVC application which was running on Win 8.1 and IIS Express 7 but Microsoft changed this by force with updates and now I have Windows 10 and IIS 10.
Application stopped working today (day 1 month 4 2017).
I end up with
Service Unavailable
HTTP Error 503. The service is unavailable.
or
HTTP Error 403.14 - Forbidden The Web server is configured to not list the contents of this directory.
Privileges
Application pool for this app is under different account. The user has privileges to different folders. Logs are enabled.
Problem 1
I see nothing (significant) in any logs. It seems logs are not working. I am not sure, or I just can not see them.
Problem 2
After I starts application pool it stops in a few seconds.
In Event log I have only this:
Event log
Error: Application pool 'MyApp' is being automatically disabled due to a series of failures in the process(es) serving that application pool. -
Warning: A listener channel for protocol 'http' in worker process '8924' serving application pool 'MyApp' reported a listener channel failure. The data field contains the error number. 5139 -
Note
When I run this app on different computer from Visual Studio it is working.
Question
Upvotes: 3
Views: 8255
Reputation: 9
We may get http error 403.14 - forbidden if ASP.NET is disabled in Application Development Features section of Internet Information Services in Turn Windows Features on or off in Control Panel\Programs\Programs and Features
Upvotes: 0
Reputation: 11
Found the problem to my last post - I took out the added system statement above (only made things worse) then I enabled Directory Browsing and got web exactly that, web browsing of the folder for this site. I then attempted to open the web.config file from the browser and got:
HTTP Error 404.3 - Not Found The page you are requesting cannot be served because of the extension configuration. If the page is a script, add a handler. If the file should be downloaded, add a MIME map.
In my html code I then took out the statement that asked for an image since it was a MIME issue. Then got the webpage properly without the image of course.
That took me to the stackoverflow fix which had me enable ASP.NET 4.7.
SUCCESS! FIXED
Upvotes: 1
Reputation: 3409
After some playing with this bug in IIS 10 I managed to transform from HTTP Error 503 into HTTP Error 403.14. For this case solution was to add
<system.webServer>
<modules runAllManagedModulesForAllRequests="true"/>
</system.webServer>
into project Web.config
file.
Original info here:
https://serverfault.com/questions/405395/unable-to-get-anything-except-403-from-a-net-4-5-website
Upvotes: 0