Problem
You added a new web front end server to the farm. Subsequently, you see the following report in the farm's All Reports listing:
Solution
ReferencesYou added a new web front end server to the farm. Subsequently, you see the following report in the farm's All Reports listing:
Title | This Distributed Cache host may cause cache reliability problems. |
Severity | 2 - Warning |
Category | Configuration |
Explanation | This Distributed Cache service on this Distributed Cache host has been stopped but not unregistered from the farm. In order to avoid reliability issues, it is recommended that a Distributed Cache host with a stopped Distributed Cache service be unregistered from the farm |
Remedy | Unregistered cache hosts using PowerShell. For more information about this rule, see http://go.microsoft.com/fwlink/?LinkID=3136960". |
Failing Servers | [new WFE] |
Failing Services | SPTimerService (SPTimerV4) |
Rule Settings | View |
Solution
- Ensure ShellAdmin Access
- Login to the WFE using the SharePoint Setup User Administrator account (eg, spAdmin).
- On the WFE, launch an elevated SharePoint Management Shell.
- Execute the following command:
Get-SPShellAdmin
This checks the farm configuration database for those users who can modify it. - Verify that the SharePoint Setup User Administrator account has been added. If it isn't, make it so.
- Get Service Instance ID
- Login to the WFE using the SharePoint Setup User Administrator account (eg, spAdmin).
- On the WFE, launch an elevated SharePoint Management Shell.
- Execute the following command:
Get-SPServiceInstance | Where-Object {$_.Server -Like "*<yourWFE>*"} | Select-Object TypeName, ID, Status | Sort-Object TypeName
This generates a listing of SharePoint-related service instances on the machine, including their IDs and statuses, sorted. - Look for Distributed Cache in this listing.
- Copy its ID.
- Delete Service Instance
- In the same management shell, execute the following command:
(Get-SPServiceInstance <yourWFE-ID>).delete()
If you now re-execute the command in step 2.3, above, you will no longer see it listed. However, if you should now re-analyze the rule, it still remains. And if you check the server services control panel, you will see that the AppFabric Caching Service status remains Running. - Remove Service Instance
- In the same management shell, execute the following command:
Remove-SPDistributedCacheServiceInstance
- Re-analyze Rule Violation Problem
- In Central Administration, navigate to the Review problems and solutions page.
- Click on the item, This Distributed Cache host may cause cache reliability problems.
- Click the Re-analyze button.
- Initial deployment administrative and service accounts in SharePoint 2013
- This Distributed Cache host may cause cache reliability problems (SharePoint 2013)
- Managing Windows Server AppFabric Caching Features
- SharePoint 2013: how to remove a cache host from an unrecoverable farm server
- SharePoint Setup User Administrator
- Get-SPShellAdmin
- Get-SPServiceInstance
- Remove-SPDistributedCacheServiceInstance
- SharePoint 2013 Distributed Cache: Boon or Bane
- I tried the process in the Microsoft TechNet article cited above (2); however, this failed to resolve the problem.
- You could of course stop the AppFabric Caching Service service using the server Services panel, but this is not recommended. I've tried this myself without success. I then used the PowerShell command, above, and this worked.
2 comments:
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.
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. :-(
Appreciate any feedback!
See this article SharePoint 2013: how to remove a cache host from an unrecoverable farm server. Try out these steps and then let me know what occurs.
Post a Comment