Ask Learn
Preview
Ask Learn is an AI assistant that can answer questions, clarify concepts, and define terms using trusted Microsoft documentation.
Please sign in to use Ask Learn.
Sign inThis browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Issue
You have a high CPU utilization, in my case it was almost 100% for several hours, and mostly consumed by the Security Token Service (STS). The issue will show up after installing June 2016 CU for SharePoint 2013, or any subsequent CU until March 2017 CU.
Restarting IIS will resolve the issue temporarily, but it will show up again shortly. Checking the SharePoint ULS logs will show events as shown below:
xx/xx/xxxx xx:xx:xx.xx w3wp.exe (0x34F0) 0x47C4 SharePoint Foundation Database 4ohp High Enumerating all sites in SPWebApplication Name=Contoso Site.
xx/xx/xxxx xx:xx:xx.xx w3wp.exe (0x0448) 0x066C SharePoint Foundation Database 4ohq Medium Site Enumeration Stack: at Microsoft.SharePoint.SPBaseCollection.GetEnumerator() at Microsoft.Office.Server.Search.Administration.UrlMapper.GetNewCacheEntry(Pair`2 properties) at Microsoft.Office.Server.Search.Administration.UrlMapper.GetUrlMapping(QueryProperties properties, Boolean useCache, UrlZoneOverride urlZoneOverride) at Microsoft.Office.Server.Search.Administration.SearchServiceApplicationProxy.<>c__DisplayClass6.<UpdateQueryProperties>b__4(Object x) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem() at System.Threading.ThreadPoolWorkQueue.Dispatch()
Cause
Analyzing this issue shows that the Security Token Service was heavily consumed by receiving so many requests while SharePoint was enumerating all the sites in the farm, and in my case we had so many sites.
Solution
The issue was fixed in March 2017 CU for SharePoint Server 2013.
Note: this fix is only for this issue, and is not supposed to resolve any other performance or high CPU issue you have in your SharePoint farm.
Ask Learn is an AI assistant that can answer questions, clarify concepts, and define terms using trusted Microsoft documentation.
Please sign in to use Ask Learn.
Sign in