Solved

Error: The context has expired and can no longer be used. (Exception from HRESULT: 0x80090317)

Posted on 2013-05-20
3
2,704 Views
Last Modified: 2013-05-28
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.
0
Comment
Question by:CBPOWER
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 3

Expert Comment

by:ajmehta
ID: 39182164
We also get that and after much research and managed services intervention it was determined that it's a low priority nuisance and not really a problem.

basically, nobody knew the answer so we left it alone.  I hope you can find the solution though.
0
 

Accepted Solution

by:
CBPOWER earned 0 total points
ID: 39185479
It seems it all goes back to updates that did not install correctly.  Once I forced the updates to install all started working.
0
 

Author Closing Comment

by:CBPOWER
ID: 39197447
It seems like nothing else worked but now that the updates are installed everything is working right.
0

Featured Post

Free eBook: Backup on AWS

Everything you need to know about backup and disaster recovery with AWS, for FREE!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Back in July, I blogged about how Microsoft's new server pricing model, combined with the end of the Small Business Server package, would result in significant cost increases for many small businesses (see SBS End of Life: Microsoft Punishes Small B…
In case you ever have to remove a faulty web part from a page , add the following to the end of the page url ?contents=1
Nobody understands Phishing better than an anti-spam company. That’s why we are providing Phishing Awareness Training to our customers. According to a report by Verizon, only 3% of targeted users report malicious emails to management. With compan…
I've attached the XLSM Excel spreadsheet I used in the video and also text files containing the macros used below. https://filedb.experts-exchange.com/incoming/2017/03_w12/1151775/Permutations.txt https://filedb.experts-exchange.com/incoming/201…

752 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question