Dear All,
Today, I have faced an issue when try to use session in my custom webpart and it destroyed the whole website.
After checking the log file i found the issue is related to ASP.net 2.0 session is not enable for the web Application
I have spend 5 hours to find the proper solution here are the steps i hope it will work
1) Please make sure in your services ASP.NET Session State is enable. If it's not started make it automatic and start it.
2) Run the following command on your SharePoint Powershell by running as Administrator
3) The Most important point that you need to do in SQL Server
Strange? Not so. According to the permissions and security settings article, your main account only needs dbcreator and securityadmin rights. But, when you enable the session state service, a job has to be created under the SQL Agent Service, which you need sysadmin rights for. So if your account only has dbcreator and securityadmin at runtime, kindly ask the SQL team to give sysadmin for just a sec.
If you already created the service application with the wrong SQL permissions, you can always manually create a job under the SQL Agent Service to execute the “DeleteExpiredSessions job”.
Today, I have faced an issue when try to use session in my custom webpart and it destroyed the whole website.
After checking the log file i found the issue is related to ASP.net 2.0 session is not enable for the web Application
I have spend 5 hours to find the proper solution here are the steps i hope it will work
1) Please make sure in your services ASP.NET Session State is enable. If it's not started make it automatic and start it.
2) Run the following command on your SharePoint Powershell by running as Administrator
3) The Most important point that you need to do in SQL Server
Strange? Not so. According to the permissions and security settings article, your main account only needs dbcreator and securityadmin rights. But, when you enable the session state service, a job has to be created under the SQL Agent Service, which you need sysadmin rights for. So if your account only has dbcreator and securityadmin at runtime, kindly ask the SQL team to give sysadmin for just a sec.
If you already created the service application with the wrong SQL permissions, you can always manually create a job under the SQL Agent Service to execute the “DeleteExpiredSessions job”.
Make sure the above permission will set on the session database which you will find under your sql this session database is not the content database
Apply the permission on the SQL Agent Service and Assign this user with your Session database
I hope it save your time
Regards
Rashid Imran Bilgrami
I simply couldn’t depart your site before suggesting that I really enjoyed the usual information an individual supply in your visitors? Is going to be again steadily to check out new posts.
ReplyDeleteSharepoint Training in Chennai