Share this article

Improve this guide

Sorry, something went wrong error in SharePoint 2013

10 min. read

Updated onOctober 4, 2023

updated onOctober 4, 2023

Share this article

Improve this guide

Read our disclosure page to find out how can you help Windows Report sustain the editorial teamRead more

Many of use use Office tools frequently, but sometimes issues with Office tools can appear on Windows 10. Users reportedSorry, something went wrongerror messageinSharePoint2013, and today we’re going to show you how to fix it.

How can I fix “Sorry, something went wrong” error in SharePoint 2013?

Sorry, something went wrong in SharePoint 2013

Solution 1 – Change the Require content approval settings

According to users,Sorry, something went wrongerror messagecan appear due to your Content approval settings. This error appears when you try to saveSharePointsite as a template, and in order to fix this problem, you need to follow these steps:

Solution 2 – Publish display templates

Users reported that this error appears if your display templates aren’t published, so be sure to publish them.

According to users, uploaded display templates won’t work for non-administrators, and they’ll getSorry, something went wrongerror message.

To fix this problem, make sure that display templates are published.

Solution 3 – Delete the recurring calendar appointments

According to users, this error can appear if you import calendars fromSharePoint2003 toSharePoint2013.

It seems thatSharePoint2013 has issues with recurring appointments, and in order to fix this issue it’s necessary that you delete those appointments.

If you don’t want to permanently delete your appointments, you can restore them by going to theSite Contents > Recycle Binand choosing the Restore option. After restoring the appointments, the issue should be permanently fixed.

SharePoint online calendar not showing events? Don’t worry, we’ve got you covered.

Solution 4 – Make sure that the time zone is configured

Sometimes this error appears inSharePoint2013 if your time zone isn’t properly configured. To check time zone settings inSharePoint, do the following:

If the Default Time Zone setting is missing, you need to check if the correct time zone is set on your PC. To do that, follow these steps:

Alternatively, you can also check your time zone by following these steps:

Now you just need to go back to Web Application General Settings and set the time zone of yourserver. Performiisresetand the problem should be permanently fixed.

Windows 10 won’t let you change your time zone? Check out this guide to solve the problem easily.

Solution 5 – Configure the Root site collection

According to users, this issue can sometimes occur if you don’t have the Root site collection configured.

If you create your collection in /Sites/ instead of Root you might experience this error, therefore we suggest to create a Root site collection and check if that fixes this error.

Solution 6 – Make sure that your domain account has access to SPDataAccess role

Improper configuration can sometimes causeSorry, something went wrongerror to appear. In order to avoid this problem inSharePoint2013 while using Access Services, you need to grant certain permissions to your domain.

After granting your account access to theSPDataAccessrole inSharePointconfiguration database (inSQL Server) the issue will be completely resolved.

Solution 7 – Restart the SPTimer service

Users reported that this error appears while adding apps toSharePoint. This error can be problematic, but it can be fixed simply by restarting theSPTimerservice (OWSTIMER.EXE).

After restarting the service, the error was completely fixed. In order to avoid these errors in the future, remember to restart SPTimer service every time you make a major configuration change inSharePoint2013.

Solution 8 – Check App ManagementService

This error can appear if the App ManagementServiceisn’t installed, but you can fix it by following these steps:

If you performed all these steps correctly, the error should be completely fixed.

Sorry, something went wrong in SharePoint 2013 search

Solution 1 – Delete the service application and create a new one

If you’re getting this error while using the search application, try deleting the service application. After you delete it, create it again and the problem with search should be fixed.

After creating a new service application, be sure that it’s set as a default for your application.

Solution 2 – Change the access rights

You can fix this problem by adding Everyone to the Members group. Bear in mind that you need to change the rights toRead Only. This isn’t the best solution, and it’s probably not the safest, so use it at your own risk.

Solution 3 – Be sure that Search Service Application is working

Sometimes Search Service Application can stop working and that can causeSorry, something went wrongerror to appear. To fix this problem, do the following:

Solution 4 – Check if theSharePointSearch Host Controller is running

SharePoint2013 relies on certain services in order to run properly, and ifSharePointSearch Host Controller isn’t running, you might getSorry, something went wrongerror messagewhile using search inSharePoint2013.

To fix this error, check ifSharePointSearch Host Controller is running. To do that, follow these steps:

Sorry, something went wrong in SharePoint 2013 workflow

Solution 1 – Create a new workflow with a different name

Users reported thatSorry, something went wrongerror messagecan be caused by deleting and recreating your workflow. To fix this error you need to create a new workflow but use a different name for it.

After creating a new workflow with a different name, the error should be completely fixed.

Solution 2 – Use flushdns command

This error can occur due to your DNS, but you can easily fix it by flushing your DNS. To do that, follow these simple steps:

After running the flushdns command, you might want to recycle Workflow andServiceBus services and try to publish workflow again.

If you’re having trouble accessing Command Prompt as an admin, then you better take a closer look atthis guide.

If you can’t flush the DNS Resolver Cache in Windows 10, follow the steps in this handy guide to fix the issue.

Solution 3 – Assign db_owner permissions to your user account

If you’re getting this error while using workflow UI, you might want to change your permissions. To do that, go to your databases and assigndb_ownerpermissions to your workflow service account in your database.

Sorry, something went wrong in SharePoint 2013 site collection

Solution – Delete the web application

Users reported this error while creating a site collection inSharePoint2013, and to fix this problem you need to delete the web application you created. After that, follow these steps:

After doing this you should be able to create web applications and site collections without any errors.

Sorry, something went wrongSharePoint2013 error can be caused by many different things, and it might be hard to fix sometimes, but we hope that you managed to fix it by using one of our solutions.

If you have any other suggestions or questions, don’t hesitate to leave them in the comments section below.

Sorry, something went wrong error in SharePoint 2013#

How can I fix “Sorry, something went wrong” error in SharePoint 2013?#

Sorry, something went wrong in SharePoint 2013#

Sorry, something went wrong in SharePoint 2013 search#

Sorry, something went wrong in SharePoint 2013 workflow#

Sorry, something went wrong in SharePoint 2013 site collection#