Distributed Cache Service Exception: Unexpected exception in FeedCacheService.IsRepopulationNeeded: Cache cluster is down, restart the cache cluster and Retry.

I have been working on intranet Portal Project for a client, after completing the configuration and distribution of the services inside the farm, we found an error occurs every 5 minutes, the event id is 6398, and the event description is:

The Execute method of job definition Microsoft.Office.Server.UserProfiles.LMTRepopulationJob (ID 07bbf799-deb4-422f-8df8-81a30d22b1a1) threw an exception. More information is included below.

Unexpected exception in FeedCacheService.IsRepopulationNeeded: Cache cluster is down, restart the cache cluster and Retry.

The issue seems related to distributed cache service, so we run commands to check the health of distributed cache service

Use-cachecluster

Get-cachehost

The result was all servers are UP, that’s means that the configuration of the distributed cache service is correct, so I tried to check the permissions of the cache cluster by running the command

Get-CacheAllowedClientAccounts

 

It displayed  wss_wpg and wss_wpg_admin so i went looking in wss_wpg group and the user profile app (UPA) account was missing.

If the user profile app (UPA) account doesn’t have permissions, then you’ll see “Cache cluster is down, restart the cache cluster and Retry” a lot specifically, although with the farm account name in the error details as this is a timer-job.

The fix for this is to grant the service-account running whatever service is failing access to the cache-cluster as sometimes these permissions can be missing:

Grant-CacheAllowedClientAccount -Account “DOMAIN\service_account”