{"id":923,"date":"2013-07-10T15:37:10","date_gmt":"2013-07-10T22:37:10","guid":{"rendered":"https:\/\/mmman.itgroove.net\/?p=923"},"modified":"2023-02-24T21:48:42","modified_gmt":"2023-02-24T21:48:42","slug":"fixing-the-appfabric-cache-cluster-in-sharepoint-2013","status":"publish","type":"post","link":"https:\/\/regroove.ca\/archive\/2013\/07\/10\/fixing-the-appfabric-cache-cluster-in-sharepoint-2013\/","title":{"rendered":"Fixing the AppFabric Cache Cluster in SharePoint 2013"},"content":{"rendered":"

I ran into this at a client site recently, and wanted to blog my experience.  I had a number of things not working as expected in the Cache (including Event ID 1000 and Event ID 1026), and at the end of the day, it appears to have boiled down to 2 things.  Firstly, the cache cluster was improperly configured.  As such, I ended wiping out the cluster, and rebuilding it.  Then after much pain, I found that one of the servers in the cluster that was constantly complaining about not being able to start properly was still misconfigured (using the wrong account), and after stopping the cluster, exporting the config, fixing it, and reimporting the config, then restarting the cluster finally solved the problem for good.<\/p>\n

I started with this blog post http:\/\/www.sharepointconsultant.ch\/2013\/03\/07\/adding-a-local-sharepoint-2013-development-server-as-a-cache-host-to-appfabrics-cache-cluster\/<\/a>. <\/p>\n

That gave me the following knowledge:<\/p>\n

1) There\u2019s a Windows Service named \u201cAppFabric Caching Service\u201d, which matches 1:1 to each server in the cluster (IE. every server that\u2019s part of the cluster has this service on it, and it should be set to run \u201cAutomatic\u201d, and be running, if it\u2019s healthy).<\/p>\n

2) The key PowerShell you\u2019ll need to know is as follows.<\/p>\n

** Always run your PowerShell window as Administrator when working with the AppFabric Cache **<\/em><\/p>\n

Start with the following line of PowerShell to let it know who\u2019s boss.<\/p>\n

PS C:> Use-CacheCluster<\/font><\/p>\n

Next, find out the details about your individual host.  (It\u2019s most likely configured on port 22233)<\/p>\n

PS C:> <\/font>Get-CacheHostConfig \u2013ComputerName [yourServerName] -CachePort 22233<\/pre>\n
That should return the details for this server in the cluster.  Something like below.<\/p>\n
HostName        : [Your Server Name]
ClusterPort     : 22234
CachePort       : 22233
ArbitrationPort : 22235
ReplicationPort : 22236
Size            : 400 MB
ServiceName     : AppFabricCachingService
HighWatermark   : 99%
LowWatermark    : 90%
IsLeadHost      : True<\/font><\/p>\n
If, however, you\u2019re getting an error along the lines of:<\/p>\n
PS C:> <\/font>Get-AFCacheHostConfiguration : ErrorCode<ERRCAdmin010>:SubStatus<ES0001>:Specified host is not present in cluster.<\/pre>\n
You can register your host in the cluster as follows.<\/p>\n
PS C:> <\/font>Register-CacheHost \u2013Provider [yourProvider] \u2013ConnectionString [yourConnectionString] -Account \"NT AuthorityNetwork Service\" -CachePort 22233 -ClusterPort 22234 -ArbitrationPort 22235 -ReplicationPort 22236 \u2013HostName [yourServerName]<\/pre>\n
You\u2019ll need 3 pieces of information to properly run the statement above.<\/p>\n
yourProvider<\/font> & yourConnectionString<\/font> \u2013 Can be found in the registry under HKLM  Software  Microsoft  AppFabric  V1.0  Configuration or they can also be found in C:Program FilesAppFabric 1.1 for Windows Server in the DistributedCacheService.exe.config file.<\/p>\n
yourServerName<\/font> \u2013 The name of your server<\/p>\n
(Optionally you can change the account, but I would recommend you leave the Network Service account in place \u2013 this seems to keep SharePoint 2013 happy)<\/p>\n
Now when you run this command:<\/p>\n
PS C:> <\/font>Get-CacheHost <\/p>\n
You should see the following.<\/p>\n
HostName : CachePort         Service Name            Service Status Version Info
——————–         ————            ————– ————
MyServer1.domain.com:22233   AppFabricCachingService UP             3 [3,3][1,3]
MyServer2.domain.com:22233   AppFabricCachingService UP             3 [3,3][1,3]<\/font><\/p>\n
At the very least, you should see both servers in the cluster at this point.  If you see this above, you\u2019re done, and don\u2019t need the rest of this article.  However, if you\u2019re unlucky, and one or more of the servers are down (Service Status = Down, or Starting) keep reading.<\/p>\n
At this point, one of my servers was not started (DOWN), so I went ahead and ran the following.<\/p>\n
PS C:> Start-CacheHost \u2013ComputerName [yourServerName] \u2013CachePort 22233<\/font><\/p>\n
If that failed, like it did for me, I would recommend exporting your cache cluster configuration, and seeing if anything is wrong.  To do this, run the following.<\/p>\n
PS C:> Export-CacheClusterConfig [path to output filename]<\/font><\/p>\n
So, for example\u2026<\/p>\n
PS C:> Export-CacheClusterConfig c:file.txt<\/font><\/p>\n
When looking at the file, down near the bottom, I noticed that the account that MyServer1 was running under was all goofy (usernames shouldn\u2019t have tilde\u2019s in them).<\/p>\n
<hosts>
     <host replicationPort=”22236″ arbitrationPort=”22235″ clusterPort=”22234″
         hostId=”1909348767″ size=”800″ leadHost=”true” account=”DOMAINappsrv1~<\/font>“
         cacheHostName=”AppFabricCachingService” name=”MyServer1.domain.com”
         cachePort=”22233″ \/>
     <host replicationPort=”22236″ arbitrationPort=”22235″ clusterPort=”22234″
         hostId=”1634054989″ size=”400″ leadHost=”true” account=”DOMAINspService”
         cacheHostName=”AppFabricCachingService” name=”MyServer2.domain.com”
         cachePort=”22233″ \/>
<\/hosts><\/font> <\/p>\n
WARNING: MAKE A BACKUP BEFORE YOU MAKE ANY CHANGES!!!<\/font><\/p>\n
I fixed the account name (to match the service account on the other server DOMAINspService) and then had to import the configuration back in.  <\/p>\n
** BUT WAIT \u2013 There\u2019s more! **<\/p>\n
Before you try to import your configuration, you\u2019ll need to go into your Windows \u201cServices\u201d application and disable the \u201cAppFabric Caching Service\u201d, and then stop the service on each server in the cluster.<\/p>\n
To do this, go find the following service and double click on it.<\/p>\n
\"image\"<\/a><\/p>\n
Next follow this order exactly, set the startup type to disabled, then stop the service (this is the same as running the PowerShell to shut down the AppFabric host).<\/p>\n
\"image\"<\/a><\/p>\n
Repeat the above steps on each server in the cache cluster.<\/p>\n
Finally, once you\u2019re done, now you can import the file like below.<\/p>\n
PS C:> Import-CacheClusterConfig C:file.txt<\/font><\/p>\n
<\/font><\/p>\n
Confirm
Are you sure you want to perform this action?
Performing operation “Replace cluster configuration.” on Target “Cluster configuration.”.
[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [S] Suspend  [?] Help (default is “Y”): y<\/font><\/p>\n
If you shut down the cluster properly (like I describe above), your configuration should take at this point.  <\/p>\n
If you see the following error, ensure that you\u2019ve shut down the service on all servers in the cluster (seen above).<\/p>\n
Import-AFCacheClusterConfiguration : ErrorCode<ERRCAdmin001>:SubStatus<ES0001>:Hosts are already running in the
cluster.
At line:1 char:1
+ Import-AFCacheClusterConfiguration C:file.txt
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     + CategoryInfo          : NotSpecified: (:) [Import-AFCacheClusterConfiguration], DataCacheException
     + FullyQualifiedErrorId : ERRCAdmin001,Microsoft.ApplicationServer.Caching.Commands.ImportAFCacheClusterConfigurat
    ionCommand<\/font><\/p>\n
Go back to your services window and set your AppFabric service back to Automatic.  Now all you should need to do is start the cluster, and you\u2019ll be good.<\/p>\n
PS C:> Start-CacheCluster<\/font><\/p>\n
And all your servers should be UP at this point.  You can also check the cluster health with the following.<\/p>\n
PS C:> Get-CacheClusterHealth<\/font><\/p>\n
You can also check the Cache status with the following command.<\/p>\n
PS C:> Get-Cache<\/font><\/p>\n
Don\u2019t forget, you can always see all the valid PowerShell commands using the following.<\/p>\n
PS C:> Get-Help *Cache*<\/font><\/p>\n
I hope this helps others where I was pulling my hair out.<\/p>\n","protected":false},"excerpt":{"rendered":"
I ran into this at a client site recently, and wanted to blog my experience.  I had a number of things not working as expected in the Cache (including Event ID 1000 and Event ID 1026), and at the end of the day, it appears to have boiled down to 2 things.  Firstly, the cache … <\/a><\/p>\n","protected":false},"author":13,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"categories":[7],"tags":[],"acf":[],"yoast_head":"\nFixing the AppFabric Cache Cluster in SharePoint 2013 - Archive<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/regroove.ca\/archive\/2013\/07\/10\/fixing-the-appfabric-cache-cluster-in-sharepoint-2013\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Fixing the AppFabric Cache Cluster in SharePoint 2013 - Archive\" \/>\n<meta property=\"og:description\" content=\"I ran into this at a client site recently, and wanted to blog my experience.  I had a number of things not working as expected in the Cache (including Event ID 1000 and Event ID 1026), and at the end of the day, it appears to have boiled down to 2 things.  Firstly, the cache …\" \/>\n<meta property=\"og:url\" content=\"https:\/\/regroove.ca\/archive\/2013\/07\/10\/fixing-the-appfabric-cache-cluster-in-sharepoint-2013\/\" \/>\n<meta property=\"og:site_name\" content=\"Archive\" \/>\n<meta property=\"article:published_time\" content=\"2013-07-10T22:37:10+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2023-02-24T21:48:42+00:00\" \/>\n<meta property=\"og:image\" content=\"http:\/\/mmman.itgroove.net\/wp-content\/uploads\/mmman\/2013\/07\/image_thumb.png\" \/>\n<meta name=\"author\" content=\"Colin Phillips (Alumni)\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Colin Phillips (Alumni)\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"6 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/regroove.ca\/archive\/2013\/07\/10\/fixing-the-appfabric-cache-cluster-in-sharepoint-2013\/\",\"url\":\"https:\/\/regroove.ca\/archive\/2013\/07\/10\/fixing-the-appfabric-cache-cluster-in-sharepoint-2013\/\",\"name\":\"Fixing the AppFabric Cache Cluster in SharePoint 2013 - Archive\",\"isPartOf\":{\"@id\":\"https:\/\/regroove.ca\/archive\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/regroove.ca\/archive\/2013\/07\/10\/fixing-the-appfabric-cache-cluster-in-sharepoint-2013\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/regroove.ca\/archive\/2013\/07\/10\/fixing-the-appfabric-cache-cluster-in-sharepoint-2013\/#primaryimage\"},\"thumbnailUrl\":\"http:\/\/mmman.itgroove.net\/wp-content\/uploads\/mmman\/2013\/07\/image_thumb.png\",\"datePublished\":\"2013-07-10T22:37:10+00:00\",\"dateModified\":\"2023-02-24T21:48:42+00:00\",\"author\":{\"@id\":\"https:\/\/regroove.ca\/archive\/#\/schema\/person\/adeb0df1cc7a862160be620ca7eace1b\"},\"breadcrumb\":{\"@id\":\"https:\/\/regroove.ca\/archive\/2013\/07\/10\/fixing-the-appfabric-cache-cluster-in-sharepoint-2013\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/regroove.ca\/archive\/2013\/07\/10\/fixing-the-appfabric-cache-cluster-in-sharepoint-2013\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/regroove.ca\/archive\/2013\/07\/10\/fixing-the-appfabric-cache-cluster-in-sharepoint-2013\/#primaryimage\",\"url\":\"http:\/\/mmman.itgroove.net\/wp-content\/uploads\/mmman\/2013\/07\/image_thumb.png\",\"contentUrl\":\"http:\/\/mmman.itgroove.net\/wp-content\/uploads\/mmman\/2013\/07\/image_thumb.png\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/regroove.ca\/archive\/2013\/07\/10\/fixing-the-appfabric-cache-cluster-in-sharepoint-2013\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Blog Archive\",\"item\":\"https:\/\/regroove.ca\/archive\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Fixing the AppFabric Cache Cluster in SharePoint 2013\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/regroove.ca\/archive\/#website\",\"url\":\"https:\/\/regroove.ca\/archive\/\",\"name\":\"Archive\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/regroove.ca\/archive\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/regroove.ca\/archive\/#\/schema\/person\/adeb0df1cc7a862160be620ca7eace1b\",\"name\":\"Colin Phillips (Alumni)\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/regroove.ca\/archive\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/14eeab0d377e9630e0983d9c08911979?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/14eeab0d377e9630e0983d9c08911979?s=96&d=mm&r=g\",\"caption\":\"Colin Phillips (Alumni)\"},\"url\":\"https:\/\/regroove.ca\/archive\/author\/cphillips\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Fixing the AppFabric Cache Cluster in SharePoint 2013 - Archive","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/regroove.ca\/archive\/2013\/07\/10\/fixing-the-appfabric-cache-cluster-in-sharepoint-2013\/","og_locale":"en_US","og_type":"article","og_title":"Fixing the AppFabric Cache Cluster in SharePoint 2013 - Archive","og_description":"I ran into this at a client site recently, and wanted to blog my experience.  I had a number of things not working as expected in the Cache (including Event ID 1000 and Event ID 1026), and at the end of the day, it appears to have boiled down to 2 things.  Firstly, the cache …","og_url":"https:\/\/regroove.ca\/archive\/2013\/07\/10\/fixing-the-appfabric-cache-cluster-in-sharepoint-2013\/","og_site_name":"Archive","article_published_time":"2013-07-10T22:37:10+00:00","article_modified_time":"2023-02-24T21:48:42+00:00","og_image":[{"url":"http:\/\/mmman.itgroove.net\/wp-content\/uploads\/mmman\/2013\/07\/image_thumb.png"}],"author":"Colin Phillips (Alumni)","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Colin Phillips (Alumni)","Est. reading time":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/regroove.ca\/archive\/2013\/07\/10\/fixing-the-appfabric-cache-cluster-in-sharepoint-2013\/","url":"https:\/\/regroove.ca\/archive\/2013\/07\/10\/fixing-the-appfabric-cache-cluster-in-sharepoint-2013\/","name":"Fixing the AppFabric Cache Cluster in SharePoint 2013 - Archive","isPartOf":{"@id":"https:\/\/regroove.ca\/archive\/#website"},"primaryImageOfPage":{"@id":"https:\/\/regroove.ca\/archive\/2013\/07\/10\/fixing-the-appfabric-cache-cluster-in-sharepoint-2013\/#primaryimage"},"image":{"@id":"https:\/\/regroove.ca\/archive\/2013\/07\/10\/fixing-the-appfabric-cache-cluster-in-sharepoint-2013\/#primaryimage"},"thumbnailUrl":"http:\/\/mmman.itgroove.net\/wp-content\/uploads\/mmman\/2013\/07\/image_thumb.png","datePublished":"2013-07-10T22:37:10+00:00","dateModified":"2023-02-24T21:48:42+00:00","author":{"@id":"https:\/\/regroove.ca\/archive\/#\/schema\/person\/adeb0df1cc7a862160be620ca7eace1b"},"breadcrumb":{"@id":"https:\/\/regroove.ca\/archive\/2013\/07\/10\/fixing-the-appfabric-cache-cluster-in-sharepoint-2013\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/regroove.ca\/archive\/2013\/07\/10\/fixing-the-appfabric-cache-cluster-in-sharepoint-2013\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/regroove.ca\/archive\/2013\/07\/10\/fixing-the-appfabric-cache-cluster-in-sharepoint-2013\/#primaryimage","url":"http:\/\/mmman.itgroove.net\/wp-content\/uploads\/mmman\/2013\/07\/image_thumb.png","contentUrl":"http:\/\/mmman.itgroove.net\/wp-content\/uploads\/mmman\/2013\/07\/image_thumb.png"},{"@type":"BreadcrumbList","@id":"https:\/\/regroove.ca\/archive\/2013\/07\/10\/fixing-the-appfabric-cache-cluster-in-sharepoint-2013\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Blog Archive","item":"https:\/\/regroove.ca\/archive\/"},{"@type":"ListItem","position":2,"name":"Fixing the AppFabric Cache Cluster in SharePoint 2013"}]},{"@type":"WebSite","@id":"https:\/\/regroove.ca\/archive\/#website","url":"https:\/\/regroove.ca\/archive\/","name":"Archive","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/regroove.ca\/archive\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/regroove.ca\/archive\/#\/schema\/person\/adeb0df1cc7a862160be620ca7eace1b","name":"Colin Phillips (Alumni)","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/regroove.ca\/archive\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/14eeab0d377e9630e0983d9c08911979?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/14eeab0d377e9630e0983d9c08911979?s=96&d=mm&r=g","caption":"Colin Phillips (Alumni)"},"url":"https:\/\/regroove.ca\/archive\/author\/cphillips\/"}]}},"_links":{"self":[{"href":"https:\/\/regroove.ca\/archive\/wp-json\/wp\/v2\/posts\/923"}],"collection":[{"href":"https:\/\/regroove.ca\/archive\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/regroove.ca\/archive\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/regroove.ca\/archive\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/regroove.ca\/archive\/wp-json\/wp\/v2\/comments?post=923"}],"version-history":[{"count":1,"href":"https:\/\/regroove.ca\/archive\/wp-json\/wp\/v2\/posts\/923\/revisions"}],"predecessor-version":[{"id":1918,"href":"https:\/\/regroove.ca\/archive\/wp-json\/wp\/v2\/posts\/923\/revisions\/1918"}],"wp:attachment":[{"href":"https:\/\/regroove.ca\/archive\/wp-json\/wp\/v2\/media?parent=923"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/regroove.ca\/archive\/wp-json\/wp\/v2\/categories?post=923"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/regroove.ca\/archive\/wp-json\/wp\/v2\/tags?post=923"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}