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.
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
Figure 1 – FIPS Error Message
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.
As part of a Domain migration, moved all servers in the SharePoint Farm to a new
One of the SharePoint Application Servers had to be rebuilt and re-added to the Farm. When trying to add the server to the Farm, got the following error:
Error:
Some or all identity references could not be translated.
Solution:
This issue is part of the duplicate SPManagedAccount issue that is blogged here.
But the solution will not work. You wont be able to get into the Service Accounts to change the Farm account to another Service Account.
You will need to rebuild the Central Admin.
Make sure to disconnect all your App Servers and Web Front Ends first before you disconnect the Central Admin server from the Farm.
{Microsoft.SharePoint.SPException: The context has expired and can no longer be used. (Exception from HRESULT: 0x80090317) —> System.Runtime.InteropServices.COMException (0x80090317): The context has expired and can no longer be used. (Exception from HRESULT: 0x80090317)
An IIS Reset on the server will resolve the issue.
1 Giant Nerd 