Stack Overflow
Query:
Currently I have 3 different SharePoint environments; DEV,UAT and PROD. These environments have same server topology and same software installations.
I populate some SharePoint lists and a SQL Server database with PowerShell. PowerShell script works fine under DEV and UAT. It also works well on PROD. However, whenever I run the script in the PROD, SharePoint site starts displaying;
Sorry, something went wrong
The context has expired and can no longer be used. (Exception from HRESULT:X80090317)
There is no such problem neither on DEV nor UAT. I assume that some configurations are different on the PROD but I couldn't find which ones they are.
What is the problem here? How can I avoid this?
Solutions :
Similar to the above answer but check if the web application time zone and the server time zone are identical, you could refer this article: Time zone issue
Time Zone Issue :
How to fix SharePoint 2013 Web Application error “The context has expired and can no longer be used”
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: 0x80090317)
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!
References:
1. How to fix SharePoint 2013 Web Application error “The context has expired and can no longer be used”
No comments:
Post a Comment