This article is a mirror article of machine translation, please click here to jump to the original article.

View: 14859|Reply: 0

[ASP.NET] asp.net Resolution for MVC4 IIS7.5 403.14 error

[Copy link]
Posted on 5/6/2016 3:51:46 PM | | |
1. Publishing mvc3 error: 403.14 - Forbidden web server is configured not to list the contents of this directory

After tossing for a long time, the solution in the prompt is:

If you do not want to enable directory browsing, make sure that the default document is configured and that the file exists.
Use IIS Manager to enable catalog browsing.
Open IIS Manager.
In the Features view, double-click Catalog Browse.
On the Catalog Browse page, click Enable in the Actions pane.
Verify that the configuration/system.webServer/directoryBrowse@enabled property in the site or application configuration file is set to True.
After changing according to this method, I found that the web page running interface became a directory structure, and later I found that after changing the configuration section of the configuration file web.config configuration file, the website can be used normally, record it.

<system.webServer>
    <validation validateIntegratedModeConfiguration="false" />
    <modules runAllManagedModulesForAllRequests="true" />
        <directoryBrowse enabled="false" />
  </system.webServer>

The <modules>value of the section to be set to true does not actually affect whether directory browsing is enabled or disabled.

2. After publishing, the login interface can be displayed, an error is reported when jumping to the page to access the database, Login on failed for "IIS APPPOOL\ASP.NET v4.0", and it is found that the "IIS APPPOOL\ASP.NET v4.0" of the web page has no permission to access the database, and the user login name "IIS APPPOOL\ASP.NET v4.0" has been added to the database, and all permissions have been added, and it is ready to use.



It's all on top!!!!!

Learn to develop projects with asp.net MVC4 today.

When publishing the project to the local IIS (WIN7+IIS7.5), the access was unsuccessful. Solution:

Add a configuration <modules runAllManagedModulesForAllRequests="true" /> under the <system.webServer> node in the root directory





Previous:As a junior programmer, I did a winform C/S project for a month, just learned to copy the code and then implement it
Next:C# obtains system information, including operating system memory usage, etc
Disclaimer:
All software, programming materials or articles published by Code Farmer Network are only for learning and research purposes; The above content shall not be used for commercial or illegal purposes, otherwise, users shall bear all consequences. The information on this site comes from the Internet, and copyright disputes have nothing to do with this site. You must completely delete the above content from your computer within 24 hours of downloading. If you like the program, please support genuine software, purchase registration, and get better genuine services. If there is any infringement, please contact us by email.

Mail To:help@itsvse.com