Last post Sep 15, 2012 04:29 AM by Ash Harris
Jun 01, 2012 01:34 PM|hsnowdenjr|LINK
Classic case of everything runs perfect in the development environment, but breaks on production environment. We’re a Window desktop application design house, and new to ASP.Net and IIS.
We’ve built an ASP.Net web site in VS 2010 pro and deployed it to an MS Server 2008 R8 using the VS Web Set Up Project. We’ve converted the web site to an application in IIS. Our application pool is set to ASP.Net 4.0 Classic though not sure why we can’t
run it under ASP.Net 4.0 default pool.
The issue we’re having is our session variables are not passing from page to page in the production environment.
Example: User selects a location. The location has a unique id we pass to the next page. The next page will query a database and display a report based on the location Id.
Code from selection page:
Session("SiteType") = ID
We’re tried multiple settings in IIS under Session State (inPro and SQLState) with no results. We’re in 3 day of troubleshooting. I’ve read about every Google search I’ve found before posting this. I’m hoping it’s an IIS setting. Looking for suggestions
on what might need to be tweaked.
Jun 01, 2012 02:00 PM|viperx1967dag|LINK
There are several things you can try.
1. Change your application pool to integrated I was having problems with session state when running in classic mode.
2. Make sure the server Session state is set properly should be In Process just make sure its not set to Not Enabled.
3. In your web.config file make sure you have your sessionState mode option set to InProc and that your session timout is default (20 minutes)
4. Check that your anti-virus software is not scanning your .asax and .config files.
Check this article it might give you some things to check
Hopefully one of these things will solve your problem.
Jun 01, 2012 03:01 PM|hsnowdenjr|LINK
Thanks for the response.
2 & 3. Those were the original Session State settings.
4. Looking into the antivirus software
Tech Note: I have shifted the state management to “out of process” by using SQLState. ASP State manager is running. No success.
I’m thinking the key is in the application pool. I am not sure why it will not run under the default pool with integrated support.
Jun 05, 2012 09:46 AM|hsnowdenjr|LINK
Problem solved. it appeared to be a code error and not a Session state setting. Thanks for the assist.
Sep 15, 2012 04:29 AM|Ash Harris|LINK
I am still having this problem.. How did u solve tat friend.. Help me..