Lydia Bronze

How to fix SharePoint 2013 Web Application error “The context has expired and can no longer be used”

October 22nd, 2012 | Author: | Filed under: CloudShare, SharePoint | Tags: , , , ,

I came across this odd error a couple of times in the past few weeks, so I wrote a quick guide that might help you get rid of it.

If you see this error after opening your SharePoint 2013 site, there is a lack of synchronization between Date and Time settings in your SharePoint 2013 Server and your SharePoint web application.

Sorry, something went wrong. The context has expired and can no longer be used. (Exception from HRESULT: 0×80090317)

Here is how you fix it!

  • Open Central Administration -> Application Management.

  • Locate the relevant Web Application and click on 
  • Web Application General Setting window will open up, notice that the Default Time Zone is missing.


  • Open Date and Time options on your server and check which time zone is configured. Configure the same time zone in Web Application General Setting.

  • Perform IIS Reset and open your SharePoint 2013 site again.

Hooray! SharePoint site works again!

About the author:
Lydia Bronze ( @LydiBee ) , Cloud Content Architect at CloudShare, is an experienced technologist with a diverse and deep background in infrastructure technologies, information security and technical training. Lydia's proven ability to architect, implement and provide solutions for advanced infrastructures using Microsoft and Open Source technologies makes her an invaluable asset to the team. She brings technical experience from a variety of industries, including the Defense and Finance sectors. In addition, Lydia has extensive SharePoint experience and has implemented corporate environments as well as custom SharePoint solutions for organizations of all sizes. Lydia is continuously seeking new challenges that will allow her to utilize her technical abilities.

  • Raja

    Thanks a lot for the fix!

  • Matz

    Had the same issue, but the time zones already matched. An IIS Reset fixed it for me.

  • Rauno Mägi

    Simple IISRESET will do the job. Time Zone stuff doesn’t help.

  • Ajay Khanna

    IISREset will fix it.
    Other way to do this is
    From Central Admin- Select the web application and Select –> Web Application General Settings –> Navigate to ‘Web page Security validation’, change or disable the timeout field.

  • David

    Thanks! Info from this article was the solution for me. IIs-reset was´nt enough…

  • sp_junior

    thanks Lydia, you’re beautiful and clever!

  • Denis

    Thank you so much.

  • Babmoa

    Thanks this helped me by following the steps

  • Papageno Sweden

    Don’t really care if you need the time zone stuff or not. This saved my day, my nerves and my night sleep! Thanks a lot for taking the time to write this simple fix down!