Contents
Welcome to SharePoint Online troubleshooting! Here’s a collection of information on how to identify and fix errors that you may run into when using this product. Below is a collection of the top issues.
What happens when there are too many SharePoint Online requests?
When a user exceeds usage limits, SharePoint Online throttles any further requests from that user account for a short period. All user actions are throttled while the throttle is in effect. For requests that a user performs directly in the browser, SharePoint Online redirects you to the throttling information page, and the requests fail.
In the F12 tools, on the Network tab, press the green play button to load a page. Click one of the .aspx files returned by the tool and then click DETAILS. Click Response headers. What’s causing performance issues in SharePoint Online?
What happens when you get throttled in SharePoint Online?
What happens when you get throttled in SharePoint Online? 1 For requests that a user performs directly in the browser, SharePoint Online redirects you to the throttling information… 2 For all other requests, including CSOM or REST calls, SharePoint Online returns HTTP status code 429 (“Too many… More
You have Microsoft Office 2010 installed on a computer. On the same computer, you also have an Office 2013 application installed, such as Lync 2013 or Word 2013. In this scenario, when you try to open a document from SharePoint Online by using the Office 2010 client application, you receive the same error message that is mentioned in Scenario 1.
How to create custom 404 error page in SharePoint?
Let’s see how a custom 404 error page in SharePoint can be done: 1. Create an aspx page in Root site collection (say, “\\SitePages\\CustomError.aspx”). Add some descriptive image and text to it. 2. Go to IIS Manager, Backup the web.config file and proceed with the following steps. 3. Expand the desired web application, open the “Error Pages” feature.
They are solutions that someone figured out just by looking at the architecture a little while longer with a lot of head-scratching, lip-biting, coffee-drinking, and gum-chewing frustrations. SharePoint is an amazing technology that packs a lot of functionalities that would have been dubbed independent modules into one single application.
Why does SharePoint 2013 take so long to load?
I installed SharePoint 2013 on a single box along with 6gb and all I was able to do is to create a single site collection and since then it stopped working. Since the problem is only when you try to access SharePoint in browser, you should enable Developer Dash board and check what factor is taking most time while page loads.
Installing the root certificate, disable the clr check or send clr.microsoft.com to the 127.0.0.1. It speed ups the “awake” of the websites. Sometimes considerably. Its also a must have trick for SharePoint 2010. Configure Noderunner to use less memory.
Are there any problems with SharePoint 2013 Foundation?
We are facing problems with SharePoint 2013 Foundation with SQL Express. Users are (there are total 50 of them, peak should be no more than 20) experiencing long latency and “Sorry, something went wrong” screens. I analyzed logs tracing problems back with correlation IDs and here is what I found (couple of cases included):