• Sharepoint Running Slow
• Sharepoint Online Slow
• Sharepoint 2013 Very Slow Jams

We have an new sharepoint 2013 site, Server Virtual and standalone, it has 12 gb ram. This sharepoint user interface extremely slow. In Developer Dashboard we see each aspx page requests waiting about 6-7 second.

• SharePoint Foundation 2010, SharePoint Server 2010; In this article Symptoms. Assume that you have a web application that uses claims-based authentication in SharePoint Foundation 2010 or SharePoint Server 2010. The SharePoint server does not have access to the Internet, or the server is protected by a firewall that has limited ports open.
• One thought on “ SharePoint 2013 – Pages are loading very slowly ” Pingback: SharePoint 2013 – Critical, Unexpected, Warnings and Monitorable errors in the SharePoint ULS logs SharePains Leave a Reply Cancel reply.

Question

ran009 on Tue, 05 Jan 2016 21:31:22

Hi there

When I load my SharePoint 2013 site - it takes about 14-15 seconds. Please see this IE Developer Tool screenshot for times taken.

The top two URLs are exactly same - From Click to XMLHTTPRequest - it takes 14.46 seconds - the browser keeps saying 'Waiting for site'.

Any clue, what might be causing slow performance?

Thanks.

Ibanez guitar serial number search. Developer Dashboard:

Developer Dashboard SQL Tab:

Sharepoint Running Slow

Replies

Alex Brassington on Tue, 05 Jan 2016 22:29:54

Does it do this on every page load and on every page?

Sharepoint Online Slow

Does it do the same on a different site collection?

Crawling through these logs is difficult and skilled work. Getting someone else on the other end of a bulletin board to get to the vital bit of information is very tricky, you generally get better results looking at what is and isn't working on a larger scale.

Having said that, 1.04 seconds to load a 0.65KB image seems absurdly slow, how is the latency on your connection?

Trevor Seward on Tue, 05 Jan 2016 22:32:22

Another question is what webparts are on that page? Looks like there may be a Content Query or DataView webpart, based on the XMLHttpRequest.

ran009 on Tue, 05 Jan 2016 22:51:18

Hi Alex,

Yes, every page loads slow.
There is only one site collection and it is slow.

All the Internet sites work fine so I assume Network latency should not be an issue. Could this be DNS issue?

Thanks.

Alex Brassington on Wed, 06 Jan 2016 09:29:15

What are the Internet sites?

Are you able to create a new site collection to test that for performance?

Sharepoint 2013 Very Slow Jams

Where is the SharePoint farm located in relation to you, the same building, another one in the same town or a server on another continent?

DNS is very unlikely to be related.

Dean_Wang on Wed, 06 Jan 2016 10:41:14

Hi ran009,

You can use SharePoint Developer Dashboard to monitor the page load process, which would be helpful to you to find the reason of the issue.

You need to create Usage and Health Data Collection Service Application and enable SharePoint Developer Dashboard to use it. More detailed information about it for your reference:

Best Regards,

Dean Wang

Dai Webb on Wed, 06 Jan 2016 11:04:41

Has it always been slow or has something changed and it has been slow since that change?

Are you seeing Event ID 8321 being logged on the server (in the Application log within Event Viewer)? See http://www.adventuresinsharepoint.co.uk/2014/04/30/a-certificate-validation-operation-took-xxxx-milliseconds-and-has-exceeded-the-execution-time-threshold/

ran009 on Wed, 06 Jan 2016 18:07:12

This happened after we upgraded from SP 2010 to SP 2013.

Nope, I do not see any Event ID 8321.

Thanks.

ran009 on Wed, 06 Jan 2016 20:56:09

I attach Developer Dashboard for your reference in the original ticket.

Thanks.

ran009 on Wed, 06 Jan 2016 20:58:34

Hi Trevor,

There is one LVWPs from same site collection.
1 RSS feed from an external site - I have already tried removing it but it did NOT give any faster performance.

Thanks.

Deepesh Yevle on Thu, 07 Jan 2016 02:01:07

Kabhi sautan kabhi saheli last episode 223 download. HI,

Please check Windows Services if any related services have been stopped. Check all server , Evnet IDs, CPU ,Clearing the cache, A- virus status,Reset IIS , apps pool.

Dean_Wang on Thu, 07 Jan 2016 03:23:32

Hi ran009,

In the Developer Dashboard, there are several sections.

For example, in the SQL section, you can check what type of queries runs in the background for each request so that it will be a great help for while troubleshooting the performance issues related to SharePoint. Once you go to the SQL section of the dashboard you can see the queries name and execution plan details will get displayed once you click on those links.

You can use the several sections to troubleshoot the issues related to performance in SharePoint 2013.

Best Regards,

Dean Wang

ran009 on Thu, 07 Jan 2016 22:07:09

Hi Dean,

Sure - I just updated a screenshot of SQL tab in Developer Dashboard.

Please let me know if I can provide more information.

Thanks.

ran009 on Fri, 08 Jan 2016 00:01:17

Hi ALex,

- The RSS Viewer webpart (wheter removed or not, site is still slow). It fetches data from MediaMiser.com. Even other pages which do NOT have RSS web part are still slow.

- I created a new Site Collection. A bit less slow, but still slow for a blank site.

- SP Farm is located about 20 miles from us in other building.

Everything has always been like this, and before we upgraded to SP 2013 everything was fine.

Thanks. Wii netflix hack.

ran009 on Mon, 01 Feb 2016 21:05:12

So it can help someone else having similar issue - I was able to fix my slow SharePoint 2013 by rerunning 'psconfig -cmd upgrade -inplace b2b;' and 'Product Configuration Wizard'.

Thanks all.

I was setting up Incoming Mails for SharePoint 2013 and like many people on Google, my mails were delivered to the Drop folder and were stuck there. I have solved this and have gained some insights into how Incoming Mails should be configured. This post captures these learnings.

Please note this is for SharePoint 2013 only.

1. My topology and Incoming Mails configuration

In the end the problem was because of a misconfiguration that was not appropriate for my topology. I will therefore first describe my topology and the original configuration.

I have a 4-servers farm with 2 WFEs and 2 Apps servers. The SharePoint Incoming Mails service is provisioned on both Apps servers. One of the Apps servers runs the Windows SMTP Service.

In Central Admin I configured Incoming Mails using the Automatic mode and specified to use Directory Management Service.

2. High level overview of how Incoming Mails works

This is necessary to understand the problem. If configured correctly, then when a mail is sent to Exchange, Exchange routes the mail to the SMTP Server that is specified in Central Admin’s Incoming Mails configuration. This ends up in the Drop folder of the SMTP Service on this server. A SharePoint timer job, namely Microsoft SharePoint Foundation Incoming E-Mail, monitors this folder and processes mails that are delivered to this folder. This timer job is responsible for creating items in your lists/libraries and removing processed mails from the Drop folder. This timer job is scheduled on all servers where the SharePoint Incoming Mails service is provisioned. It is scheduled to run every 1 minute by default.

3. The problem, root cause and the fix

As mails were being delivered to the Drop folder, we can exclude Exchange from the problem, and isolate it down to the SharePoint timer job. In my case, the root problem is because the timer job was not able to access the Drop folder to process delivered mails.

Recall that I have the SharePoint Incoming Mails service provisioned on 2 Apps servers (server A and B). This means that the timer job is scheduled to run on both of these servers. Recall that I also have the Windows SMTP service running on 1 Apps server (server A). This means the Drop folder is on server A.

In Central Admin I also configured Incoming Mails using Automatic Mode. This means SharePoint uses the Drop folder as specified by the Windows SMTP service. By default this is c:inetpubmailrootDrop.

The root cause is because when the timer job is running on server B, it is unable to access the Drop folder on server A. This is probably because it attempts to access it using c:inetpubmailrootDrop, which does not exist on server B.

I created a network share to the Drop folder on server A, switched Incoming Mails to Advanced Mode in Central Admin, and entered the share path (e.g. serverADrop) for the E-Mail drop folder setting and Incoming Mails immediately worked for me.

Be aware that you will need to grant appropriate permissions to the network share for the Central Admin’s app pool account, and the content web application app pool accounts as per the MSDN article on setting up Incoming Mails.

4. Understanding more about Incoming Mails

OK, so the timer job on server B could not access the Drop folder, but what about the timer job on server A? If the timer jobs are scheduled every 1 minute, the mails shouldn’t get stuck for a long time, right?

Well, this is where things got interesting.

By chance I noticed that even though the timer job is scheduled on 2 servers, it was only executing on server B as shown below.

The job on server A would be rescheduled every 1 minute, but it’d never execute.

I found this post http://www.sharepoint2013.me/Blog/Post/161/Incoming-email-service-on-SharePoint-2013-server-farm-, which explains what’s going on. As a summary, while the timer job can be defined on multiple servers (i.e., on those servers where the Microsoft SharePoint Foundation Incoming E-Mail service is provisioned), it will only execute on 1 particular server. The server that it will execute on seems to be internally set when the Timer Service Recycle job (of the Microsoft SharePoint Foundation Timer service) is executed.

I tested this and it seems to be true. I ran the Timer Service Recycle job and the Microsoft SharePoint Foundation Incoming E-Mailjob started executing on the other server (server A) and stopped executing on server B. I do not know how SharePoint picks which server to run the Incoming E-Mail job on.

The Timer Service Recycle job performs a graceful restart of the Timer service. You can read more about it here: http://blogs.msdn.com/b/besidethepoint/archive/2012/01/10/the-timer-recycle-job-job-timer-recycle.aspx. The default schedule for this job is 6:00am daily. It is however disabled by default on my server.

5. Summary and Take Away

So when incoming mails are stuck in the Drop folder, it is likely because they are not being processed by the Incoming E-Mail timer job. In a multi-servers farm, it is best to create a network share to the Drop folder and use this network share in configuring Incoming Mails in Central Admin. This helps to ensure that the Incoming E-Mail timer job can access the Drop location regardless of where it is being run from in the farm. Ensure you have granted permissions to the network share as per the MSDN article on configuring Incoming Mails.