cacheHostInfo is null when adding a 2nd Distributed Cache to SharePoint 2019 Min Role

Question

Hi
I have 4 Servers farm in SharePoint 2019 ( 2 created with Application with Search, 2 created with FrontEnd+Disctributed Cache Min Role)
When i adding Second WFE server to the farm i got below error

Server is joined to the SharePoint Farm but Disctributed Cache not working and when i browse the Web application it not working
when i user Use-CacheCluster command it throws error

Answer 1

Hi @adil ,

Based on my research and testing , you can do some troubleshooting:
1,Start AppFabric Caching Service
Started AppFabric Caching Service and add the SPDistributedCacheServiceInstance.

2,IF running the configuration wizard again failed, downloaded and Installed Cumulative Update 7 (KB3092423) for Microsoft AppFabric 1.1 for Windows Server.
Cumulative Update 7 for Microsoft AppFabric 1.1 for Windows Server

Restart the computer after applying this cumulative update package.

After successfully installing the CU package, execute the following PowerShell script to remove the caching service instance:

$SPFarm = Get-SPFarm  
 $cacheClusterName = "SPDistributedCacheCluster_" + $SPFarm.Id.ToString()  
 $cacheClusterManager = [Microsoft.SharePoint.DistributedCaching.Utilities.SPDistributedCacheClusterInfoManager]::Local  
 $cacheClusterInfo = $cacheClusterManager.GetSPDistributedCacheClusterInfo($cacheClusterName);  
 $instanceName ="SPDistributedCacheService Name=AppFabricCachingService"  
 $serviceInstance = Get-SPServiceInstance | ? {($_.Service.Tostring()) -eq $instanceName -and ($_.Server.Name) -eq $env:computername}  
 $serviceInstance.Delete()  

Then run the Configration Wizard again.

Thanks,
Yanli Jiang

===========================================

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

In my case, this was resolved by verifying DNS records. My non-FQDN was routing to an old machine's IP address with a static record. FQDN was routing fine though.

• Cleared out the stagnant record from DNS.
• Ran ipconfig /registerdns on the server with the stagnant record.
• Ran ipconfig /flushdns on the other machines,
• Disconnected the server(s) having this issue from the farm.
• Cleared Config Cache on all servers.

Cache Cluster appears to use the non-FQDN, while most other things during this setup use FQDN.

Hopefully helps someone having this issue!