4

I had a problem with this error on a site collection and a document wiki library

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

I do reset and removing cache in using The context has expired and can no longer be used. (Exception from HRESULT: 0x80090317) and this and reset IIS and SharePoint server and this error still exists.

  • You didn't mention trying the 3rd answer of your first link, which suggests reseting the cache.ini's value to 1 while the Timer Service is stopped. Did you try that? If you are about to, first take a copy of the non-modified cache-file to have it as a backup. – moe Jun 10 '17 at 9:43
  • Also, which build of SP2013 do you have running (i.e. what is the latest patch you have installed for your SharePoint)? – moe Jun 10 '17 at 9:46
  • thanks, I did that to and for a while every thing is alright but after that that error happened on wiki library and after that whole site collection ! – alireza Jun 10 '17 at 11:09
  • @moe maj:15 min:0 build:4569 Rev:1000 – alireza Jun 19 '17 at 6:51
4

I've got two options for you to try out:

The first one is to try this Ryan McIntyre's suggestion on changing the Security Service's token lifetime which should fix claim expiration. This could fit to your error description as the error appears after some time.

$sts = Get-SPSecurityTokenServiceConfig
$sts.FormsTokenLifetime = (New-TimeSpan -minutes 2)
$sts.WindowsTokenLifetime = (New-TimeSpan -minutes 2)
$sts.LogonTokenCacheExpirationWindow = (New-TimeSpan -minutes 1)
$sts.Update()
iisreset

The second suggestion would be to simply add more RAM to your SharePoint hosting server. You can try with e.g. adding 4 Gb in addition to what you currently have and evaluate the results.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.