Sharepoint – 1 Giant Nerd

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.

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.

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`" `

5.) Restart the server.

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

Error: This Implementation is not part of the Windows Platform FIPS validate cryptographic algorithms

Error:

When trying to access my newly provision SharePoint 2019 central Administration Site, encounter the following error:

This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms

Root Cause:

FIPS stands for “Federal Information Processing Standards.” It’s a set of government standards that define how certain things are used in the government–for example, encryption algorithms. FIPS defines certain specific encryption methods that can be used, as well as methods for generating encryption keys. It’s published by the National Institute of Standards and Technology, or NIST.

The setting in Windows complies with the US government FIPS 140 standard. When it’s enabled, it forces Windows to only use FIPS-validated encryption schemes and advises applications to do so, as well.

“FIPS mode” doesn’t make Windows more secure. It just blocks access to newer cryptography schemes that haven’t been FIPS-validated. That means it won’t be able to use new encryption schemes, or faster ways of using the same encryption schemes. In other words, it makes your computer slower, less functional, and arguably less secure.

Reference: https://www.howtogeek.com/245859/why-you-shouldnt-enable-fips-compliant-encryption-on-windows/

Solution:

The FIPS compliant setting is forced via Group Policy.

Open Group Policy and navigate to:
Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options

Set the setting System cryptography: Use FIPS compliant algorithms for encryption, hashing and signing to Disabled.

Run a gpupdate /force on the server and you will now be able to access Central Admin (or whatever website you had this issue).

Additional information can be found here – https://docs.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/system-cryptography-use-fips-compliant-algorithms-for-encryption-hashing-and-signing

AutoSPInstaller Error – Insufficient system memory in resource pool ‘default’

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:

Deploying Web Application via AutoSPInstaller when the script failed

Error: New-SPWebApplication: There is insufficient system memory in resource pool ‘default’ to run this query.

AutoSPInstaller – Error – Insufficient system memory

Don’t be fooled, this is a SQL Server related error, and not IIS.

If you open SQL Server Management Studio on your database server, and open the Logs, you will see the following errors:

AutoSPInstaller – Error – SQL Server Error Message

Solution:

Open SQL Server Management Studio > Right Click on the Instance > Select Properties > Select Memory tab.

AutoSPInstaller – Error – SQL Maximum Server Memory

You will see that the Maximum Server Memory is 512MB which is way too low.

Set the Maximum Memory as at least 2GB shy of the total server memory, e.g 14GB if total server memory is 16GB.

AutoSPInstaller – Error – Set SQL Maximum Server Memory

Restart the SQL Server Service, and you wont have this issue again.