SharePoint 2016, Sharepoint 2013, Sharepoint 2010, Windows Server 2012, Sql Server 2012,2014,IIS, Active Directory,User Profile Service, Managed MetaData Service, Search Service, Topology, Web Application, IIS, Site collection, List, Library, PowerShell, office web app, Windows Authentication, NTLM, Kerberos, Saml, ADFS, Active Directory Import, MIM, Distributed Cache (AppFabric Cache) Event ID: 1000 & 1026 on SharePoint Server 2013 – SharePoint

Distributed Cache (AppFabric Cache) Event ID: 1000 & 1026 on SharePoint Server 2013

The reason I am writing this blog, because I spent a lot of time to fix the AppFabric Cache’s event ID 1000 & 1026. I almost spend a week and tried all the available solutions but no luck. here are the options which I tried in a sequence to fix my issue.

1)      I start the Distributed Cache on One server via Central Admin > manage Services on server, but it’s stuck on starting. Then I tried to re-start App fabric services from Services Console but its stuck atstopping.

Easy Fix:

Easy fix for this, add the services account which running AppFabric services into Local admin on the server. Once services started you can remove it from local admin.

2)      Now time to fix the error, once you make sure the Distributed Cache services started on the server and AppFabric services running via services console. Run the below mentioned powershell command to repair it.
$instanceName =”SPDistributedCacheService Name=AppFabricCachingService”
$serviceInstance = Get-SPServiceInstance | ? {($_.service.tostring()) -eq $instanceName -and ($_.server.name) -eq $env:computername}

$s.delete()

Now run this one

Add-SPDistributedCacheServiceInstance

Hope this will fix your problem. Making sure DC is running please run the following commands in the sequence to get the report.

Use-CacheCluster

Get-CacheHost ( result should be like this if its up otherwise down or unknown)

HostName : CachePort    Service Name     Service Status  Version                                                                   

——————–   ———–        ————–   ——-

Name server:22233  AppFabricCachingService UP 3 [3,3] [1,3]

Get-CacheHostConfig

ComputerName: Name of the server where DC running

CachePort:  22233

You will get the result like this:

HostName        : name of the Server
ClusterPort     : 22234
CachePort       : 22233
ArbitrationPort : 22235
ReplicationPort : 22236

Size            : 819 MB
ServiceName     : AppFabricCachingService
HighWatermark   : 99%
LowWatermark    : 90%
IsLeadHost      : True
******************************************************
Update: turn off the App fabrice cache services on the server which are not part of Distributed Cache Cluster. simply run the below command on the server to stop it.

Remove-SPDistributedCacheServiceInstance

You may also like...

Leave a Reply

Your email address will not be published. Required fields are marked *