"Visual studio.net has detected that the specified web server is not running ASP. net1.1. You will not be able to run the Asp.net web application or service "problem solution

Solution 1:

1. Check whether. NET Framework 1.1 is installed. You can view the directory. c: \ winnt \ microsoft.net \ framework restarts IIS and restarts the computer (general error correction method)

2. if your web server uses a fixed IP Address: Make sure that the "Default web site" is used in your "Internet Information Service" and the IP address in the property is "(all unallocated )", not the specified IP address. Do not delete the default web site. If yes, you can create a directory named "Default web site.

3. If IE uses a proxy, "Do not use a proxy server for local addresses" is checked.

4. For configuration problems, choose "start" in Windows>Program-> Visual Studio. NET 2003-> Visual Studio.. Net tool-> Visual Studio. net command prompt, open the window, enter aspnet_regiis/I, wait a moment, prompt to start installation, end installation, return to the prompt.

5. reinstall IIS. Step 4 is also required after reinstallation.

Solution 2:

Yesterday, my colleague mm was debugging an installation. net web server again appears "Visual Studio. net has detected that the specified web server is not running ASP. NET 1.1 .. "Let me help you with the error. It took me half a day to fix it. What is the problem?

In the past, she deleted the "Default web site" in IIS and created a new site. When the site runs normally, it cannot be compiled or created. If a non-Version 1.1 error occurs, the previous error occurs because, the server uses a fixed IP address, and the administrator sets the IP address in the attribute as the specified IP address! Now it is necessary to make a summary!

Follow these steps:

1. Check whether version 1.1 is installed. Check the path c: \ winnt \ Microsoft. NET \ framework \ v1.1.4322.

2. As many people know, If you reinstall aspnet_regiis and how to install it, I will not say much about it. There are a lot of Internet resources!

3. Restart IIS and restart ASP. NET.

4. if your web server uses a fixed IP Address: Make sure that "Default web site" is used in your "Internet Information Service" and the IP address in its attribute is "(all are not allocated) instead of the specified IP address. You can modify the name of the "Default web site", but do not delete it. Once deleted, the name can be restored as long as it is strictly "Default web site" when it is created.

5. If your IE uses a proxy, check the bypass proxy server for local adresses.

6. If you already have a Web site, uninstall it without re-installing vs.net. You only need to reinstall IIS.

7. If the problem persists, there is no way to fix it. Reload IIS, framwork,. net, and the operating system.

Finally, let's talk about a security problem. Try not to point IIS to the default path c: \ Inetpub \ wwwroot, which is very vulnerable to attacks. It is best to point it back to a new path, and then delete the wwwroot folder. If you need to upload files, you must stop uploading ". "HTA" file to grant Website access permissions, block and execute the HTA file, and back up the database!

It is also a bit of work experience for your reference, less detours!

It is indeed a bug.

1. your web server uses a fixed IP Address: Make sure that "Default web site" is used in your "Internet Information Service" and the IP address in its attribute is "(all unallocated )", instead of the IP address you have specified. Then try again in vs. Net, which may solve the problem.
2. when the above method cannot solve the problem, consider the solution in msdn as follows:
Visual Studio. net cannot determine whether ASP is running on the Web server computer. NET 1.1. This error may occur in several different situations. Check whether the following conditions are true:
A. Make sure that. NET Framework 1.1 is installed on the Web server computer. For more information, see Visual Studio. NET software requirements.
B. If ASP. net has been installed on a Web server computer but still encounters this error, it may be a configuration problem. To correct problematic installation or configuration, you can use the ASP. NET utility named aspnet_regiis. You can find this command line utility in a path similar to the following:
C: \ WINDOWS \ Microsoft. NET \ framework \ v1.1.nnnn, where NNNN represents four internal version numbers. Search for the maximum version number. Use the/I switch to run the utility:
aspnet_regiis/I
prompts you to open the command window directly from the correct directory of the command. From the "Start" menu of windows, point to "program", "Visual Studio. NET 2003", "Visual Studio. NET tool", and select "Visual Studio. NET command prompt ". After the window opens, type aspnet_regiis/I.

No. Enter aspnet_regiis-R in vs.net command prompt of vs.net tool of the program.

The problem can be solved.
Take a closer look at the significance of the aspnet_regiis parameter.
Query parameter aspnet_regiis/all
All parameters are listed.