Troubleshooting Distributed Cache for SharePoint 2013 On Premise


Here is a script that will give you a good starting point for troubleshooting Distributed Cache for SharePoint 2013 On Premises.

Make sure to save it as a .ps1 file and run the script (Administrator) on a running Cache Host like "PS C:\> .\DistributedCacheScript.ps1", or right click "Run with PowerShell" as it will simply not work with copy paste.

I will keep adding and changing functionality if time permits, please feel free to suggest any improvements.

Small post on how to interpret the output you can find here:

http://blogs.technet.com/b/filipbosmans/archive/2015/09/07/how-to-check-for-issues-with-distributed-cache-and-the-script.aspx

Recommendations post:

http://blogs.technet.com/b/filipbosmans/archive/2015/10/17/sharepoint-distributed-cache-recommendations.aspx

Tools:

http://blogs.technet.com/b/filipbosmans/archive/2016/02/29/tools-to-troubleshoot-distributed-cache-sharepoint-2013.aspx

It will:

  • Create a folder @ C:\Distributed Cache [ServerName]
  • Create files which contain things like local event logs for DC, DC commands, exported configuration XML for the Cache Cluster etc.

It will not make any changes what so ever anywhere.

Apologies for the excessive formatting code added, I like to keep things nice and clean 🙂

Decided to add more than just Cluster/Server checks, now includes also output to verify SharePoint permission issues for instance.

Due to adding more things lately, you might want to run it on all Cache Hosts when you suspect non-Cluster related settings being related to your issue.

Firewall check will only work on Server 2012 or higher.

Moved to https://gallery.technet.microsoft.com/Distributed-Cache-6e8ace1a

Big thanks to Cristian Negulescu for merging 2013 and 2016 version and adding the SQL part.

Comments (4)

  1. BlueSky2010 says:

    Thank you for putting this together!

    Since you are open to suggestion (:p) – I would say if there were a scenario as to when you would use a script like this that might help others more.

  2. Hi, was planning to do this but never found the time, will update the post some time soon.
    You will be able to spot a lot of common issues and rule out cluster misconfiguration.

Skip to main content