Forum Discussion
Cannot get AppFabric installed on Windows Server 2016
- Jan 08, 2018If you're not familiar with it, you didn't use it :) Usually what you'd do is set all your DistCache parameters (service account, memory usage) prior to introducing a 2nd DC host, but if you need to deploy a DC+FE host, you can use that parameter to prevent DC from provisioning.
If DC is truly not working, you need a new farm. Certain things are only provisioned when the first DC host is introduced to the farm.
https://github.com/Apress/deploying-sharepoint-2016/blob/master/Ch03/Ch03/ConfigureDistributedCacheSettings.ps1
Hi Trevor,
So after re-building my farm I was able to get Distributed Cache started by adding my WFE1 server to the farm, configuring Distributed Cache and making sure it was running, then I added my second WFE2 sever and Distributed Cache is started now on both servers.
One issue I noticed, if I run:
Use-CacheCluster
Get-CacheHost
Export-CacheClusterConfig -Path C:\export.txt
The config is different for each server( I bolded the differences):
<hosts>
<host replicationPort="22236" arbitrationPort="22235" clusterPort="22234"
hostId="16089484" size="3096" leadHost="true" account="domain\ch.farmacc"
cacheHostName="AppFabricCachingService" name="11-MySERVER-WFE1.mydomain.com"
cachePort="22233" />
<host replicationPort="22236" arbitrationPort="22235" clusterPort="22234"
hostId="303111937" size="819" leadHost="true" account="domain\ch.ServiceAcc"
cacheHostName="AppFabricCachingService" name="11-MySERVER-WFE2.mydomain.com"
cachePort="22233" />
</hosts>
Should these settings all the same for both servers?