Forum Discussion
Cannot get AppFabric installed on Windows Server 2016
- If 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.
I'm not familiar with -SkipRegisterAsDistributedCacheHost. Are you saying I should have used that?
Also, for a new VM, can I try adding it to the existing farm or does it have to be a completely new Farm?
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.
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?
Hi Trevor,
When trying the PowerShell to update Distributed Cache, I get this error:
Update-SPDistributedCacheSize : Error occurred while performing the operation on host MYSERVER-FE1:22233 :
ErrorCode<ERRCAdmin003>:SubStatus<ES0001>:Time-out occurred on net.tcp://MYSERVER-FE1.mydomain:22233.- My only recommendations would be to set the memory value appropriately for your environment and swap out the service account for a non-privileged account.
https://github.com/Apress/deploying-sharepoint-2016/blob/master/Ch03/Ch03/ConfigureDistributedCacheSettings.ps1 Ok thanks alot for your help here....I think we'll have to give that a try. I'll come back and reply once it's done.
Do you have any advice on how to properly set up the DistCache parameters prior to adding my second FE server?
- If you do Step #4, you don't need to use SkipRegister... and can use the Config Wizard for all 4 servers.
Ok, so just to be clear...I would do this?:
- Create new farm
- Add my 2 "Application with Search" servers using SPConfig
- Add my first "Front-end with DC" using SPConfig
- Configure DC cache, make sure it's running etc.
- Then add Second "Front-end with DC" using PowerShell script, similar to this: https://thesharepointfarm.com/2014/06/configuring-sharepoint-powershell/
In my PowerShell script, where do I put the -SkipRegisterAsDistributedCacheHost line?