none
The context has expired and can no longer be used RRS feed

  • Question

  • I am running across a repeatable error when accessing a specific Site Collection. EVERY TIME the SC is loaded we receive the error 'The context has expired and can no longer be used'.

    I have already validated the SharePoint servers' time zones are all the same and match the web application(s), as well as set the 'Web page Security validation' to "Off".

    What else could I be missing? Could this have anything to do with Distributed Cache?


    - Rick

    Wednesday, April 9, 2014 2:59 PM

Answers

  • Rick,

    Do you see anything in the ULS logging.?
    Do you see the behaveiour on all the site collection or a specific site collection?

    Well security trimming and page load performance are some of the features of Distributed Cache, just make sure that the serice "Distributed Cache" is running on the Sharepoint server (Services on server)

    Satyam...

    • Marked as answer by Lindali Sunday, April 20, 2014 7:49 AM
    Wednesday, April 9, 2014 6:00 PM

All replies

  • Rick,

    Do you see anything in the ULS logging.?
    Do you see the behaveiour on all the site collection or a specific site collection?

    Well security trimming and page load performance are some of the features of Distributed Cache, just make sure that the serice "Distributed Cache" is running on the Sharepoint server (Services on server)

    Satyam...

    • Marked as answer by Lindali Sunday, April 20, 2014 7:49 AM
    Wednesday, April 9, 2014 6:00 PM
  • Hi,

    We just began to have the same error. The servers are also correctly set for the timezone (UTC) as well as the Web Applications.
    The error happens for every site collections, there isn't a specific site where I'm able to reproduce the issue.
    This is the ULS :

    05/27/2014 12:59:05.98	w3wp.exe (0x1524)	0x0780	Web Content Management	Publishing Cache	ahh6l	Verbose	CreateListItemFromUrl : Parameters url : '/sitename/SitePages/Home.aspx', enableCheckedOutItem : 'True', checkedOutByCurrentUser 'False' retVal Id = '4618889e-0e1c-4503-a7fb-70fd36e2661d'.	01ff949c-98cc-d0fb-9795-c691c2852f54
    05/27/2014 12:59:05.98	w3wp.exe (0x1524)	0x0780	Web Content Management	Publishing Cache	ahh6l	Verbose	CreateListItemFromUrl : Parameters url : '/sitename/SitePages/Home.aspx', enableCheckedOutItem : 'True', checkedOutByCurrentUser 'False' retVal Id = '4618889e-0e1c-4503-a7fb-70fd36e2661d'.	01ff949c-98cc-d0fb-9795-c691c2852f54
    05/27/2014 12:59:06.00	w3wp.exe (0x1524)	0x0780	SharePoint Foundation	Runtime	tkau	Unexpected	System.Runtime.InteropServices.COMException: The context has expired and can no longer be used. (Exception from HRESULT: 0x80090317)    at Microsoft.SharePoint.Library.SPRequestInternalClass.SetHttpParameters(String bstrHttpMethod, String bstrRequestDigest, UInt32 flags, Guid gTranLockerId, Byte[]& ppsaImpersonateUserToken, Boolean bIgnoreTimeout, String bstrUserLogin, String bstrUserKey, UInt32 ulRoleCount, String bstrRoles, Boolean bWindowsMode, String bstrAppPrincipalName, Boolean bIsHostHeaderAppPrincipal, String bstrOriginalAppPrincipalIdentifier, ApplicationPrincipalInfo& pAppUserInfo, Boolean bInvalidateCachedConfigurationProperties, Int32 lAppDomainId, ISPManagedObjectFactory pFactory, Boolean bCallstack, ISPDataCallback pCanaryCallback)     at Microsoft.SharePoint.Library.SPRequest.SetHttpParameters(String bstrHttpMethod, String bstrRequestDigest, UInt32 flags, Guid gTranLockerId, Byte[]& ppsaImpersonateUserToken, Boolean bIgnoreTimeout, String bstrUserLogin, String bstrUserKey, UInt32 ulRoleCount, String bstrRoles, Boolean bWindowsMode, String bstrAppPrincipalName, Boolean bIsHostHeaderAppPrincipal, String bstrOriginalAppPrincipalIdentifier, ApplicationPrincipalInfo& pAppUserInfo, Boolean bInvalidateCachedConfigurationProperties, Int32 lAppDomainId, ISPManagedObjectFactory pFactory, Boolean bCallstack, ISPDataCallback pCanaryCallback)	01ff949c-98cc-d0fb-9795-c691c2852f54
    


    Tuesday, May 27, 2014 1:25 PM
  • What seems to have fixed it for me was turning off the Request Management service in Central Administration - System Settings - Services on Server - Request Management - STOP.

    I'm wondering if maybe my servers have some problems with their certificates. Also, I know our servers are a few seconds off on their time but I cannot imagine that is the reason. That would be entirely too fragile for an enterprise system.

    Monday, November 3, 2014 10:25 PM