– Unable to make the session state request to the session state server

The Question :

124 people think this question is useful

Our site is currently having this problem. Basically it only happen when we click some particular links where it will pop-up a new window.
This is the error message we receive :

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 ‘’ as the server name.

target site :
Void MakeRequest(StateProtocolVerb, System.String, StateProtocolExclusive, Int32, Int32, Int32, Byte[], Int32, Int32, SessionNDMakeRequestResults ByRef)

this is the webconfig that contain sessionstate tag :

<sessionState mode="StateServer" timeout="45" />

I have check the ASP.NET State Service, and it is currently started and set to automatic

I have set the registry stated in the error message to 1, but still not working.

The Question Comments :

The Answer 1

314 people think this answer is useful
  1. Start–> Administrative Tools –> Services
  2. Right-click on the ASP.NET State Service and click “start”

Additionally you could set the service to automatic so that it will work after a reboot

The Answer 2

26 people think this answer is useful

If you need to change HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\aspnet_state\Parameters\AllowRemoteConnection to 1, remember to restart the state service after you change the parameter.

The Answer 3

9 people think this answer is useful

Check that:


is correct. Also please check that default port (42424) is available and your system does not have a firewall that is blocking the port on your system

The Answer 4

6 people think this answer is useful

Type Services.msc in run panel of windows run window. It will list all the windows services in our system. Now we need to start Asp .net State service as show in the image.enter image description here

Your issue will get resolved.

The Answer 5

5 people think this answer is useful

One of my clients was facing the same issue. Following steps are taken to fix this.

 (1) Open Run. 

 (2) Type Services.msc

 (3) Select ASP.NET State Service

 (4) Right Click and Start it.

The Answer 6

2 people think this answer is useful

Another thing to check is whether you have Windows Firewall enabled, since that might be blocking port 42424.

The Answer 7

2 people think this answer is useful

I’ve found that some developers will for some reason define the server’s private IP outside of IIS in an unexpected location, like a nonstandard config file (i.e. not web.config) or a text file. This can cause internal operation to fail even when the service is started, ports aren’t being blocked, reg keys are correct, etc.

Kaseya, in particular, places a file called serveripinternal.txt in the root IIS directory of the VSA server. I’ve seen the text of your error when somebody running their own Kaseya instance changed the server’s internal IP. The server will be reachable, IIS will respond, and the login page will come up – but login will fail with the cited message.

The Answer 8

1 people think this answer is useful

I’ve had the same issue when some ASP.NET installation was corrupted. In that case they suggest running aspnet_regiis -i -enable

The Answer 9

0 people think this answer is useful

I recently ran into this issue and none of the solutions proposed fixed it. The issue turned out to be an excessive use of datasets stored in the session. There was a flaw in the code that results in the session size to increase 10x.

There is an article on the msdn blog that also talks about this.

I used a function to write custom trace messages to measure the size of the session data on the live site.

The Answer 10

0 people think this answer is useful

Not the best answer, but it’s an option anyway:

Comment the given line in the web.config.

Add a Comment