SharePoint 2019 – Check Distributed Cache Memory

When the SharePoint 2019 is installed, the Distributed Cache service automatically allocates the memory required, but in the event that you increase the memory on the servers later down the track, you will need to manually adjust the memory allocation on the Distributed Cache servers.

1.) Get the Distributed Cache cluster.

Use-CacheCluser
Get-AFCacheHostConfiguration -ComputerName <ComputerName> -Cache Port "22233"

2.) Stop the Distributed Cache Service. Repeat on all hosts in the Distrubuted Cache cluster.

Stop-SPDistributedCacheServiceInstance

3.) Increase the memory allocation. Repeat on all hosts in the cluster.

Update-SPDistributedCacheSize -CacheSizeInMB <#MB>

4.) Restart the Distributed Cache Service

$InstanceName = "SPDistributedCacheService Name=AppFabricCachingService"
$ServiceInstance = Get-SPServiceInstance | ? { ($_.Service.ToString() ) -eq $InstanceName -and ($_.server.name) -eq $env:COMPUTERNAME}
ServiceInstance.Provision()

Repeat on all servers in the Cluster.

What is the Distributed Cache Service in SharePoint?

It is a service that provides an additional caching mechanism (introduced in SharPoint 2013 & later) to support SharePoint features like Object Cache, BLOB Cache & Page Output Cache.

It enabld quick data retrieval without any dependency on SQL Server databases, as it stores everything in memory, aka cache.

AutoSPInstaller – XML and Script Version Mismatch

AutoSPInstaller is a great project that facilitates Automated SharePoint installation including Sharepoint 2010, 2013, 2016 and 2019.

Auto SP Installer provides a powerful way to deploy and configure a
single-server development environment to multiple-server SharePoint farm.

There is a chance when running the AutoSPInstaller scripts, you will get a warning that the XML and script version is mismatched.

AutoSPInstaller – Config Warning

In the XML file, by default, the version of the XML header will be 3.99.70. A warning will appear to advise that the version of the XML does not match the script.

AutoSPInstaller – Version Mismatch

Resolution:

Ignore the Warning as this is just that, a warning. This does not affect the function of the script.

SharePoint 2019 – Windows AppFabric Is Not Correctly Configured

Installing SharePoint 2019 on a Development Server.

SP2019 – App Fabric Error – Not Correctly Configured

The cause of this error is that i installed Windows Server AppFabric manually (click the executable) instead of using the SharePoint 2019 Pre-Requisites installer.

Solution:

1.) Uninstall program from Control Panel > Programs.

2.) Reboot the server.

3.) Open Command Prompt as an Administrator.

4.) Run the following command to install the App Fabric the correct way.

Start-Process "C:\SharePoint2019\PrerequisiteInstaller.exe" -ArgumentList /AppFabric:`"C:\SharePoint2019\PrerequisiteInstallerFiles\WindowsServerAppFabricSetup_x64.exe`" `

SP2019 – App Fabric Install

SP2019 – App Fabric License Terms

SP2019 – App Fabric Extracting Files

SP2019 – App Fabric Install Complete

5.) Restart the server.

SharePoint 2019 Database Requirements

Was recently reviewing the SharePoint 2019 requirements when I noticed a change in the requirements compared to previous versions of SharePoint.

The change is that as long as SQL Server version supports the Database Compatibility Level 130, then you can use whatever version you require.

Source – https://docs.microsoft.com/en-us/sharepoint/install/hardware-and-software-requirements-2019

This helps with migrations and upgrades when certain versions of SQL Server go end of life.

This is perfect for people like my client who are running SharePoint 2010 on SQL Server 2008 R2. SQL Server 2008 R2 has gone end of life from extended support back in July 2019, so when we migrate to SharePoint 2019 we can provide rolling SQL Server upgrades without having to perform a complete SharePoint migration just because SQL Server is end of life.