Server Error in '/' Application

比眉伴天荒 2022-01-11 08:19 161阅读 0赞

Many articles are discussing about advantages of using Session StateServer or SQLServer over InProc Mode. One basic reason why I choose StateServer Mode is when your website is running on Third Party Hosting than you will notice that Session Timeout can occur anytime depends on load of traffic on your server.

If your website has large number of visitors and session timeout can cause problem, It is better to change Session Mode Session="InProc" to Session="StateServer".

Main Advantage of Session StateServer (Best to choose while hosting on third party server)

1. Session is persistent and reliable.

2. Avoid Session Timeout due to Memory shortage on server (IIS Setting).

Main Disadvantage

1. Poor Performance compare to Session="InProc"

2. Session\_End Event would not fire.

Now lets understand

**Steps for changing Session InProc Mode to Session StateServer Mode.**

**Step 1:** **Start Asp.net State Servcie**

1. Go to Control Panel > Administrative Tools > Services

2. Select Asp.Net State Service.

3. Right Click on Asp.net State Service and choose start from popup menu.

**If you forget to Start Service you will receive following error.**

# Server Error in '/' Application. #

## *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.* ##

**Description:** An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.  
  
**Exception Details:** System.Web.HttpException: 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.

**Step 2:**   **Change Session Mode in Web.Config File**

<sessionState **mode="StateServer"**

stateConnectionString="tcpip=127.0.0.1:42424"

cookieless="false"

timeout="120"/>

Note: You can adjust timeout minutes based on your requirement. Let the tcpip server to be localhost i.e. 127.0.0.1. Most webhosting company uses these settings unless you have different IP for StateServer and You are not required to change Port Number.

**Step 3: Make All Object Serializable**

You should make all object in your website to serializable.

Note: To take advantage of Session StateServer or SQLServer or Custom Mode, object needs to be serialized.

Example: If your project contains class files for creating DAL (Data Access Layer), you should append Serializable to every class definition in order to make class Serializable.

[Understanding Serialization in C\#][Understanding Serialization in C]

[Serializable]

Class Department

long \_deptId;

string \_deptName;

public long DeptId

get \{ return \_deptId; \}

set \{ \_deptId = value; \}

public string DeptName

get \{ return \_deptName; \}

set \{ \_deptName = value; \}

**IMPORTANT While doing Serialization**

Remember SQLConnection cannot be serialized.

You might receive following error if you don't handle this situation.

## *Unable to serialize the session state. In 'StateServer' and 'SQLServer' mode, ASP.NET will serialize the session state objects, and as a result non-serializable objects or MarshalByRef objects are not permitted. The same restriction applies if similar serialization is done by the custom session state store in 'Custom' mode.* ##

**So to handle this situation you need to do following thing.**

1. Mark SQLConnection Object as NonSerialized

**\[NonSerialized\]** protected SqlConnection \_mainConnection;

2. Mark your Class as Serializable and derive from IDeserializationCallback