CBPOWER
asked on
Error: The context has expired and can no longer be used. (Exception from HRESULT: 0x80090317)
Error: The context has expired and can no longer be used. (Exception from HRESULT: 0x80090317)
Error:
The context has expired and can no longer be used. (Exception from HRESULT: 0x80090317)
Reason:
1. Security context of your session may be expired.
2. You/somebody may have changed the date/time in the server.
Solution:
1. Just change/update the Date/Time in the SharePoint server.
2. Increase the Security context in SharePoint central admin. This can be done by following the below steps:
Go to central admin
Go to "Application management section"
Go to "Web Application General Settings"
Go to "Web page Security validation" section & increase the timeout field. Or, you can simply disable this option.
My servers all get their time from a GPS NPT server. I have checked all the above setting and tried disabling the Web page security validation setting for the web Application.
I have 4 other web applications all set the same way that do not have this issue. The problem seems to vary between the subsites. If I run IISRESET it will fix the problem for a while but it will come back. It may effect 1 or several sub sites. I am at a loss for how to fix this. All sites and subsites are set to Central time as well as the Web application My only question is if daylight savings time might be the issue.
Error:
The context has expired and can no longer be used. (Exception from HRESULT: 0x80090317)
Reason:
1. Security context of your session may be expired.
2. You/somebody may have changed the date/time in the server.
Solution:
1. Just change/update the Date/Time in the SharePoint server.
2. Increase the Security context in SharePoint central admin. This can be done by following the below steps:
Go to central admin
Go to "Application management section"
Go to "Web Application General Settings"
Go to "Web page Security validation" section & increase the timeout field. Or, you can simply disable this option.
My servers all get their time from a GPS NPT server. I have checked all the above setting and tried disabling the Web page security validation setting for the web Application.
I have 4 other web applications all set the same way that do not have this issue. The problem seems to vary between the subsites. If I run IISRESET it will fix the problem for a while but it will come back. It may effect 1 or several sub sites. I am at a loss for how to fix this. All sites and subsites are set to Central time as well as the Web application My only question is if daylight savings time might be the issue.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
It seems like nothing else worked but now that the updates are installed everything is working right.
basically, nobody knew the answer so we left it alone. I hope you can find the solution though.