Can your. NET 2.0 and 1.1 run securely and correctly on the same computer? Server application unavailable Error

ArticleDirectory

• Server application unavailable

Of course, the answer is yes.HoweverNoBy default, problems may occur during any processing!
Be careful when installing and running. NET 1.1 and. NET 2.0 on the same computer!
Does your project occasionally encounter server application unavailable errors? Or this error is reported continuously!

Today, my friend upgraded the project from 1.1 to 2.0 and released it to the company's server with Windows 2003 installed. As a result, the project in 2.0 never runs successfully. The. NET Framework 1.1-based WebProgramError. He felt very strange. He was running very well on his computer. How could he not do it as soon as he got to the server?
The process of releasing the 2.0 web program is as follows:
1. Create a directory on the server and copy the files of all published web programs to the new directory.
2. Create a new virtual directory on the server's IIS and configure it as an application that can execute scripts (the process is the same as that of creating a. NET Framework 1.1 program .) Then, configure the. NET Framework of this virtual directory to 2.0.
After success, the following error occurs when you access the configured program:

Server application unavailable

The Web application you are attempting to access on this web server is currently unavailable. Please hit the "refresh" button in your web browser to retry your request.

Administrator note: An error message detailing the cause of this specific request failure can be found in the application event log of the Web server. Please review this log entry to discover what caused this error to occur.
Then I asked for help. After carefully reading the IIS Help documentation, I found that this error was caused by the IIS6 application isolation mechanism. The default application isolation mechanism of IIS is called: "Working Process Isolation Mode" In this mode, applications are divided into multiple groups, each group is an "Application pool", and each application pool is isolated from each other. The benefits of isolation are security, stability, and so on. Each application pool in IIS is managed by a "worker process", that is, "w3wp.exe ". If you run multiple applications in the application pool, we can see multiple w3wp.exe. The created virtual directories are directed to the "ultultapppool" in iis6.
The cause of the above error is :.. NET Framework 2.0 program and. net framework1.1 (or 1.0) programs are put into the same application pool (ultapppool pool by default), that is, managed by the same worker process: w3wp.exe, however, a single working process cannot manage different programs (or different versions of programs) at the same time. If you first access. net Framework 1.1 page, the worker first loads and manages the assembly of Version 1.1. net Framework 2.0 web application page, the server application unavailable error is returned. In contrast, if w3wp.exe in the development application pool has accessed the 2.0 web application before it is started (the application assembly has been loaded at this time. net Framework 1.1 web assembly). When you access the Web application page of 1.0 or, a Chinese prompt such as "server application unavailable" will also appear. (You can use w3wp.exe to test .)
My friend didn't see this error on his development machine because he was developing based on. net Framework 2.0 project, always only access this 2.0 web program, and this has never accessed other web programs. There are already 1.0 projects on a friend's server, and they have been used all the time. This error has never been encountered before. In fact, most people only access the project being developed when developing a project. It is very likely that this problem has been ignored, but an error occurred during the release, making it messy.

 
Solution: Create an application pool in IIS and select your application pool. net framework2.0 virtual directory, click "properties"-> select the application pool you just created in "application pool", and click "OK ".
 

Address: http://www.cnblogs.com/cwbboy/archive/2006/07/11/339710.html