Server errors in ASP. NET applications (in progress)

1. Unable to verify data:
Solution: In the page command, disable MAC (Authentication Code ):
<% @ Page enableviewstatemac = "false">

Personal analysis: When a webpage is submitted to itself, the server checks the view status through Mac to see if the status is changed on the client. however, this leads to a potential problem, that is, the status of the server is usually maintained for a short period of time. If you submit the page after the server State disappears, the Mac verification will fail, error message that cannot be verified.

This solution also has a lot of trouble. For example, you need to add this command to each page submitted to you. there are also some security risks, such as malicious changes to the view status. who else can provide better solutions.

2. -- "/" ApplicationProgramServer Error in (solution in WINXP)
1) the "Security" tab is displayed.
Open "Folder Options" in "Control Panel ".
Click Start, and then click Control Panel ".
Double-click "Folder Options ".
On the "View" tab, under "Advanced Settings", clear "use simple file sharing (recommended )".
2) Add the ASPNET user to your site folder on the Folder Security tab.
3) add write rights to the users of this folder
3. During project debugging, a "Access Denied" component is used.

Sometimes, when we debug the Asp.net program, it will be very painful. Access to a certain component is denied. At this time, Restarting IIS does not work when the computer logs out. At this time, the error message is generally similar to the following method:

"/" Indicates a server error in the application.
-------------------------------------------------------------------------------- Configuration error
Note: An error occurred while processing the configuration file required to provide services to the request. Check the following error details and modify the configuration file as appropriate. Analyzer error message: Access Denied: "csdn. Authentication ". Source error: Line 196: <add Assembly = "system. enterpriseservices, version = 1.0.5000.0, culture = neutral, publickeytoken = b03f5f7f11d50a3a"/>
Line 197: <add Assembly = "system. Web. Mobile, version = 1.0.5000.0, culture = neutral, publickeytoken = b03f5f7f11d50a3a"/>
Row 198: <add Assembly = "*"/>
Row 199: </assemblies>
Row 200: </compilation>

Source File: C: \ WINDOWS \ microsoft.net \ framework \ v1.1.4322 \ config \ machine. config row: 198

Assembly loading tracking: The following information helps determine the reason why the assembly "csdn. Authentication" cannot be loaded. === Pre-bind state information ===
Log: displayname = csdn. Authentication
(Partial)
Log: appbase = file: // F:/mydevelop/AD/code/admanageweb
Log: initial privatepath = Bin
Calling Assembly: (unknown ).
===
Log: policy not being applied to reference at this time (private, custom, partial, or location-based assembly bind ).
Log: Post-Policy Reference: csdn. Authentication
Log: Attempting download of new URL File: // C:/Windows/Microsoft. net/framework/v1.1.4322/Temporary ASP. net files/root/3151f96f/581ce000/csdn. authentication. DLL.
Log: Attempting download of new URL File: // C:/Windows/Microsoft. net/framework/v1.1.4322/Temporary ASP. net files/root/3151f96f/581ce000/csdn. authentication/csdn. authentication. DLL.
Log: Attempting download of new URL File: // F:/mydevelop/AD/code/admanageweb/bin/csdn. Authentication. dll.
Log: policy not being applied to reference at this time (private, custom, partial, or location-based assembly bind ).
Log: Post-Policy Reference: csdn. Authentication, version = 1.0.1965.30523, culture = neutral, publickeytoken = NULL
--------------------------------------------------------------------------------
Version: Microsoft. NET Framework Version: 1.1.4322.2300; ASP. NET version: 1.1.4322.2300

The most common cause is the Indexing Service. The solution is to disable the indexing service, or configure the temporary directory of Asp.net not to be affected by the Indexing Service.

To configure the temporary directory of Asp.net not affected by the Indexing Service, follow these steps:

1. Start-management tools-Computer Management (similar to other operating systems in win2003)
2. Expand the "service and application" node in the left-side tree of Computer Management, then expand the "Index Service" node under it, and then expand the "System" node under it, expand the "directory" node under it.
3. On the right of Computer Management, we can see the configured index service directory.
4. Right-click the "directory" node and choose "New"> "directory"
5. In the "add directory" dialog box, enter the temporary file directory of Asp.net in the input box. The default value is:
C: \ <WINDIR> \ Microsoft. Net \ framework \ <version number> \ temporary ASP. NET Files directory.
<Version number> indicates the. NET version to be processed.
6. Is it included in the index ?" Select "no"
7. Click OK.
8. Right-click the "Index Service" node and restart the Index Service.
Another method is to create a project that references a third-party DLL and runs it locally. However, if it is put on the server, an error occurs: access is denied.

First, I tried it according to the author's method. The problem persists, whether it is to stop the index service or
The temporary directory is processed, and access to the component is still denied.
So my solution is: Put the DLL of my project and the referenced DLL on the server at the same time, so that the update time of the two DLL on the server is the same, so that the problem is solved, I don't know why, it's related to time.
In addition, if not, consider the components you reference and the version of your debugging project. It is best to use the release version.