Solved

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

Posted on 2013-05-20
3
2,760 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 learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.

Question has a verified solution.

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

Pimping Sharepoint 2007 without Server-Side Code Part 1 One of my biggest frustrations with Sharepoint 2007 in the corporate world is that while good-intentioned managers lock down the more interesting capabilities of Sharepoint programming in…
Microsoft has released remote PowerShell capabilities to all commercial Office 365 customers. So you can be controlled via PowerShell and not from the Office 365 admin center Download Windows PowerShell Module for Lync Online http://www.micros…
In this video we outline the Physical Segments view of NetCrunch network monitor. By following this brief how-to video, you will be able to learn how NetCrunch visualizes your network, how granular is the information collected, as well as where to f…
Visualize your data even better in Access queries. Given a date and a value, this lesson shows how to compare that value with the previous value, calculate the difference, and display a circle if the value is the same, an up triangle if it increased…

623 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