SharePoint is very slow and takes a long time to load.

I Recently faced an issue :

SharePoint is very slow and takes a long time to load.

In Central Admin under the Task Manager I noticed that there are 9 w3wp.exe process running and 1 of it is really consuming a large memory.

I have determined the related App Pool for the w3wp.exe using the following command.

Run the following command from the following location:

Cd C:\%SystemRoot%\System32\inetsrv
Command: appcmd.exe list WP
Note: This command returns results only if we have w3wp.exe process is running under task manager

This has allowed me to know which app Pool is the cause for the slowness of the server

Later I realised that on the weekend I have received almost 60 auto triggerd emails from 1 of the Scheduled workflows which is trying to run every 5 mins and is the reason for Issue.

Solution:

1) I Terminated the Scheduled task for work flow

2) As I now know which App Pool is causing the issue , I have recycled it after terminating the Scheduled task.

Wihout a need to IISRESET the issue was fixed.

Comments

Post a Comment

Popular posts from this blog

Migrate Secure Store Service Application from SharePoint 2013 to SharePoint 2016

Image
Migrate Secure Store Service Application Whenever we migrate SharePoint from one version to the next version , we recreate most of the service applications. However, in few cases where we have dependencies  with service applications like secure store and Managed metadata service which may have several credentials and term stores. recreating all the service IDs may be a tedious job and can easily land us in to issues. Hence, it is recommended to upgrade the Secure store service application.  Title: Steps to Migrate Secure Store Service Application from SharePoint 2013 to 2016 In on of my SharePoint Migration Projects from SharePoint 2013 to SharePoint 2016  Secure Store Service Application was one of the critical services used by the customer due to its dependency with Data Refresh Jobs from SSAS.  This article is a step by step approach to migrate Secure Store from SP 2013 to SP2016. Steps: Identify the Secure store database used in the SharePoint 2013 Database and restore a copy to th
Read more

Creation of Secure Store Service Application failed because of the following errors: The Timer Job Completed but failed on one or more machines in the farm.

Image
Unable to start Secure Store Service : Error : Creation of Secure Store Service Application failed because of the following errors: The Timer Job Completed but failed on one or more machines in the farm. Solution : Delete the Secure Store Service Application. Close all the browsers and runt the sharePoint Configuration wizard and retry to configure the secure store service and the issue should be fixed. If the issue still persists , start the Secure Store Service Application using the following commands. $proxy = Get-SPServiceApplicationProxy | where {$_.TypeName -eq "Secure Store Service Application Proxy"} $proxy.Status = "Online" $proxy.Update() In few cases it may happen that the Proxy service may start and the secure store service still has an error.In this case please delete the Secure Store service  and recreate using PowerShell as below : $sa = New-SPSecureStoreServiceApplication -Name "Secure Store Service Applicatio
Read more

HTTP 403 Forbidden SharePoint 2013

Image
Today  I faced an Issue in SharePoint where I got the error :"HTTP 403 Forbidden" for any site collection under a Web Application and this problem existed on Central Admin. Error : HTTP 403 Forbidden This error (HTTP 403 Forbidden) means that Internet Explorer was able to connect to the website, but it does not have permission to view the webpage. This problem occured after I tried configuring the SSL certificate for Central admin and the other Web Application. In this attempt I managed to Crash my SharePoint Farm. I have tried accessing the site from IIS with no go. Did Run the SharePoint Configuration Wizard successfully. Tried accessing the Central Administration Page with no go :( Resolution: After Trying the above options which did not work , finally I have deleted the Central Administration site from IIS. Run the SharePoint Products Configuration Wizard again and the Central Administration site has  been recreated. Launched Ce
Read more