Into the company began to contact the project to do the report, the original system used is Crystal report, but the Crystal Report display aspects of beauty is not good to need customers to beautify a bit. Custom reports and Crystal Reports have not been contacted before, they first learned the two reports, and later felt that the custom report design is more flexible so the custom report was selected. When the development is complete, the browsing test in the start environment does not have an issue with the ASP. NET session has expired, but when deployed to the IIS testers to test the situation:
I contact IIS is not many, and in the development environment Test no problem signed to IIS there is a problem at that time felt a bit big, so the Internet to find the next information but this is not a lot of information and many are similar and their methods have been tried or not solve the problem.
Attached to the Internet some of the methods found are not applicable:
1. <sessionstate mode= "InProc" cookieless= "true" timeout= "> </sessionState>" in the Web. config file
Change to <sessionstate mode= "InProc" cookieless= "false" timeout= "> </sessionState>"
2. Page Join
protected override void OnPreRender (EventArgs e)
{
Response.appendheader ("P3P", "cp=\" CAO PSA our\ "");
Base. OnPreRender (e);
}
Wait, here is not one by one cases, in order to solve this problem for a day or two to find a solution can not find, I am almost disoriented. Later even want to abandon the custom report to return to the Crystal Report. One time when discussing another problem with your colleague in the deployment of IIS, you stumbled upon this:
Start session state The default is "in Process (I)", think whether the problem is here, and then change him to this. Then browsing does not show that the ASP. NET session has expired. The problem is solved.