SOLVED
Home

Distributed Cache crashing under SharePoint 2019 running on WS2019

%3CLINGO-SUB%20id%3D%22lingo-sub-314254%22%20slang%3D%22en-US%22%3EDistributed%20Cache%20crashing%20under%20SharePoint%202019%20running%20on%20WS2019%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-314254%22%20slang%3D%22en-US%22%3E%3CP%3EHappy%20New%20Year!%3C%2FP%3E%3CP%3EI'm%20having%20some%20trouble%20setting%20up%20my%20new%20Lab%20environment%20using%20the%20latest%20and%20greatest%20technologies%3A%3C%2FP%3E%3CP%3EWindows%20Server%202019%2C%20SQL%202017%20and%20SharePoint%202019%20on%20three%20different%20Hyper-V%20VMs.%20All%20components%20are%20up%20to%20date.%3C%2FP%3E%3CP%3EI'm%20quite%20early%20in%20the%20process%20only%20the%20Farm%20was%20created%20using%20PowerShell.%20I%20documented%20the%20whole%20thing%20on%20twitter%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftwitter.com%2Fsassdawe%2Fstatus%2F1081670767576838145%26nbsp%3B%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Ftwitter.com%2Fsassdawe%2Fstatus%2F1081670767576838145%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20tried%20the%20all%20usual%20steps%20to%20fix%20it%2C%26nbsp%3BRemove-SPDistributedCacheServiceInstance%20etc.%20Validated%20everything%20from%20here%3A%20%3CA%20href%3D%22http%3A%2F%2Fsharepoint-blog.com%2Fappfabric-event-id-1000-and-event-id-1026-with-sharepoint-2013%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fsharepoint-blog.com%2Fappfabric-event-id-1000-and-event-id-1026-with-sharepoint-2013%2F%3C%2FA%3E%20but%20nothing%20worked.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20kindly%20ask%20you%2C%20any%20ideas%3F%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-314254%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3E2019%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAdmin%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Ecrash%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EDistributed%20Cache%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-319683%22%20slang%3D%22en-US%22%3ERe%3A%20Distributed%20Cache%20crashing%20under%20SharePoint%202019%20running%20on%20WS2019%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-319683%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F130%22%20target%3D%22_blank%22%3E%40Trevor%20Seward%3C%2FA%3E%2C%26nbsp%3Bthis%20script%20did%20the%20trick.%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20service%20is%20stable%20for%2060%2B%20minutes%20now.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-314655%22%20slang%3D%22en-US%22%3ERe%3A%20Distributed%20Cache%20crashing%20under%20SharePoint%202019%20running%20on%20WS2019%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-314655%22%20slang%3D%22en-US%22%3E%3CP%3EThat%20looks%20good!%26nbsp%3B%20Please%20let%20us%20know%20if%20those%20changes%20fix%20the%20issue.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%2C%3C%2FP%3E%0A%3CP%3EMike%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-314651%22%20slang%3D%22en-US%22%3ERe%3A%20Distributed%20Cache%20crashing%20under%20SharePoint%202019%20running%20on%20WS2019%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-314651%22%20slang%3D%22en-US%22%3E%3CP%3EAdding%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F96057%22%20target%3D%22_blank%22%3E%40Mike%20Lee%20(BOSTON)%3C%2FA%3E.%20Try%20running%20this%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CPRE%3EUse-CacheCluster%0A%0A%23%20Stop%20the%20Caching%20Services%20on%20all%20cache%20hosts%20in%20the%20cluster.%0Astop-cachecluster%0A%0A%23%20Export%20existing%20cache%20cluster%20configuration%0AExport-cacheclusterconfig%20-file%20c%3A%5Ctemp%5Cappfabconfig.txt%0A%0A%23%20make%20a%20copy%20of%20%22appfabconfig.txt%22%20and%20name%20it%20%22appfabconfig2.txt%22%0A%23%20Edit%20appfabconfig2.txt%0A%23%20Change%20%26lt%3Bcaches%20partitionCount%3D%22256%22%20to%20%22128%22%0A%0A%23%20Import%20the%20changes.%0AImport-cacheclusterconfig%20c%3A%5Ctemp%5Cappfabconfig2.txt%0A%0A%23%20Start%20the%20Caching%20Services%20on%20all%20cache%20hosts%20in%20the%20cluster.%0AStart-cachecluster%0A%0A%23%20Stop%20the%20Caching%20Services%20on%20all%20cache%20hosts%20in%20the%20cluster.%0Astop-cachecluster%0A%0A%23%20Import%20the%20original%20settings%0AImport-cacheclusterconfig%20c%3A%5Ctemp%5Cappfabconfig.txt%0A%0A%23%20Start%20the%20Caching%20Services%20on%20all%20cache%20hosts%20in%20the%20cluster.%0AStart-cachecluster%3C%2FPRE%3E%3C%2FLINGO-BODY%3E
Dávid Sass
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

 

3 Replies
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

 

Highlighted

Thanks @Trevor Seward, this script did the trick. 

The service is stable for 60+ minutes now.

Related Conversations