Loading...

Archives

INTERNAL: “Session state can only be used when enableSessionState …”

INTERNAL: “Session state can only be used when enableSessionState …”

After installing QuickApps, we can no longer browse the SharePoint sites and receive a Correlation ID error. Checking the ID in the ULS logs, the following error is thrown:

"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. "

DevExpress UI Tool errors

DevExpress UI Tool errors

: Exception information: Exception type: ConfigurationErrorsException Exception message: Could not load file or assembly ‘DevExpress.Web.v9.3, Version=9.3.3.0, Culture=neutral, PublicKeyToken=b88d1754d700e49a’ or one of its dependencies. The system cannot find the file specified. Is DevExpress used inside Quick-apps for SharePoint?

“The error code is 2203” when uninstalling

“The error code is 2203” when uninstalling

When trying to uninstall QuickApps, either through the msi package or Add/Remove Programs, the following error is thrown:

"The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2203."

Missing Management Pages after WFE installation

Missing Management Pages after WFE installation

After installing QuickApps on the WFE, the installation and solution deployment are successful and all of the web parts work but there are no Management Pages in CA to upload the license file. Central Administration is installed on the App Server, not the WFE.

When trying to install QuickApps, getting “error code 2869”

When trying to install QuickApps, getting “error code 2869”

When trying to install v.6.2 on SP2013, an installer “error code 2869” message is being thrown. We have verified that UAC is turned off and that the setup.msi is being ‘Run as Administrator’, but the error is still thrown.

Suspect install issues

Suspect install issues

The product is not performing as expected.  Suspected install issues.