SharePoint Document Issues

Fix SharePoint Versioning Settings 'Something Went Wrong' Error

Huma Ashraf Ch Oct 22, 2026 869 views

Question details

Users are unable to configure list history because the Versioning Settings page fails to load and throws a generic error message.

How to Fix 'Something Went Wrong' Error in SharePoint Versioning Settings

Product: Microsoft SharePoint Online
Device & OS: not provided
Scenario: Attempting to open the Versioning Settings configuration page for a SharePoint Online list.
Observed behavior: Instead of loading the configuration page, SharePoint displays a 'Something went wrong' error message.

Before you start

Verify that your internet connection is stable and ensure you have Site Owner or Full Control permissions for the affected SharePoint list.

Solution 1Recommended

Check Microsoft Service Health for Known Incidents

Verify if the issue is caused by a server-side disruption, such as the known Microsoft incident SP574131.

Microsoft identified this specific behavior under SharePoint Online incident SP574131, which temporarily broke access to version history settings exclusively for SharePoint Online lists (document libraries were unaffected).

When such server-side issues occur, the fix must be deployed globally by Microsoft.

Access the Admin Center

Have your Microsoft 365 administrator log in to the Microsoft 365 Admin Center.

Navigate to Service Health

Go to 'Health' > 'Service health' to view the current status of SharePoint Online.

Review Active Incidents

Look for SP574131 or similar advisories related to list versioning. If an incident is active, you must wait for Microsoft to finish deploying the fix.

Check Microsoft Service Health for Known Incidents

Incident Status: Microsoft has already deployed a fix for incident SP574131. If you still experience this error, it may be a local browser issue or a new, unrelated outage.

Solution 2

Troubleshoot Browser and Cache Compatibility

Rule out local browser glitches or corrupted cache data that might be triggering the error page.

Solution 3

Escalate to Microsoft 365 Support

If the error persists across multiple browsers and there are no active service advisories, the issue requires a direct support ticket.

Free Microsoft Office alternative

Need a Reliable Alternative for Document Management? Try WPS Office

Dealing with server-side SharePoint errors can disrupt your workflow. If you are looking for a highly efficient, offline-capable suite for your daily document tasks, WPS Office provides a free, lightweight, and incredibly powerful alternative to Microsoft Office. Create, edit, and manage your documents seamlessly without worrying about cloud configuration errors.

1. Download the Installer: Visit the official WPS website and download the free WPS Office installer for your operating system.
2. Install WPS Office: Run the setup file and follow the on-screen prompts for a quick, lightweight installation.
3. Open Your Documents: Launch WPS Office and instantly open your existing Word, Excel, or PowerPoint files without any format conversion.

Fully compatible with Microsoft Office formats (.docx, .xlsx, .pptx) for smooth file sharing.Lightweight installation with blazing-fast performance, reducing system resource usage.Familiar tabbed user interface, ensuring zero learning curve for users switching from Microsoft Office.Built-in PDF editing tools, powerful templates, and local file management without mandatory cloud dependencies.

microsoft office alternative - wps office

Frequently Asked Questions

Did SharePoint incident SP574131 affect document libraries too?

No. According to Microsoft's service incident reports, SP574131 exclusively impacted access to the version history settings for SharePoint Online lists. Standard document libraries were not affected.

Can I still view version history on individual list items when this error occurs?

Yes, usually. The error primarily affects the main Versioning Settings configuration page. You can often still view the version history of individual items by clicking the ellipses (...) next to the list item and selecting 'Version history'.

How long does it take for a SharePoint fix to deploy?

When Microsoft resolves a service incident like SP574131, the server-side fix is rolled out globally. This can take anywhere from a few hours to a couple of days to reach all tenants worldwide.

Document & File Issues