如何在IIS 10运行ASP.Net MVC 4应用？升级后遇403.14错误求助

Hey there! Let's work through this 403.14 error you're facing after upgrading to Windows 10, switching to VS 2017, and setting up IIS 10 for your ASP.NET MVC 4 app. This error typically means IIS can't resolve the default entry point for your app or isn't configured to handle MVC's routing properly. Here are the most effective fixes to try:

1. Verify Default Document Settings #

IIS might not recognize your MVC app's default page (like Home/Index). To fix this:

• Open IIS Manager, navigate to your website, and double-click Default Document.
• Click Add and enter Index.cshtml (or your app's default view name) if it's not already listed.
• Ensure Default.aspx or Global.asax are in the list too, and move your preferred default page to the top of the priority order.

2. Enable ASP.NET 4.5 in Windows Features #

MVC 4 relies on ASP.NET 4.5, which might not be enabled by default on Windows 10:

• Open Control Panel > Programs > Turn Windows features on or off.
• Expand Internet Information Services > World Wide Web Services > Application Development Features.
• Check the box for ASP.NET 4.5, then click OK.
• Restart IIS by running iisreset in an elevated Command Prompt.

3. Re-register ASP.NET with IIS #

After upgrading your OS or Visual Studio, ASP.NET might not be properly registered with IIS. Run these commands in an elevated Command Prompt:

• For 32-bit systems:

  C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -i
  

• For 64-bit systems:

  C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -i
  

• Restart IIS again with iisreset.

4. Ensure URL Routing Module is Enabled #

MVC's routing system depends on the UrlRoutingModule-4.0 module in IIS:

• In IIS Manager, select your website and click Modules in the Features View.
• Look for UrlRoutingModule-4.0 in the list. If it's missing, running the aspnet_regiis.exe -i command from step 3 should register it.
• Also, confirm that your app's web.config has the correct routing configuration (MVC 4 projects usually include this by default, but double-check if you've modified the config).

5. Check Folder Permissions for the App Pool #

The IIS application pool identity needs read/execute access to your app's physical folder:

• Right-click your app's root folder, go to Properties > Security.
• Click Edit > Add, then enter IIS AppPool\[Your App Pool Name] (replace [Your App Pool Name] with the name of your app's pool).
• Grant the identity Read & Execute, List Folder Contents, and Read permissions, then click OK.

6. Disable Directory Browsing #

Since MVC apps don't rely on directory listing, make sure this is disabled to force IIS to use routing or default documents:

• In IIS Manager, select your website and click Directory Browsing in the Features View.
• Click Disable in the Actions pane on the right.

Start with steps 1-3 first—those are the most common culprits for this error. If none of these work, double-check your web.config for any routing errors or missing handlers.

内容的提问来源于stack exchange，提问作者Sreekanth Jagaleti