These are few of the configuration settings we need to consider while deploying our custom web application within ISV folder of CRM.
If we want the page to run under the context of the logged in user than we need to enable impersonation.
<authentication mode="Windows"/><identity impersonate="true"/>
If we are using view state or session state we need to enable them as well.
<pages enableSessionState="true" enableViewState="true" >
CRM 4 implements http modules for multi-tenancy support. Here we need to remove these modules from being called for our custom web application.
<httpModules><remove name ="CrmAuthentication"/><remove name ="MapOrg"/></httpModules>Bye..
Discover more from Nishant Rana's Weblog
Subscribe to get the latest posts sent to your email.

Hi Nishant,
I am not managing to get session state working in my ISV page, this error is just not going away.
“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.
”
The page authenticates fine from context, dlls are in Crm’s BIN folder.
i have EnableSessionState=”True” in the aspx page directive.
i normally deploy with no wen.config file, but now i added one specially:
still no luck.
any ideas?
LikeLike
sorry, the post was edited.
i added a web config specially for
pages enableSessionState=”true” enableViewState=”true”
LikeLike
C3-00 Free Net Setting
LikeLike
Rana
LikeLike