tag:blogger.com,1999:blog-7732432868969196646.post8479666639874057850..comments2024-02-16T06:29:59.099-05:00Comments on Al's Tech Tips: SharePoint 2013: This Distributed Cache host may cause cache reliability problemsUnknownnoreply@blogger.comBlogger2125tag:blogger.com,1999:blog-7732432868969196646.post-89714023937901681852015-08-14T19:58:53.283-04:002015-08-14T19:58:53.283-04:00See this article SharePoint 2013: how to remove a ...See this article <a href="http://alstechtips.blogspot.com/2014/07/sharepoint-2013-how-to-remove-cache.html" rel="nofollow">SharePoint 2013: how to remove a cache host from an unrecoverable farm server</a>. Try out these steps and then let me know what occurs.Alhttps://www.blogger.com/profile/07690348866694162731noreply@blogger.comtag:blogger.com,1999:blog-7732432868969196646.post-10635401611536282832015-08-13T16:19:22.165-04:002015-08-13T16:19:22.165-04:00Hi Al - I was able to sort out most of my issues w...Hi Al - I was able to sort out most of my issues with Distributed Cache Host with your guide except one. Hoping you can shed some light. Health Analyzer failing on a non-existent server. Since that server does not exist Get-SPServiceInstance PS command not returning anything. "Unregister-CacheHost" fails with "No such host is known". Any suggestion how can I remove this. Tried doing multiple "ReAnalyze" with no luck. <br /><br />Host names match through Get-ServiceInstance and Get-CacheHost commands. That non-existent server does not show up in these lists.Not sure where Health Analyzer picking that name from. That server used to exist at one point but decommissioned long time ago. :-( <br /><br />Appreciate any feedback!PeaceBeUponYouhttps://www.blogger.com/profile/18207877861489430852noreply@blogger.com