Commands to Troubleshoot Distributed Cache Error In SharePoint 2013

1
Commands to Troubleshoot Distributed Cache Error
In SharePoint 2013
/pages/SharePoint-Repair-Tool/1381880235392544
u/1/112419988540311198928
/alexwaston14/file-repair-tool
 
http//sharepoint.filerepairtool.net/blog/troubles
hoot-distributed-cache-error-sharepoint-2013
2
Index

• About the Issue
• Errors of SharePoint
• Complete Troubleshooting options
• Automatic solution
• Conclusion

 
http//sharepoint.filerepairtool.net/blog/troubles
hoot-distributed-cache-error-sharepoint-2013
3
About the Issue

• The Distributed Cache service is responsible
  to execute either a physical or virtual server.
  Sometime SharePoint 2013 application get prone of
  Distributed Cache error and start showing error
  message (401  Not Authorized) while loading
  clients homepage. This error is the main reason
  of poor SharePoint performance, you may get
  various types of errors some of them are

 
http//sharepoint.filerepairtool.net/blog/troubles
hoot-distributed-cache-error-sharepoint-2013
4
Errors of SharePoint

• Unexpected Exception in SPDistributedCachePointerW
  rapperInitializeDataCacheFactory for usage
  DistributedLogonTokenCache Exception
  Microsoft.ApplicationServer.Caching.DataCacheExce
  ption ErrorCodeltERRCA0018gtSubStatusltES0001gtThe
  request timed out.
• Unexpected error occurred in method GetObject,
  usage Distributed Logon Token Cache Exception
  Microsoft.ApplicationServer.Caching.DataCacheExce
  ption ErrorCodeltERRCA0018gtSubStatusltES0001gtThe
  request timed out.

 
http//sharepoint.filerepairtool.net/blog/troubles
hoot-distributed-cache-error-sharepoint-2013
5
Complete Troubleshooting options to cure
Distributed Cache Error In Sharepoint 2013

• Step 1 Execute the below given two commands
• use-cachecluster
• get-cachehost
• Run these on any server thats a cache host,
  in the case of multiple cache hosts in the
  cluster it is suggested to execute the commands
  on all of them and make sure that the output is
  equal. These above commands return the AppFabric
  Reference of the cache cluster.
• If you are getting Error message then it
  means the node is NOT a part of the AppFabric
  cluster.

 
http//sharepoint.filerepairtool.net/blog/troubles
hoot-distributed-cache-error-sharepoint-2013
6

• Step 2 Get the SharePoint position of the Cache
  Cluster from SharePoint configuration database
• Farm Get-SPFarm
• cacheClusterName SPDistributedCacheCluster_
  Farm.Id.ToString()
• cacheClusterManager Microsoft.SharePoint.Distr
  ibutedCaching.Utilities.SPDistributedCacheClusterI
  nfoManagerLocal
• cacheClusterInfo cacheClusterManager.GetSPDist
  ributedCacheClusterInfo(cacheClusterName)
• cacheClusterInfo
• cacheClusterInfo.CacheHostsInfoCollection fl
•  
• Verify that the output of the both command i.e.
  first command from option 1 and command from
  step 2 is same.
• To check the results in the configuration
  database, run the below given query
• SELECT FROM SharePoint_Config.dbo.CacheClus
  terConfig where EntryType like hosts

 
http//sharepoint.filerepairtool.net/blog/troubles
hoot-distributed-cache-error-sharepoint-2013
7
Step 3 Try to remove the AppFabric host from
each Cache Host

1. Stop-SPDistributedCacheServiceInstance -Graceful
2. Remove-SPDistributedCacheServiceInstance
3. After it verify the results with
4. use-cachecluster
5. get-cachehost

 
http//sharepoint.filerepairtool.net/blog/troubles
hoot-distributed-cache-error-sharepoint-2013
8
Step 4 Try to Add Distributed Cache on the
server

• Add-SPDistributedCacheServiceInstance
• After executing the above given commands on a
  host must verify
• Central Admin gt Services on server gt Server gt
  Distributed cache service needs to be Started.
• Host gt services.msc gt AppFabric Caching service
  needs to be Started gt and this should not crash
  after a few seconds/minutes.

 
http//sharepoint.filerepairtool.net/blog/troubles
hoot-distributed-cache-error-sharepoint-2013
9
Step 5 Refresh the distributed cache service

1. Use-CacheCluster
2. Get-CacheHost
3. Stop-CacheCluster
4. Start-CacheCluster

 
http//sharepoint.filerepairtool.net/blog/troubles
hoot-distributed-cache-error-sharepoint-2013
10
Step 6 After the execution of above steps if you
still suffering with the error then go additional
by deleting the instance of the server that is
NOK DO NOT run the below given commands

• instanceName SPDistributedCacheService
  NameAppFabricCachingService
• serviceInstance Get-SPServiceInstance ?
  (_.service.tostring()) -eq instanceName -and
  (_.server.name) -eq envcomputername
• serviceInstance.Unprovision()
• then
• Get-SPServiceInstance fl TypeName, ID
• s Get-SPServiceInstance ID
• s.delete()
• And then to add it back to the cluster
• Add-SPDistributedCacheServiceInstance

 
http//sharepoint.filerepairtool.net/blog/troubles
hoot-distributed-cache-error-sharepoint-2013
11
Step 7 Commands of step 6 is able to fix the
issue but at the same time it can create orphan
entries in the configuration database. An orphan
entry is produced so that you have to reinstall
the server that is NOK and again add it back to
the farm with a diverse name.

• a. Export-CacheClusterConfig Path c\config.xml
• b. Delete the host
• Common output would seem like this for solitary
  cache host in the cluster
• lthostsgt
• lthost replicationPort22236 arbitrationPort222
  35 clusterPort22234
• hostIdid size400 leadHosttrue
  accountdomain\account
• cacheHostNameAppFabricCachingService
  nameservername.domain.local
• cachePort22233 /gt
• lt/hostsgt
• c. Stop-cachecluster
• d. Import-cacheclusterconfig file
  path\file.xml
• e. Start-cachecluster

 
http//sharepoint.filerepairtool.net/blog/troubles
hoot-distributed-cache-error-sharepoint-2013
12
Automatic solution

• This error can also fixed by the use of an
  automatic tool known as SharePoint Repair tool,
  this application is specially designed by the
  SharePoint professionals to get rid of any
  related to this database. If you are not able to
  run above given commands due to lack of knowledge
  then this recovery tool is the best option.

 
http//sharepoint.filerepairtool.net/blog/troubles
hoot-distributed-cache-error-sharepoint-2013
13
Conclusion

• All the given methods is able to fix this
  issue without need of any extra effort. But it is
  recommended that given commands must be executed
  by the professionals because a simple mistake may
  harm your data. Automatic solution is for all
  types of user because through this one can easily
  fix SharePoint Errors.

 
http//sharepoint.filerepairtool.net/blog/troubles
hoot-distributed-cache-error-sharepoint-2013
14
The End
/pages/SharePoint-Repair-Tool/1381880235392544
/u/1/112419988540311198928
/alexwaston14/file-repair-tool
 
http//sharepoint.filerepairtool.net/blog/troubles
hoot-distributed-cache-error-sharepoint-2013