SOLVED

Distributed Cache crashing under SharePoint 2019 running on WS2019

Occasional Contributor

Happy New Year!

I'm having some trouble setting up my new Lab environment using the latest and greatest technologies:

Windows Server 2019, SQL 2017 and SharePoint 2019 on three different Hyper-V VMs. All components are up to date.

I'm quite early in the process only the Farm was created using PowerShell. I documented the whole thing on twitter https://twitter.com/sassdawe/status/1081670767576838145 

 

I've tried the all usual steps to fix it, Remove-SPDistributedCacheServiceInstance etc. Validated everything from here: http://sharepoint-blog.com/appfabric-event-id-1000-and-event-id-1026-with-sharepoint-2013/ but nothing worked.

 

I'm kindly ask you, any ideas?

Thanks

 

5 Replies
best response confirmed by sassdawe (Occasional Contributor)
Solution

Adding @Mike Lee (BOSTON). Try running this:

 

Use-CacheCluster

# Stop the Caching Services on all cache hosts in the cluster.
stop-cachecluster

# Export existing cache cluster configuration
Export-cacheclusterconfig -file c:\temp\appfabconfig.txt

# make a copy of "appfabconfig.txt" and name it "appfabconfig2.txt"
# Edit appfabconfig2.txt
# Change <caches partitionCount="256" to "128"

# Import the changes.
Import-cacheclusterconfig c:\temp\appfabconfig2.txt

# Start the Caching Services on all cache hosts in the cluster.
Start-cachecluster

# Stop the Caching Services on all cache hosts in the cluster.
stop-cachecluster

# Import the original settings
Import-cacheclusterconfig c:\temp\appfabconfig.txt

# Start the Caching Services on all cache hosts in the cluster.
Start-cachecluster

That looks good!  Please let us know if those changes fix the issue.

 

Thanks,

Mike

 

Thanks @Trevor Seward, this script did the trick. 

The service is stable for 60+ minutes now.

When I am searching to solve a problem in SharePoint, Before reading the answers I look for your profile picture. Because I am always sure that if you answered the question, that means my problem is definitely solved.
That's nice of you to say, thank you!

By the way, this bug is fixed in SharePoint Server Subscription Edition Preview!