You open your SharePoint site, expecting to get work done, but instead, all you see is a blank screen with “SharePoint Something Went Wrong error.” I know how frustrating that moment feels because recently, my team also dealt with this issue.
That time, I figured out, this error will appear when you’re opening a page, accessing a document library, or running an admin command, after the SharePoint tenant to tenant migration. Moreover, the worst part is, SharePoint doesn’t explain what went wrong. This means you have to find out manually.
Don’t panic, because I’m here to provide you with the details of this issue, i.e. why it occurs, and how to resolve it in minutes via step-by-step troubleshooting.
Without wasting any time, let’s explore:
What does SharePoint Something Went Wrong Mean?
The “SharePoint Sorry Something Went Wrong” message is a generic error. It’s SharePoint’s way of saying, “I encountered a problem, but I’m not going to tell you much about it.”
This can occur in various scenarios:
- When trying to open a list or library
- While accessing a SharePoint page or site
- During PowerShell commands or migration
- Create a SharePoint folder or files
- When creating or editing site collections
- Even when signing in with Microsoft 365 credentials
So, it’s the default response when something breaks, SharePoint Online permissions, or configuration.
Common Causes of the SharePoint Sorry Something Went Wrong Error
According to a recent community discussion. i.e. Microsoft TechNet, Reddit, and SharePoint forums, the causes can be grouped into a few main categories:
#1. Permission Issues
If you don’t have the right access to a list, library, or site component, SharePoint can throw this SharePoint something went wrong error instead of a clear Access Denied message. Try accessing the site using a Global Admin or Site Collection Admin account.
If you don’t know, then learn how to check the Site Collection Administrator in SharePoint Online first. If that works, review and reassign permissions for the affected users or groups.
#2. Corrupted Web Part or Page Component
Sometimes, adding or modifying a web part, especially custom or embedded ones, can corrupt a page layout and trigger this and the SharePoint HTTP 404 Not Found error. To fix this, open the page in Edit Mode, remove the problematic web part, and re-add it.
If you can’t access the page, use the?Contents=1 query to open the Web Part Maintenance page:
https://mackjohntenant.sharepoint.com/sites/mackjohnsite/SitePages/Home.aspx?contents=1
#3. Browser Cache or Authentication Conflict
Modern SharePoint heavily relies on cached authentication tokens. If those expire or conflict, you will see the “SharePoint Something Went Wrong” screen when logging in.
Try these quick steps to troubleshoot:
- Clear your browser cache and cookies.
- Sign out of Microsoft 365 completely.
- Reopen SharePoint in InPrivate/Incognito Mode.
- Re-authenticate with the correct account.
This simple fix has worked for me many times.
#4. Corrupted Workflow or List Schema
If you recently edited a list or workflow and suddenly this error appears, it’s likely a schema mismatch issue. You can address it:
- Check the workflow history (if accessible).
- Recreate or republish the workflow in Power Automate or SharePoint Designer.
- For lists, try exporting the list schema and verifying columns & data types.
Advanced Fixes – For Admins Only
If none of the above work, here’s what you can try next as an admin:
#1. Use PowerShell to Check Site Health
To identify quota, storage, or lock issues, run:
Connect-SPOService -Url https://mackjohntenant-admin.sharepoint.com
Get-SPOSite -Detailed
#2. Enable Correlation IDs
SharePoint Something Went Wrong instance with a Correlation ID. You’ll usually see it on the error screen.
You can use that ID to trace the exact failure in ULS logs (for on-premises) or Microsoft Support (for Online):
Correlation ID: 1a2b3c4d-1234-5678-9abc-def123456789
Search this in your ULS viewer to address the faulty process.
#3. Restore Page Versions
If you suspect a page change caused it, go to Site Pages > Version History, and restore the last working version.
How to Prevent “SharePoint Something Went Wrong” After Migrations?
Many post-migration errors can be avoided with the right approach:
- Always validate permissions and web parts after migration.
- Test pages, lists, and libraries before handing over to users.
- Use a dedicated SharePoint Online Migration Tool to ensure all content, metadata, permissions, and web parts are migrated intact.
Quick Checklist to Fix “SharePoint Sorry Something Went Wrong”
Here’s my go-to checklist to quickly resolve this issue:
- Check permissions
- Try Incognito mode
- Remove or fix web parts
- Review recent changes (themes, scripts, workflows)
- Test with admin access
- Check Microsoft 365 Service Health
- Trace Correlation ID if needed
When to Contact Microsoft Support?
If you’ve tried everything and the issue persists, then don’t waste time; open a ticket with Microsoft 365 Support. Provide the following details for faster resolution:
- Correlation ID
- URL of the affected site/page
- Timestamp
- Screenshot of the error
Author’s Verdict
The “SharePoint Something Went Wrong” error may look vague, but once you know where to look and how to fix it, you will easily troubleshoot it in minutes. However, we can’t resolve this permanently, so backup SharePoint to local storage to ensure data continuity if this type of error persists.
It is suggested to bookmark this guide as it serves as a comprehensive reference for troubleshooting the “SharePoint Sorry Something Went Wrong” error.