Trying to install - Session State error


https://forum.kartris.com/Topic1928.aspx
Print Topic | Close Window

By jgkartrisuser - Tue 23 Apr 2013
I am trying to install Kartris as a demo to evaluate it. I am using IIS 7.5 on Windows Server 2008 R2, 64-bit. I am following the User's guide (here) for a manual install (section 2.4.2.2). I want to let the setup routine set up the database, so I have skipped step 5. When point my browser to myhost/Kartris, I get the "Oops! An error occured" page. Windows Event Viewer shows the following error:

Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 4/23/2013 10:27:55 AM
Event time (UTC): 4/23/2013 3:27:55 PM
Event ID: 325d1064749b4520900649ad744dd7f2
Event sequence: 7
Event occurrence: 3
Event detail code: 0

Application information:
Application domain: /LM/W3SVC/2/ROOT/Kartris-1-130112024013936193
Trust level: Full
Application Virtual Path: /Kartris
Application Path: C:\inetpub\PDshop\Kartris\
Machine name: ISERVER

Process information:
Process ID: 2792
Process name: w3wp.exe
Account name: IIS APPPOOL\PDshop

Exception information:
Exception type: HttpException
Exception message: Session state can only be used when enableSessionState is set to true, either in a configuration file or in the Page directive. Please also make sure that System.Web.SessionStateModule or a custom session state module is included in the <configuration>\<system.web>\<httpModules> section in the application configuration.
at System.Web.UI.Page.get_Session()
at Admin_Install.InitializeCulture()
at ASP.admin_install_aspx.__BuildControlTree(admin_install_aspx __ctrl)
at ASP.admin_install_aspx.FrameworkInitialize()
at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequest(HttpContext context)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)



Request information:
Request URL: http://10.0.0.87/Kartris/Admin/Install.aspx
Request path: /Kartris/Admin/Install.aspx
User host address: 10.0.11.145
User:
Is authenticated: False
Authentication Type:
Thread account name: IIS APPPOOL\PDshop

Thread information:
Thread ID: 10
Thread account name: IIS APPPOOL\PDshop
Is impersonating: False
Stack trace: at System.Web.UI.Page.get_Session()
at Admin_Install.InitializeCulture()
at ASP.admin_install_aspx.__BuildControlTree(admin_install_aspx __ctrl)
at ASP.admin_install_aspx.FrameworkInitialize()
at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequest(HttpContext context)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

In IIS Manager, the System.Web.SessionState.SessionStateModule is listed in the Modules feature at all levels. However, a case-insensitive search (with grepWin) for the text "sessionstate" does not find anything in the .aspx files or .config files for Kartris. Looking at Microsoft's docs for the sessionState Element shows quite a few options. Does anyone know what I need to do to resolve this error?
By Mart - Wed 24 Apr 2013
I found some relevant entries here...

http://stackoverflow.com/questions/2757403/error-using-session-in-iis-7

Is the server a new clean install? Or might it have settings changed?

Check that the web you've set up is using the correct version of .net

Lastly, let us know if you do fix it!
By jgkartrisuser - Wed 24 Apr 2013
I had seen the stackexchange post refrenced, but that didn't help.

I did a fresh install of IIS, and it worked, so some setting somewhere in IIS must have been changed from the default. I didn't spend any more time trying to figure it out.
By Mart - Wed 24 Apr 2013
Great you got it fixed... Thanks for updating us on it