Common errors and Solutions in the process of asp.net Operation
This article introduces the knowledge of "common mistakes and solutions in the operation of asp.net". In the operation of actual cases, many people will encounter such a dilemma, so let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!
Error 1: IIS does not recognize ASP.NET and reports the following error:
The name begins with invalid characters. Error processing resource 'http://localhost/likong/'. Line 1, location: 2
Solution:
Run in the 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 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.
Select search for the following 2 files from the start menu: EnvDTE.dll,EnvDTE80.dll. And copy the 2 files to the BIN directory in the virtual space (if there is no such directory, you will create it manually)
Error 2: how to solve the problem of using registration as allowDefinition='MachineToApplication outside the application level
Error 1 it is wrong to use a section registered as allowDefinition='MachineToApplication' outside the application level. This error may occur if the virtual directory is not configured as an application in IIS. D:\ myweb\ YuJieSuanGenZong\ WebApplication1\ WebApplication1\ Web.config 25
Cause of error: look at all the folders involved in the project, and this error will occur if there are two web.config.
Solution: delete redundant web.config files
Error 3: error establishing a connection to the server. When connecting to SQL Server 2005, SQL Server does not allow remote connections by default, which may cause this failure. (provider: SQL network interface, error: 26-error locating specified server / instance)
Solution: first make sure that SQL SERVER EXPRSS is installed on your local computer and that the SQL SERVER (SQLEXPRESS) service has been started successfully. If the problem persists, you can try to open the SQL Server Peripheral Application Configurator, select the Peripheral Application Configurator for Services and connections, and then configure remote connection to use both TCP/IP and named pipes.
This is the end of the content of "common mistakes and solutions in the operation of asp.net". Thank you for your reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!