Solution for server errors in the "/" application (two cases)

Case (a) Problem Description “/” Server error in the application. -------------------------------------------------- ------------------------------ Configuration error Explanation: An error occurred while processing the configuration file required to service the request. Please check the specific error details below and modify the configuration file as appropriate.

Parser Error Message: Failed to load file or assembly “System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35” or one of its dependencies. The system can not find the file specified.

Source Error:

Line 36: <add assembly="System.Design, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A" /> Line 37: < ;add assembly="System.DirectoryServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A" /> Line 38: <add assembly="System.Web.Extensions, Version=1.0.61025.0, Culture =neutral, PublicKeyToken=31BF3856AD364E35"/> Line 39: </assemblies> Line 40: </compilation> Source File: F:\\WebUI\\web.config Line: 38 Assembly Load Tracking: The following information helps Determine the assembly “System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35”The reason why the load could not be loaded.

Warning: Assembly binding logging is turned off. To enable assembly binding failure logging, set the registry value [HKLM\\Software\\Microsoft\\Fusion!EnableLog] (DWORD) to 1. Note: There will be some performance penalty associated with assembly binding failure logging. To turn off this feature, remove the registry value [HKLM\\Software\\Microsoft\\Fusion!EnableLog].

Solution: Please set the registry value [HKLM\\Software\\Microsoft\\Fusion!EnableLog] (DWORD) to 1. Modify it on the line
Case (2) Solution: Increase the ntfs permission of the directory where the site is located, and increase the complete control of the service user to the site directory. The error message is as follows: Runtime error description: An application error occurred on the server. The current custom error setting for this application prohibits remote viewing of application error details (for security reasons). But it can be viewed by a browser running on the local server computer. More information: To enable others to view the details of this particular error message on a remote computer, create a <customErrors> tag in the “web.config” configuration file located in the root of the current web application. You should then set the <customErrors> tag's “mode” attribute to “Off”. <!-- Web.Config Configuration File--><configuration><system.web><customErrors mode="Off"/></system.web></configuration> Notes: You can replace the current error page you see with a custom error page by modifying the application's <customErrors> configuration tag's <defaultRedirect” property to point to the URL of the custom error page. <!-- Web.Config configuration file--><configuration><system.web><customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/></system.web> ;</configuration>“/” server error in the application. Configuration Error Description: An error occurred while processing the configuration file required to service the request. Please check the specific error details below and modify the configuration file as appropriate. Parser error message: Unrecognized configuration section <;connectionStrings” Source Error: Line 12: <add key="Dsn" value="server=(local);database=al_bysj;uid=sa;pwd=" ;/>Line 13: </appSettings> Line 14: <connectionStrings> Line 15: <add name="al_bysjConnectionString" connectionString="Data Source=(local);Initial Catalog=al_bysj;User ID= Sa;Password=" providerName="System.Data.SqlClient"/> Line 16: </connectionStrings> Source file: D:\\PrecompiledWeb\\MaterialManage\\web.config Line: 14 Version Information: Microsoft .NET Framework Version: 1.1.4322.2300; ASP.NET version: 1.1.4322.2300 can be captured from the version information. To confirm your version of Microsoft .NET Framework, I am using Microsoft .NET Framework 2.0. Solution one: Run C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/aspnet_regiis.exe in the cmd command line. Solution 2: Select the website in IIS and right click ‘properties & rsquo;, Select the Asp.net tab bar. Change the Asp.net version to 2.0.