Last post Sep 09, 2013 01:54 AM by ElChe77
Sep 04, 2013 04:43 AM|ElChe77|LINK
I've also asked this
question on stackoverflow.com
We've migrated our webapplication from .net runtime 2 (v 3.5) to .net runtime 4 (v 4.5) and I have a question for deployment to our production servers.
Our sessionstate server is a "stateserver" that all our webservers use in common, and runs aspnetsession from framework 2 on a separate server.
When we deploy and change the application pool to .net 4 to one of our webservers in test, it seems that the session expires or is dropped somehow as we're redirected to the logon page of our application.
Is there any way of deploying our new version of the app (while also upgrading the app pool) without our users losing session in the process? Are the sessioncookie created by application pools runnning in .net 2 not compatible with .net 4? I cannot see anything
about this in the breaking changes whitepaper
In advance, thank you for any pointers
Sep 08, 2013 02:49 AM|MSDN_ice|LINK
According to your description, I see that you are suffering with the state server session expires when upgrade the .net iframework.
For this issue, i suggest you notice below points.
# Be sure the ASP.NET state service is running on the server.
# Have the same encryption keys specified in the machineKey element of your Web configuration for all applications that are part of the Web farm.
How to use state server session
Similar issue with solution.
Hope this helps, thanks.
Sep 09, 2013 01:54 AM|ElChe77|LINK
Hi, this is not very helpful.
We're of course running the service, and are well aware of machinekeys etc.