Solution to the failure to send a session Status Request error to the session Status Server

The error is as follows:

"/" Indicates a server error in the application.

Unable to send a session Status request to the session Status server. Make sure that ASP. NET State Service (ASP. NET State Service) is started and the client port is the same as the server port. If the server is on a remote computer, check the value of HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services \ aspnet_state \ Parameters \ allowremoteconnection to ensure that the server accepts remote requests. If the server is located on the local computer and the registry value mentioned above does not exist or is set to 0, the status server connection string must use "localhost" or "127.0.0.1" as the server name.
Note: unprocessed exceptions occur during the execution of the current Web request. Check the stack trace information for details about the error and the source of the error in the code.
Exception details: system. Web. httpexception: unable to send a session Status request to the session Status server. Make sure that ASP. NET State Service (ASP. NET State Service) is started and the client port is the same as the server port. If the server is on a remote computer, check the value of HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services \ aspnet_state \ Parameters \ allowremoteconnection to ensure that the server accepts remote requests. If the server is located on the local computer and the registry value mentioned above does not exist or is set to 0, the status server connection string must use "localhost" or "127.0.0.1" as the server name.

 

Cause analysis:
In web. config, the mode of sessionstate is set to StateServer, but the server does not enable or change the service.
Solution:
1. In web. config, change the sessionstate mode to "inproc ";
2. Enable "ASP. NET State Service" in the service"

 

Session model Overview
What is session? Simply put, it is the number that the server sends to the client. When a WWW server is running, several users may browse the website running on this server. When a user establishes a connection with the WWW server for the first time, the user establishes a session with the server, and the server automatically assigns a sessionid to the user to identify the unique identity. This sessionid is a random string consisting of 24 characters on the WWW server. We will see it in the following experiment.
This unique sessionid has great practical significance. When a user submits a form, the browser automatically attaches the user's sessionid to the HTTP header information (this is an automatic function of the browser and the user will not notice it ), after the server processes the form, it returns the result to the user corresponding to the sessionid. Imagine how the server knows which user submitted the form when two users register simultaneously without sessionid. Of course, sessionid has many other functions, which we will mention later.
In addition to sessionid, each session contains many other information. However, for ASP or ASP. NET Programming and programming, the most useful thing is to access ASP/ASP. NET's built-in Session object to store their own information for each user. For example, if we want to know how many pages a user visits our website browses, we may add the following to each page that a user may access:
<%
If SESSION ("pageviewed") = "" then
Session ("pageviewed") = 1
Else
Session ("pageviewed") = SESSION ("pageviewed") + 1
End if
%>
You can use the following sentence to learn about several pages you have browsed:
<%
Response. Write ("You have viewed" & SESSION ("pageviewed") & "pages ")
%>
Some readers may ask: where does this seemingly array SESSION ("...") come from? Do I need to define it? In fact, this session object is a built-in object of the WWW server with ASP interpretation capability. That is to say, this object has been defined for you in the ASP system, and you only need to use it. The variable name in session ("...") is like the variable name. In session ("...") = $, $ is the variable value. You only need to write a sentence to access the value in the variable .. on every page of the user.
In fact, Asp has a total of seven built-in objects, including session, application, Cookie, response, request, server, etc. Similar objects are also available in other server-side scripting languages such as JSP and PHP, but they are not the same in terms of naming or usage.
ASP session functional defects
Currently, ASP developers are using session, but they have discovered the following defects in ASP session:
Process dependency: the ASP sessionstate is stored in the iisprogress, And the inetinfo.exe program is also used. When the inetinfo.exe process crashes, the information is lost. In addition, restarting or disabling the IIS service will cause information loss.
Limitations of the range of session Status usage: when a user accesses another website from one website, the session information will not be migrated. For example, there may be more than one WWW server on the Sina website. After a user logs on, he/she will go to various channels, but each channel is on a different server, what if I want to share session information on these www servers?
Cookie dependency: in fact, the client's session information is stored in the cookie. If the client completely disables the cookie function, it cannot enjoy the function provided by the session.
In view of the above defects of ASP session, Microsoft designers are designing and developing ASP. net session, and the above defects are completely overcome, making ASP. net session has become a more powerful feature.
Introduction to the Web. config file
Some ASP. NET programmers say: What is the Web. config file? I have never heard of it, but can the program I wrote work properly? Yes, you are right. Without the Web. config file program, it can run normally. However, if you create a large website, you need to make some overall configuration for the entire website, for example, you need to use the web. config file. Although some options in the web. config file can be configured through IIS, if the corresponding settings in Web. config also overwrite the configuration in IIS. In addition, the biggest convenience of the web. config file is that you can access the settings in Web. config by calling the system. Web namespace on the ASP. NET page.
There are two types of Web. config: the server configuration file and the web application configuration file, both named Web. config. This configuration file stores a series of information about the web pages written in which language, Application Security Authentication mode, and session information storage mode on the current IIS server. This information is saved using XML syntax. If you want to edit it, use the text editor.
The server configuration file takes effect for all applications on all sites on the IIS server. In. NET Framework 1.0, the Web. config file of the server exists in \ winnt \ Microsoft. NET \ framework \ v1.0.3705.
The Web application configuration file web. config is stored in various web applications. For example, the root directory \ Inetpub \ wwwroot of the current website, and the current web application is myapplication, the root directory of the Web application should be \ Inetpub \ wwwroot \ myapplication. If your website has only one web application, the root directory of the application is \ Inetpub \ wwwroot. To add a web application, add a virtual directory with the application starting point in IIS. The files and directories under this directory are considered as a web application. However, adding a web application through IIS does not generate a web. config file for you. To create a web application with a web. config file, use Visual Studio. NET to create a web application project.
The Web. config configuration file of the Web application is optional and optional. If not, each web application uses the Web. config configuration file of the server. If yes, the corresponding values in the web. config configuration file of the server will be overwritten.
In ASP. NET, modifications to Web. config will automatically take effect immediately after they are saved. You do not need to restart the web application to take effect after modifying the configuration file in ASP.
Session configuration information in the web. config file
After opening the configuration file web. config of an application, we will find the following section:
<Sessionstate
Mode = "inproc"
Stateconnectionstring = "TCPIP = 127.0.0.1: 42424"
Sqlconnectionstring = "Data Source = 127.0.0.1; trusted_connection = yes"
Cookieless = "false"
Timeout = "20"
/>
This section describes how the application stores session information. The following operations mainly aim at this configuration section. Let's take a look at the meaning of the content contained in this section. The syntax of the sessionstate node is as follows:
<Sessionstate mode = "off | inproc | StateServer | sqlserver"
Cookieless = "True | false"
Timeout = "number of minutes"
Stateconnectionstring = "TCPIP = serverort"
Sqlconnectionstring = "SQL connection string"
Statenetworktimeout = "number of seconds"
/>

The required attribute is
Attribute option description
Mode setting: Where to store session information
Off is set to not use the session Function
Inproc is set to store sessions in the process, which is the storage method in ASP. This is the default value.
StateServer is set to store sessions in independent State services.
Sqlserver settings store sessions in SQL Server.

 

Solution to the failure to send a session Status Request error to the session Status Server