0

All,

I am migrating a working .Net Framework Website from IIS 8.5 on a Microsoft Windows Server 2012 to IIS 10 on a Microsoft Windows Server 2019.

The new web site is showing the error

HTTP Error 403.14 - Forbidden
The Web server is configured to not list the contents of this directory.

As far as I can see the website on the new server is configured the same as on the existing.

Neither have directory Browsing enabled nor a default file set as is recommended by most of the posts which exist discussing this error.

I have run the following which is also recommended.

%windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -ir

The problem still exists.

I came across a post saying there might be an issue if paths referenced in the web.config are not correct but they look fine.

Has anyone got any insight into what else might cause this issue?

Are there any differences between IIS 8.5 and IIS 10 or between windows servers 2012 and 2019 which might cause this issue?

Thanks

kevins1966
  • 366
  • 2
  • 4
  • 19
  • What is the URL(s) that gives you 403.14? Make sure you have a home page https://stackoverflow.com/questions/1142003/set-homepage-in-asp-net-mvc or 403.14 is expected. – Lex Li Dec 12 '22 at 17:28

2 Answers2

-1

This problem occurs because the website doesn't have the Directory Browsing feature enabled. Also, the default document isn't configured. To resolve this problem, use one of the following methods:

Method 1: Enable the Directory Browsing feature in IIS

To resolve this problem, follow these steps:

  1. Start IIS Manager. To do it, select Start, select Run, type inetmgr.exe, and then select OK.
  2. In IIS Manager, expand server name, expand Web sites, and then select the website that you want to change.
  3. In the Features view, double-click Directory Browsing.
  4. In the Actions pane, select Enable.

Method 2: Add a default document

To resolve this problem, follow these steps:

  1. Start IIS Manager. To do it, select Start, select Run, type inetmgr.exe, and then select OK.
  2. In IIS Manager, expand server name, expand Web sites, and then select the website that you want to change.
  3. In the Features view, double-click Default Document.
  4. In the Actions pane, select Enable.
  5. In the File Name box, type the name of the default document, and then select OK.

More information you can refer to this link: HTTP Error 403.14 - Forbidden when you open an IIS webpage.

samwu
  • 3,857
  • 3
  • 11
  • 25
  • Hey @samwu, I am not sure what you are trying to achieve with this response. It's pretty much word for word and format for format identical to a number of posts that anyone can find. Your response adds no value and it's obvious there is more to this error then this explanation. If you read my question it states that this issue I am having on one server does not happen on another where neither of the options you recommend are configured. – kevins1966 Dec 14 '22 at 10:20
-1

All those clowns glibly posting that "HTTP Error 403.14 - Forbidden: The Web server is configured to not list the contents of this directory" can be fixed by configuring the web site by either enabling the Directory Browsing feature or adding a default document are really not understanding what they are talking about. Anyone can copy a solution from one post and paste to another.

I'm not going to pretend I know what I am talking about but I have fixed my issue and will share what I did here to see in the hope it helps others.

I created a project (of the same type as the application I was trying to deploy) using my IDE (MSVS) in the same .Net version of the application I was trying to deploy. In this case it was creation of an MVC project in .Net Framework 4.5.

I did nothing to it. All I wanted was a skeleton.

I replaced all the files in the home directory of the web site I had an issue with, with the files of this skeleton project.

I attempted to browse to the web site and it worked successfully. Note the directory browsing was not enabled nor was a default directory set.

This proved to me that those settings were irrelevant.

Having googled around, some sites point to paths in config files causing an issue if they do not exist, eg a logging path to d:\logs where that directory was missing. It didn't fix my issue but there's no harm checking.

I stumbled across a post which talked about the roles and features enabled on the server. In Web Server (IIS)/Web Server/Application Development they had selected "Application Initialisation" and "ASP".

The Windows Sever 2012 server I was moving the application from, where it work without a hitch, did not have those selected so had not selected them on the Windows Server 2019 I was moving them to when I set that server up.

It made no sense that this would be the solution but having tried everything else I activated those two options. Stone me if the issue was resolved.

As a check I removed those two options and the problem came back and when I reselected them it went away again.

This struck me as pretty conclusive only having thought I'd found the cause of the problem I built the website from scratch and the problem came back again.

It took a number of iterations but eventually I got there, more by luck than judgement and whatever the cause was it was due to an issue in the application which wasn't being logged in event viewer so focus on permissions to files being written to: not only that the app pool account is set up on the directories it needs access to but also that it has modify or even full control.

All those muppets robotically posting advice on configuring the web site by either enabling the Directory Browsing feature or adding a default document will no doubt copy this and paste it into their posts to claim the credit but c'est la vie.

I hope this post is of use to someone, apart from those muppets.

kevins1966
  • 366
  • 2
  • 4
  • 19