SP 2019 Setup -- Issue with distributed cache service setup

Question

We are setting up an SP 2019 Farm in AWS with 6 server Farm (2 Web, 2 App, 2 Search servers in two AZs, one set in each AZ)

while setting up distributed cache service on web server 2, the service is not shown after this service is setup using power shell , App fabric service is also not seen in the services after running the power shell , tried multiple ways to resolve this issue (including reinstalling App Fabric service) and could not resolve this issue, Checked ULS and Event viewer logs, no related errors have been logged.

distributed cache service is running as expected on Web server1 with out any issue, only having issue on Web server 2.

Appreciate your inputs if any one has faced similar issue.

Can we try uninstalling and reinstalling SP on this Web Server?

Answer 1

Hi @Rahul Siripragada ,

To narrow down this issue, I have something to confirm with you. Did you get any error mesages after running Add-SPDistributedCacheServiceInstance? You have to run below PowerShell commands after adding SharePoint Distributed Cache Service Instance to start the service.

$instanceName ="SPDistributedCacheService Name=AppFabricCachingService"  
$serviceInstance = Get-SPServiceInstance | ? {($_.service.tostring()) -eq $instanceName -and ($_.server.name) -eq $env:computername}  
$serviceInstance.Provision()  

Have a try to run below PowerShell commands, will the web server 2 be displayed in the return values? Or will any error message appear?

Use-CacheCluster     
Get-CacheHost  

The Distributed Cache depends on Windows Server AppFabric as a prerequisite. Do you mean that AppFabric Caching Service is missing in the Services?

Last but not least, reboot your server may give a favor to you. You can share here your SharePoint Server build number or install the latest CU if the issue still persists.

---

If an Answer is helpful, please click "Accept Answer" and upvote it.
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

OS used in windows server 2019 R2, we have tried reinstalling APp fabric and could not resolve this issue, this issue has been reported to Microsoft Premier support and concluded that this issue is because the necessary ports are not opened. Working with the network team to open the ports, will update once the ports are opened and reconfiguration is successful.
@Allen Xu_MSFT thank you very much for your inputs, appreciate your inputs.