NOTE – PDF format updated to include both SharePoint 2013 and 2016 notes.
Ever wondered what fixes are inside of a given CU? Please see attached PDF with full detail. I wanted a new format for easy reading. Show management and make the business case for why downtime should be taken to apply CUs. Also posted at http://sharepointupdates.com/
If you found this helpful, please leave a comment.
![shades_smile_thumb_thumb_thumb_thumb[2]](http://www.spjeff.com/wp-content/ftp_uploads/Whats-in-that-patch-SharePoint-2013--Oct_A762/shades_smile_thumb_thumb_thumb_thumb2.gif "shades_smile_thumb_thumb_thumb_thumb[2]")
| What’s in that patch – Nov 2018.PDF |
When SharePoint Server Distributed Cache is unhappy in a farm, you may see page loads error, 404s not found, API failures, and similar. Having a well configured Distributed Cache will ensure healthy page renderings. PowerShell notes below. Credit to one awesome long term SP engineer for the snippets below. Thank you. Cheers!
CHECK STATUS
To check the status of the Distributed Cache Servers, run this command on each Farm from a DC machine.
|
1 2 3 4 5 6 7 |
# CHECK DC STATUS Use-CacheCluster; Get-CacheHost; $servers=Get-CacheHost; foreach ($server in $servers) { Get-AFCacheHostConfiguration -ComputerName $server.hostname -CachePort "22233" } |
REMOVE SERVER
|
1 2 |
# REMOVE COMPUTER TO DC HOSTS Remove-SPDistributedCacheServiceInstance |
ADD SERVER
|
1 2 |
# ADD COMPUTER TO DC HOSTS Add-SPDistributedCacheServiceInstance |
CHANGE SERVICE = UP
To change the Service Status of a server to UP, run these commands on the server you wish to bring UP.
|
1 2 3 4 |
# CHANGE DC STATUS = UP $instanceName ="SPDistributedCacheService Name=AppFabricCachingService" $serviceInstance = Get-SPServiceInstance | ? {($_.service.tostring()) -eq $instanceName -and ($_.server.name) -eq $env:computername} $serviceInstance.Provision() |
CHANGE STATUS = DOWN
To change the Service Status of a server to DOWN, run these commands on the server you wish to bring DOWN.
|
1 2 3 4 |
# CHANGE DC STATUS = DOWN $instanceName = "SPDistributedCacheService Name=AppFabricCachingService" $serviceInstance = Get-SPServiceInstance | ? {($_.service.tostring()) -eq $instanceName -and ($_.server.name) -eq $env:computername} $serviceInstance.Unprovision() |
CHANGE IsLeadHost=FALSE
There can be only one IsLeadHost=True server in a Farm. If there is more than is IsLeadHost=True servers your Farm will act unstable and people will see page load errors. We traditional set the lowest server name alphabetically in a Farm as IsLeadHost. Change the DC Farm so that Service Status=DOWN on server.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 |
# CHANGE LEAD HOST = FALSE $instanceName = "SPDistributedCacheService Name=AppFabricCachingService" $serviceInstance = Get-SPServiceInstance | ? {($_.service.tostring()) -eq $instanceName -and ($_.server.name) -eq $env:computername} $serviceInstance.Unprovision() #Change IsLeadHost value to false (use computer name or local computer name) Set-CacheHostConfig -HostName $env:computername -CachePort 22233 -IsLeadHost "false" -RefreshNow # CHANGE DC SERVER STATUS = UP $instanceName ="SPDistributedCacheService Name=AppFabricCachingService" $serviceInstance = Get-SPServiceInstance | ? {($_.service.tostring()) -eq $instanceName -and ($_.server.name) -eq $env:computername} $serviceInstance.Provision() # WAIT 30 SECONDS FOR DC STATUS=UP Start-Sleep -s 30 # CHECK DC STATUS Use-CacheCluster; Get-CacheHost; $servers=Get-CacheHost; foreach ($server in $servers) { Get-AFCacheHostConfiguration -ComputerName $server.hostname -CachePort "22233" } |
More than one IsLeadHost=True is BAD.
SET DC CACHE SIZE (24GB server = 6GB CACHE)
Also notice our default DC cache size is only 819 MB. MSFT formula = 24GB-2GB=22GB/2GB=11GB. Typical recommendation for a 24GB server is no more than 8GB Cache size. If running 24GB RAM on WFE, we should allocate 6GB (1024*6=6144 MB).
|
1 2 3 4 5 6 7 8 9 10 |
# CHANGE DC STATUS = DOWN $instanceName = "SPDistributedCacheService Name=AppFabricCachingService" $serviceInstance = Get-SPServiceInstance | ? {($_.service.tostring()) -eq $instanceName -and ($_.server.name) -eq $env:computername} $serviceInstance.Unprovision() # CHANGE DC CACHE SIZE (6GB) Update-SPDistributedCacheSize -CacheSizeInMB 6144 # CHANGE DC SERVER STATUS = UP $instanceName ="SPDistributedCacheService Name=AppFabricCachingService" $serviceInstance = Get-SPServiceInstance | ? {($_.service.tostring()) -eq $instanceName -and ($_.server.name) -eq $env:computername} $serviceInstance.Provision() |
References
NOTE – PDF format updated to include both SharePoint 2013 and 2016 notes.
Ever wondered what fixes are inside of a given CU? Please see attached PDF with full detail. I wanted a new format for easy reading. Show management and make the business case for why downtime should be taken to apply CUs. Also posted at http://sharepointupdates.com/
If you found this helpful, please leave a comment.
| What’s in that patch – Oct 2018.PDF |
After troubleshooting an issue with SharePoint Designer, I wanted to document the fix for others. Installing the “DP.CustomActions” WSP from CodePlex worked well on SharePoint 2010 and 2013. However, with 2016 an issue occurs which requires additional [web.config] modification. Details below. Cheers!
<authorizedType Assembly=”DP.Sharepoint.Workflow, Version=1.0.0.0, Culture=neutral, PublicKeyToken=0298457208daed83″ Namespace=”DP.Sharepoint.Workflow” TypeName=”*” Authorized=”True” />
Fun software I work with every day.
Return to Top ▲
