Unable to issue a session state request to the session-state server

Production environment:

Operating system: Win2003

Web:iis 6.0

Program language: ASP.

Operational issues:

Session state requests cannot be made to the session-state server. Make sure that the ASP. NET State service is started and that the client and server ports are the same. If the server is on a remote computer, please check the hkey_local_machine/system/currentcontrolset/services/aspnet_state/parameters/ The value of allowremoteconnection to ensure that the server accepts remote requests.
Description: An unhandled exception occurred during the execution of the current WEB request. Check the stack trace information For more information about the error and the source of the error in your code.
Exception Details: System.Web.HttpException: Unable to issue a session state request to the session-state server. Make sure that the ASP. NET State service is started and that the client and server ports are the same. If the server is on a remote computer, please check the hkey_local_machine/system/currentcontrolset/services/aspnet_state/parameters/ The value of allowremoteconnection to ensure that the server accepts remote requests.
SOURCE Error:
An unhandled exception was generated during the execution of the current WEB request. You can use the following exception stack trace information to determine information about the cause of the exception and where it occurred.
Stack trace:
[HttpException (0X8007274D): Unable to issue a session-state request to the session-state server. Make sure that the ASP. NET State service is started and that the client and server ports are the same. If the server is on a remote computer, please check the hkey_local_machine/system/currentcontrolset/services/aspnet_state/parameters/ The value of allowremoteconnection to ensure that the server accepts remote requests. ]
System.Web.SessionState.OutOfProcStateClientManager.MakeRequest (Stateprotocolverbverb, String ID, Stateprotocolexclusive exclusiveaccess, Int32 timeout, Int32lockcookie, byte[] buf, Int32 CB, Int32 networktimeout, Sessi Onndmakerequestresults&results)
System.Web.SessionState.OutOfProcStateClientManager.DoGet (String id,stateprotocolexclusive exclusiveaccess)
System.Web.SessionState.OutOfProcStateClientManager.GetExclusive (String ID)
System.Web.SessionState.StateClientManager.BeginGetExclusiveSync (String id,asynccallback CB, Object State)
System.Web.SessionState.OutOfProcStateClientManager.System.Web.SessionState.IStateClientManager.BeginGetExclusive (Stringid, AsyncCallback cb, Object State)
System.Web.SessionState.SessionStateModule.GetSessionStateItem ()
System.Web.SessionState.SessionStateModule.BeginAcquireState (Object Source,eventargs E, AsyncCallback cb, Object Extradata)
System.web.asynceventexecutionstep.system.web.httpapplication+iexecutionstep.execute ()
System.Web.HttpApplication.ExecuteStep (IExecutionStep step, boolean&completedsynchronously)

Cause Analysis:
Web. configThe mode of configuration sessionstate is StateServer, but the server does not turn on the service.

Workaround:
1.web.config inside the sessionstate mode changed to "InProc";
<sessionstate
Mode= "InProc"
Stateconnectionstring= "tcpip=127.0.0.1:42424"
sqlconnectionstring= "Data Source=127.0.0.1;user id=sa;password="
Cookieless= "false"
Timeout= "20"
/>

2. Enable in the service " ASP . NET State Service " 

The system uses the ASP. NET State Service to save the state, so it is stable. Instead, the IIS process is used to save the user state, because the InProc has a 600M memory limit, so on some virtual hosts, the resources are not sufficient to cause the user state to be lost, so we default to the ASP. NET state Service "ASP."

This article is from the "linux~dba~mba~edu" blog, make sure to keep this source http://sky9896.blog.51cto.com/2330653/1693163

Unable to issue a session state request to the session-state server