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.

SP2019 – .net.msmq Error

Installed SharePoint 2019 on one of my servers. Central Administration on my server would not load correctly, and review the Event Viewer for the server i found the below error:

Error:
The protocol ‘net.msmq’ does not have an implementation of HostedTransportConfiguration type registered.

Root Cause:
The IIS Features were not correctly installed on the server.

Resolution:
Run the following command in Powershell to install the correct Features for IIS:

Import-Module Servermanager 

Install-WindowsFeature NET-HTTP-Activation,NET-Non-HTTP-Activ,NET-WCF-Pipe-Activation45,NET-WCF-HTTP-Activation45,Web-Server,Web-WebServer,Web-Common-Http,Web-Static-Content,Web-Default-Doc,Web-Dir-Browsing,Web-Http-Errors,Web-App-Dev,Web-Asp-Net,Web-Asp-Net45,Web-Net-Ext,Web-Net-Ext45,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Health,Web-Http-Logging,Web-Log-Libraries,Web-Request-Monitor,Web-Http-Tracing,Web-Security,Web-Basic-Auth,Web-Windows-Auth,Web-Filtering,Web-Performance,Web-Stat-Compression,Web-Dyn-Compression,Web-Mgmt-Tools,Web-Mgmt-Console,WAS,WAS-Process-Model,WAS-NET-Environment,WAS-Config-APIs,Windows-Identity-Foundation,Xps-Viewer -IncludeManagementTools -verbose - Source D:\sources\sxs

AutoSPInstaller Error – This content database requires upgrade

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.

When creating the Web Application via AutoSPInstaller, the script failed because the content database required to be upgraded.

Error

New-SPWebApplication: This content database requires upgrade and could not be attached in this operation.

AutoSPInstaller Error – Content Database Requires Upgrade

Solution:

When the AutoSPInstaller failed earlier, it had initially created the Content database, but hadn’t finished configuring the database, hence the error.

Delete the Content Database from SQL Server and re-run the AutoSPInstaller script.

AutoSPinstaller Error – Custom File Location is not Accessible

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.

Error:

When running AutoSPInstaller on newly built Windows Server 2019 servers, it failed when trying to run the SharePoint Pre-Requisites.

Error: Custom file location is not accessible

AutoSPInstaller Error – Custom File Location is Not Accessible

Solution:

The SharePoint pre-requisite file were missing from the AutoSPInstaller pre-requisite folder.

Copy all pre-requisites to the folder, and re-run AutoSPInstaller.