SharePoint 2013 / 2016 uses app-fabric to host couple of cache cluster in this process the services of App fabric might get stooped due to it's time line . Also need to rights
Solution 1 : Start the App Fabric cahcing services in Services.msc and reset IIS
Solution 2: Extend the cache Settings with powershell
Solutions 3: The server farm account, which is also referred to as the database access account, is used as the application pool identity for Central Administration
Solution 1 : Start the App Fabric cahcing services in Services.msc and reset IIS
Solution 2: Extend the cache Settings with powershell
$set = Get-SPDistributedCacheClientSetting -ContainerType DistributedViewStateCache
$set.requestTimeout = “100” # normally it’s 20ms
$set.channelOpenTimeOut = “100” # normally it’s 20ms
# maybe change the other values too
Set-SPDistributedCacheClientSetting -ContainerType DistributedViewStateCache $set
Solutions 3: The server farm account, which is also referred to as the database access account, is used as the application pool identity for Central Administration
- Membership in the WSS_ADMIN_WPG Windows security group for the SharePoint Foundation 2013 Timer service.
- Membership in WSS_RESTRICTED_WPG for the Central Administration and Timer service application pools.
- Membership in WSS_WPG for the Central Administration application pool.
Solution 4 : Use the commands to stop ,remove and start the distributed service
Stop-SPServiceInstance
Remove-SPDistributedCacheServiceInstance
Add-SPDistributedCacheServiceInstance
