Archive

Archive for February, 2016

SharePoint 2013 : Change the Distributed Cache Service managed account

February 29, 2016 Leave a comment

After Completing the configuration of SharePoint Farm , i noticed that SharePoint Health Analyzer in central administration site has detected critical events that require my attention. one of these events was  changing  Distributed Cached Service Account in SharePoint servers because it runs under farm account.

execute each of  below steps

$Farm=Get-SPFarm
$CacheService=$Farm.Services | Where {$_.Name -eq "AppFabricCachingService"}
$Accnt = Get-SPManagedAccount -Identity Domain\ServiceAccount
$CacheService.ProcessIdentity.CurrentIdentityType = "SpecificUser"
$CacheService.ProcessIdentity.ManagedAccount = $Accnt
$CacheService.ProcessIdentity.Update()

For your info , in case of you have multiple servers in the farm, and distributed cache service is running on multiple server , you may encounter some issues like changes only applied on the server in which you execute above commands . i will prepare a post for resolving any issues related to distributed cache service.

The Execute method of job definition Microsoft.Office.Server.UserProfiles.UserProfileImportJob

February 28, 2016 Leave a comment

i had an issue related with profile synchronization server, Event ID 6398, the event description is

The Execute method of job definition Microsoft.Office.Server.UserProfiles.UserProfileImportJob (ID f3529d29-2c4e-44fe-bf62-f7c8923d3ba0) threw an exception. More information is included below.

There was no endpoint listening at http://SPDemo:***/ResourceManagementService/MEX that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.” 

this is issue has usually occurred because of reboot in which  Forefront Identity Manager service 

didn’t start

 

so you need to start it manually , Please start Forefront Identity Manager service and Forefront Identity Manager Synchronization service from Run >> Services.msc

Svc

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

February 26, 2016 Leave a comment

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.

Error

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”

 

Categories: SharePoint 2013