StateServer deployment in windows server 2003

Question

We implemented the Session StateServer concept in web application. Its working fine in local pC(Windows XP).

The same build we deployed in windows server 2003.the build is not working consistently

Any one please tell us.

What does you Web.config setting look like for session? ( take a peak at this link : msdn.microsoft.com/en-us/library/ms178586.aspx ) — BigBlondeViking
<sessionState mode="StateServer" stateConnectionString="tcpip=SampleStateServer:42424" cookieless="false" timeout="20"/> We use the above setting in web.config — Stateserver
Are you trying to set the web sever to use its self as a state server, or are you pointing a web server or cluster to this server? — BigBlondeViking

BigBlondeViking BigBlondeViking · Accepted Answer · 2009-06-26T13:52:36

Try setting the tcpip=SampleStateServer:42424" to localhost:42424 or 127.0.0.1:42424

if you are turning a web server into its own session server you need to make sure that you have the service enable and running... i am trying to find some where that will help you install/enable session services...

Out-of-process Mode

Included with the .NET SDK is a Windows® NT service: ASPState. This Windows service is what ASP.NET uses for out-of-process session state management. To use this state manager, you first need to start the service. To start the service, open a command prompt and type:

net start aspstate

http://msdn.microsoft.com/en-us/library/ms972429.aspx

StateServer deployment in windows server 2003

2 Answers