Sharepoint 2013 Upload Master Page Something Went Wrong

Sorry, something went wrong error in SharePoint 2013

Milan has been enthusiastic about PCs ever since his childhood days, and this led him to take interest in all PC-related technologies. Before joining WindowsReport, he worked every bit a front-cease web developer. Read more

Updated: Sep x, 2019

Posted: June 2018

XINSTALL BY CLICKING THE DOWNLOAD FILE

Many of utilise use Office tools oftentimes, but sometimes issues with Role tools can appear on Windows 10. Users reported Sorry, something went wrong fault bulletin in SharePoint 2013, and today we're going to show you how to ready it.

How can I fix "Lamentable, something went incorrect" error in SharePoint 2013?

• • Set – "Sorry, something went wrong" SharePoint 2013
    1. Change the Require content approval settings
    2. Publish display templates
    3. Delete the recurring calendar appointments
    4. Brand sure that the time zone is configured
    5. Configure the Root site collection
    6. Make sure that your domain account has admission to SPDataAccess role
    7. Restart the SPTimer service
    8. Bank check App Direction Service
  • Fix – "Pitiful, something went incorrect" SharePoint 2013 search
    1. Delete the service application and create a new 1
    2. Change the access rights
    3. Be sure that Search Service Awarding is working
    4. Check if the SharePoint Search Host Controller is running
  • Fix – "Distressing, something went wrong" SharePoint 2013 workflow
    1.  Create a new workflow with a unlike name
    2. Utilize flushdns control
    3. Assign db_owner permissions to your user business relationship
  • Prepare – "Sorry, something went wrong" SharePoint 2013 site collection

Sorry, something went incorrect in SharePoint 2013

Solution i – Alter the Require content approving settings

According to users, Sorry, something went wrong error message can appear due to your Content blessing settings. This fault appears when you endeavor to save SharePoint site as a template, and in gild to fix this problem, you demand to follow these steps:

1. Click the Gear icon and choose Site settings.
2. Go to Spider web Designer Galleries section and click on Solution.
3. Click the Library tab and click on Library Settings.
4. At present click on Versioning Settings.
5. Locate Content approval section and gear up Require content approval for submitted items to No. Click OK to save changes.
6. Save the site as a template.
7. After the template is successfully created, you can enable content approval again.

Solution 2 – Publish display templates

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

According to users, uploaded display templates won't piece of work for non-administrators, and they'll get Sorry, something went wrong error message.

To gear up this problem, brand sure that display templates are published.

Solution 3 – Delete the recurring calendar appointments

According to users, this error can appear if you lot import calendars from SharePoint 2003 to SharePoint 2013.

It seems that SharePoint 2013 has issues with recurring appointments, and in order to fix this issue it's necessary that you lot delete those appointments.

If y'all don't desire to permanently delete your appointments, you can restore them by going to the Site Contents > Recycle Bin and choosing the Restore option. After restoring the appointments, the issue should be permanently fixed.

---

SharePoint online calendar not showing events? Don't worry, nosotros've got yous covered.

---

Solution 4 – Brand certain that the time zone is configured

Sometimes this error appears in SharePoint 2013 if your time zone isn't properly configured. To check time zone settings in SharePoint, do the following:

1. Open up Central Administration > Application Management.
2. Locate your web application and click the Full general Settings icon in the Ribbon carte.
3. Web Application Full general Settings window will appear.
4. Cheque the Default Time Zone.

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

1. Click the clock in the bottom right corner and choose Date and time settings.
   
2. Go to the Time zone department and bank check if the fourth dimension zone is correct.
   

Alternatively, you can also cheque your time zone by post-obit these steps:

1. Press Windows Central + South and enter engagement.
2. Select Fourth dimension and engagement from the menu.
   
3. Locate the Fourth dimension zone section and check if your electric current time zone is correct. If not, be certain to modify it.
   

Now yous just demand to go back to Web Application Full general Settings and set the time zone of your server. Perform iisreset and the trouble should be permanently fixed.

---

Windows ten won't allow you change your time zone? Check out this guide to solve the problem easily.

---

Solution 5 – Configure the Root site collection

Co-ordinate to users, this issue tin sometimes occur if y'all don't have the Root site drove configured.

If y'all create your collection in /Sites/ instead of Root yous might feel this error, therefore we suggest to create a Root site collection and bank check if that fixes this fault.

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

Improper configuration can sometimes cause Distressing, something went wrong error to appear. In social club to avoid this problem in SharePoint 2013 while using Admission Services, you demand to grant sure permissions to your domain.

After granting your account access to the SPDataAccess role in SharePoint configuration database (in SQL Server) the issue will be completely resolved.

Solution 7 – Restart the SPTimer service

Users reported that this mistake appears while calculation apps to SharePoint. This error can be problematic, merely information technology can be fixed simply past restarting the SPTimer service (OWSTIMER.EXE).

After restarting the service, the error was completely fixed. In order to avoid these errors in the time to come, retrieve to restart SPTimer service every time you make a major configuration change in SharePoint 2013.

Solution eight – Bank check App Direction Service

Practiced Tip: Some PC issues are hard to tackle, particularly when it comes to corrupted repositories or missing Windows files. If you are having troubles fixing an error, your system may exist partially cleaved. We recommend installing Restoro, a tool that will browse your machine and identify what the fault is.
Click here to download and start repairing.

This error can appear if the App Management Service isn't installed, but you tin can gear up it past following these steps:

1. Open Central Assistants as ambassador and get to Application Direction > Manage Service Awarding.
2. Choose New > App Management Service.
3. Enter the necessary information in Service Application Name, Database Server and Database Name fields.
4. Select Create new awarding pool option and enter the name of the application pool.
5. Click OK to create a new app management service.
6. Afterward the App Direction service is created, go to System Settings > Manage Services on server.
7. Locate the App Management Service, and under the Activeness column click First.
8. Go back to Manage service applications and bank check if the Service Application Proxy is started.
9. Get to Site Settings and click Manage site features in Manage site features department.
10. Locate Workflows can use app permissions and click Activate push button.
11. Become to Site Settings > Site app permissions.
12. Copy the client section of the App Identifier betwixt the | and @ characters.
13. Get to http://{hostname}/{catalog site}/_layouts/fifteen/appinv.aspx.
14. Paste the client department of the App Identifier to the App ID field and click Lookup.

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

Sorry, something went incorrect in SharePoint 2013 search

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

If yous're getting this fault while using the search application, try deleting the service awarding. After you delete it, create it once again and the trouble with search should be fixed.

Later on creating a new service awarding, be sure that it's set up as a default for your application.

Solution 2 – Change the access rights

Yous tin fix this problem by calculation Everyone to the Members group. Bear in mind that you demand to change the rights to Read Simply. This isn't the best solution, and it's probably not the safest, then use it at your ain adventure.

Solution three – Be sure that Search Service Application is working

Sometimes Search Service Awarding tin can terminate working and that can cause Sorry, something went wrong error to announced. To set this problem, exercise the post-obit:

1. Go to Key Administration > Manage spider web Apps.
2. Highlight Sharepoint – lxxx > Service Connections and make sure that Search Service Awarding is checked.
3. Click OK to save changes.

Solution 4 – Check if the SharePoint Search Host Controller is running

SharePoint 2013 relies on certain services in order to run properly, and if SharePoint Search Host Controller isn't running, you might get Sad, something went wrong error bulletin while using search in SharePoint 2013.

To prepare this error, check if SharePoint Search Host Controller is running. To do that, follow these steps:

1. Printing Windows Key + R and enter services.msc. Press Enter or click OK.
   
2. When Services window opens, locate the SharePoint Search Host Controller service.
3. Check the status of the service. If service isn't running, right click it and choose Start from the menu.
4. In one case you lot enable this service, close Services window and check if the problem is fixed.

Sad, something went wrong in SharePoint 2013 workflow

Solution 1 – Create a new workflow with a unlike name

Users reported that Sorry, something went wrong fault message can exist caused by deleting and recreating your workflow. To ready this mistake y'all need to create a new workflow but employ a different proper name for it.

After creating a new workflow with a unlike name, the error should be completely stock-still.

Solution ii – Use flushdns command

This error can occur due to your DNS, merely you can easily fix information technology by flushing your DNS. To practice that, follow these simple steps:

1. Press Windows Key + Ten to open Power User Bill of fare and select Command Prompt (Admin) from the menu.
   
2. When Command Prompt starts, enter the ipconfig /flushdns.
   

Afterwards running the flushdns control, you might want to recycle Workflow and Service Bus services and attempt to publish workflow again.

If yous're having problem accessing Command Prompt as an admin, and so you improve take a closer await at this guide .

---

If you tin can't flush the DNS Resolver Cache in Windows ten, follow the steps in this handy guide to ready the outcome.

---

Solution iii – Assign db_owner permissions to your user business relationship

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

Sad, something went wrong in SharePoint 2013 site collection

Solution – Delete the web application

Users reported this fault while creating a site drove in SharePoint 2013, and to set up this problem you lot need to delete the web application you created. After that, follow these steps:

1. Open IIS Director and expand the local server at the top left corner.
2. Select Awarding pools.
3. Select Central Administration.
4. Select Advanced Settings and click Edit awarding pool in right cavalcade.
5. Edit shutdown time limit. Set a limit to college value than the default nether process model.

After doing this y'all should be able to create web applications and site collections without whatsoever errors.

Sorry, something went wrong SharePoint 2013 mistake can be caused past many unlike things, and information technology might be difficult to fix sometimes, only nosotros hope that you managed to ready it by using one of our solutions.

If you accept any other suggestions or questions, don't hesitate to leave them in the comments department below.

READ ALSO:

• SharePoint keeps asking for password on Windows 10
• Summit 3 browsers for seamless SharePoint employ [2019 LIST]
• We're having trouble reaching the server SharePoint error [FULL FIX]

Newsletter

parrhompsed1989.blogspot.com

Source: https://windowsreport.com/sorry-something-went-wrong-sharepoint-2013-windows-10/

Share this post