The four most common problems encountered during IIS6 ASP. NET 4.0 Installation

Yesterday, my colleague submitted an ASP.. Net 4.0 websites are installed on the customer's IIS6 host (test environment), and the results are not smooth, they once thought that the customer's host did not know how many hands had been broken (because many people are sharing the Administrator account), and then refused to install the host on the customer's host and "why should we use ASP. "net 4" feeling, but with the efforts of a group of people, I finally overcome the difficulties. I especially wrote down my notes and believe that other people may encounter these problems.

To run an ASP. NET 4.0 website, you must first install Microsoft. NET Framework 4.

Before installation, make sure that your operating system version is supported:

• Windows XP SP3
• Windows Server 2003 sp2
• Windows Vista SP1 (inclusive) and later versions
• Windows Server 2008 (not supported by server core roles)
• Windows 7
• Windows Server 2008 R2 (not supported by server core roles)

FAQs1: SetWebsiteOfASP. NETASP. NET 4.0 option not found on the tab

Note: If you do not support ASP. NET only when installing. NET Framework client profile, you must download Microsoft. NET Framework 4 (an independent installer) to complete the installation.

Normally, As long as Windows Server 2003 has installed IIs before installing Microsoft. NET Framework 4WebsiteOfASP. NETOn the tab, select ASP. NET 4.0:

FAQs2: Setting still not found after. Net 4 is installedWebsiteOfASP. NETASP. NET 4.0 option on the tab

This problem usually occurs when Microsoft. NET Framework 4 is installed before IIS6 is installed. In this case, you must enter the following command to register ASP. NET 4.0 with IIS6:

C: \ windows \ Microsoft. NET \ framework \ v4.0.30319 \ aspnet_regiis.exe-ir-enable

FAQs3: Install. Net 4 and set it.WebsiteThe ASP. NET 4.0 option still cannot execute the website

The "unable to execute Website" page appears.This page cannot be found (HTTP Error 404-unable to find the file or directory), no matter how you set the Directory Security or any execution permission, you cannot execute any ASP. NETProgramAnd only static pages can be read. For example, it is easy for IT personnel to know how to display such a general error message:

If you set "wildcard application correspondence" for ASP. net mvc installation, you will find that all pages of the website, including static files, will respondThis page cannot be found Error!

This problem occurs because IIS6 blocks the execution of the c: \ windows \ microsoft.net \ framework \ v4.0.30319 \ aspnet_isapi.dll program. All requests directed to this ISAPI handler will fail, therefore, all your HTTP requirements will get the HTTP 404 Not found result.

The solution is simple, as long [Webpage Service ExtensionTo set ASP. NET v4.0.30319 [Allow] As shown in:

FAQs4: The website platform of ASP. NET 4.0 has been set up and can be executed normally, but it will be suspended for a while!

If you are in the sameApplication assembly areaTwo different versions of ASP are set. net will cause this problem, for example, you have an ASP.. NET 2.0 platform, and set the application assembly area to defaultapppool. However, you then added an ASP. net 4.0 platform, and the default application assembly area is also in the defaultapppool, there will be a conflict, then you will see which platform is first executed, the platform that runs first will grab the ownership, and the one that runs later will cause the server application unavailable or the server application cannot be used:

There are two solutions:

• ShareWebsite OrWebsite application(Virtual directory)All are set to ASP. NET v4.0.30319
• Distinguish two different application assembly zones