Hello,
Two of our production servers running on windows 2012 Servers with framework 4.5.2 were unexpectedly quitted the service from today morning. We found below warning messages in Event Log. We are using State server for the session handling. All Servers have
multiple web sites and many virtual directories beneath each of them. Majorities are configured to state server and all are doing well for quite SOME MONTHS. Restart of State server doesn’t yield any impact; but done multiple times. Restarts of IIS have little
impact and served two or three requests before enter VEGETATE STATE.
Restart of entire server makes everything back to normalcy. But can trust it as same has been occurred on one of our server on 14th and 15th and we were forced to switch session to IN PROC.
Session in web.config is configured like this. State Server is in auto start mode. Any help is appreciated.
<sessionState cookieless="UseCookies" mode="StateServer" stateConnectionString="tcpip=loopback:42424" stateNetworkTimeout="60" timeout="120" />
=============================================================================================
Event code: 3009
Event message: Unable to make the session state request to the session state server. Details: last phase='Sending request to the state server', error code=0x80072749, size of outgoing data=0
Event time: 8/31/2016 8:41:11 AM
Event time (UTC): 8/31/2016 8:41:11 AM
Event ID: 01d70364db994082a59213a589666626
Event sequence: 266
Event occurrence: 133
Event detail code: 50016
Application information:
Application domain: /LM/W3SVC/6/ROOT/Main-2-131171051828682492
Trust level: Full
Application Virtual Path: /<Virtual Directory>
Application Path: <Application Path>
Machine name: <Machine Name>
Process information:
Process ID: 77988
Process name: w3wp.exe
Account name: IIS APPPOOL\<Application Pool Name>
Exception information:
Exception type: HttpException
Exception message: Unable to make the session state request to the session state server. Please ensure 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 machine, please ensure that
it accepts remote requests by checking the value of HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\aspnet_state\Parameters\AllowRemoteConnection. If the server is on the local machine, and if the before mentioned registry value does not exist or is
set to 0, then the state server connection string must use either 'localhost' or '127.0.0.1' as the server name.
Request information:
Request URL: <Page URL>
Request path: <Actual Page>
User host address: <Request IP>
User:
Is authenticated: False
Authentication Type:
Thread account name: IIS APPPOOL\<Application Pool Name>
Thread information:
Thread ID: 65
Thread account name: IIS APPPOOL\<Application Pool Name>
Is impersonating: False
Stack trace: