Problem in running .net framework 4.0 website on iis 7.0

后端 未结 12 595
忘掉有多难
忘掉有多难 2020-12-24 00:22

Hey I got problem in running .NET framework 4.0 website on IIS7.0. the error I got is like:

HTTP Error 404.2 - Not Found \

相关标签:
12条回答
  • 2020-12-24 00:34

    Step 1: Open IIS and click the server name Step 2. Double click “ISAPI and CGI Restrictions” Step 3. Right click ASP.NET v4.0.30319 and select “allow”

    After Stopping and Starting the World Wide Web Publishing Service

    1.Go to Start > All Programs > Administrative Tools > Services. 2.In the services list, right-click World Wide Web Publishing Service, and then click Stop (to stop the service), Start (to start it after it has been stopped), or Restart (to restart the service when it is running).

    Pramesh

    0 讨论(0)
  • 2020-12-24 00:40

    Go to IIS manager and click on the server name. Then click on the "ISAPI and CGI Restrictions" icon under the IIS header. Change ASP.NET 4.0 from "Not Allowed" to "Allowed".

    0 讨论(0)
  • 2020-12-24 00:42

    If you look in the ISAPI And CGI Restrictions, and everything is already set to Allowed, and the ASP.NET installed is v4.0.30319, then in the right, at the "Actions" panel click in the "Edit Feature Settings..." and check both boxes. In my case, they were not.

    0 讨论(0)
  • 2020-12-24 00:42

    After mapping of Application follow these steps

    Open IIS Click on Applications Pools Double click on website Change Manage pipeline mode to "classic" click Ok.

    Ow change .Net Framework Version to Lower version

    Then click Ok

    0 讨论(0)
  • 2020-12-24 00:43

    Try changing the AppPool Manged Pipeline Mode from "Integration" to "Classic".

    0 讨论(0)
  • 2020-12-24 00:49

    In our case the solution to this problem did not involve the "ISAPI and CGI Restrictions" settings. The error started occuring after operations staff had upgraded the server to .NET 4.5 by accident, then downgraded to .NET 4.0 again. This caused some of the IIS websites to forget their respective correct application pools, and it caused some of the application pools to switch from .NET Framework 4.0 to 2.0. Changing these settings back fixed the problem.

    0 讨论(0)
提交回复
热议问题