-
Title
The following error occurs: "Session state can only be used when enableSessionState is set to true -
Description
The following error is displayed when editing a web part.
The following error occurs: 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 \\ section in the application configuration.
-
Cause
QWP relies on sessions to provide additional functionality. Quest Web Parts pass data between web parts using sessions.
Unfortunately, it's not possible to use Quest Web Parts with disabled sessions. It's is a system requirement for the tool. -
Resolution
Please run the "Quest Web Parts for SharePoint Configuration Editor" Start | All programs | Quest Software | Quest WebParts for SharePoint | Configuration Editor and fix all of the red "!". You would need to have all green check marks when you open the web.config file for the Web Front End (WFE) that you are trying to load. If you have multiple WFEs you would need to change the web.config from our Quest Web Parts for SharePoint Configuration Editor on all WFEs. Please take a backup though our config editor creates a backup.
-
Additional Information
Although ASP.NET session state is disabled by default in SharePoint 2010, it may be required by custom solutions and web parts that are built on SharePoint 2010 framework.
QWP relies on SQL Server to persist information per user session to provide advanced functionalities such as cross-page communications of web parts. For example, you use qListForm to create a new Project, and once it is created, you are redirected to a new page containing a qSelector showing a list of projects, you want it to be selected automatically by the qSelector, which may be used to filter another web part such as qListView.
Making use of session state enables QWP to provide functionalities not available in OOB SharePoint web parts/solutions, which allows the user to build powerful line-of-business applications using web parts that work seamlessly to server a particular business need
What do you recommend when an application requires both the OOB setting due to the needs of other components that fail when session state is enabled, but which also want to use Quest?
We suggest to maintain web pages using Quest Web Parts in a separate web application so that you can configure the session state targeting the settings needed by Quest Web Parts.
In one case we had to run "enable-SPsessionStateService -defaultprovision" from SP management Shell