Introduction to Troubleshooting AppFabric Reliability Issues for SharePoint

AppFabric & distributed cache issues in SharePoint is something that comes up with reasonable regularity, often because SharePoint admins have never been introduced to this extra layer of SharePoint before. Read this if you either want to get to know how SharePoint & AppFabric/distributed-cache hang together and/or you want to know the basics of troubleshooting…

4

SharePoint AppFabric Error – Failed to connect to hosts in the cluster

Or “ErrorCode<ERRCAdmin040>:SubStatus<ES0001>:Failed to connect to hosts in the cluster” if you want the full error. This is just a quick-one. You may see this error if you try and add a SharePoint server to AppFabric cluster. It can happen if there is a “cluster” configured but none of the servers exist anymore; in my case…

0

Graceful SharePoint AppFabric Restarts

Many people have asked about how to cleanly restart an AppFabric server so data in the cache isn’t lost and may have even found they’ve not been able to get it to work themselves. It’s a good question; I hope to answer how here to some extent, partly because the official commands don’t actually work…

9

AppFabric Distributed Logon Token/ViewState Cache is Timing-Out – Continued

In a previous post I described how to troubleshoot AppFabric timeouts a problem which many customers have seen, most acutely when SharePoint is under heavy load. One thing consistent to almost every case is that the main victims/culprits for timeouts are view-state and login caches, and since writing the previous post I’ve refined what the…

2

Troubleshooting SharePoint Event ID 6393

This event ID means “a SharePoint timer job had an unexpected failure” in short. Admittedly this isn’t overly informative given how many different timer-jobs there are for any given SharePoint farm. Your first challenge is therefore figuring out which job it’s talking about which shouldn’t be too hard given it gives you the class name…

1

Reduce AppFabric Calls to Active Directory for SharePoint Farms

AppFabric is a key part of any SharePoint 2013 as we all know by now. It’s used for many things indeed all over the product and AppFabric in turn uses Active Directory to make sure only authorised processes get access to the cache data. Thus when SharePoint uses AppFabric, it opens a new TCP connection…

0

Troubleshooting AppFabric Error Messages for SharePoint

Otherwise entitled “The Mysteries of the Wobbly AppFabric Cache-Cluster”. In the daily running of on-premise SharePoint 2013, you may have seen errors & warnings logged about AppFabric/the distributed cache cluster. This article is to clear up why they might be happening. Errors such as: Connection to the server terminated, check if the cache host(s) is…

1

Troubleshooting AppFabric Timeouts on SharePoint

SharePoint 2013 uses AppFabric to host a bunch of stuff in a cache-cluster. This is awesome mainly because each web-front-end server doesn’t have its’ own cache island that can’t be shared with the other web-front-ends and the likelihood of a cache-miss is much lower (especially if the load-balancer doesn’t do sticky-sessions), thus the caching becomes…

4

SharePoint 2013 + Distributed Cache (AppFabric) Troubleshooting

Two messages you may have seen if you’ve administered SharePoint 2013 in anyway way about caching are “This Distributed Cache host may cause cache reliability problems” and/or “cacheHostInfo is null” from PowerShell. This article is about how to fix those errors & caching reliability problems in general for SharePoint 2013. Update: see a simplified version…

49