Solution of common errors in asp. net operation

Error 1: IIS does not recognize ASP. NET and reports the following error:

Name begins with an invalid character. Error processing resource 'http://localhost/likong/'. Line 1, position: 2

Solution:

Run in a command window:

C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -i [.NET 1.1] 

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i [.NET 2.0]

Failed to load the file or assembly "EnvDTE, Version=8. 0.0. 0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" or one of its dependencies. The system cannot find the specified file.

From the Start menu, select Search for the following 2 files: EnvDTE. dll, EnvDTE80.dll. And copy these two files to the BIN directory in the virtual space (if there is no such directory, create it manually)

Error 2: How to resolve "using registration as allowDefinition = 'MachineToApplication outside the application level

Error 1 It is an error to use a section registered as allowDefinition = 'MachineToApplication' outside the application level. This error can occur if the virtual directory is not configured as an application in IIS. D:\ myweb\ YuJieSuanGenZong\ WebApplication1\ WebApplication1\ Web.config 25

Cause of the error: View all the folders involved in the project. This error occurs if there are two web. config.

Solution: Delete redundant web. config files

Error 3: An error occurred while establishing a connection to the server. When connecting to SQL Server 2005, SQL Server does not allow remote connections under the default settings, which may cause this failure. (provider: SQL Network Interface, error: 26-Error locating specified server/instance)
Solution: First, verify that SQL SERVER EXPRSS is installed on the local computer and that the SQL SERVER (SQLEXPRESS) service has started successfully. If the problem persists, try to open SQL Server Surface Area Configurator, select Surface Area Configurator for Services and Connections, and then configure Remote Connection to use both TCP/IP and named pipes.

These three errors are often encountered when operating ASP. NET. I hope this article can really help you solve these problems.