SharePoint 2016 . PSCONFIG Failed during creation of CONFIG DB
SYMPTOMS
==========
Files that are downloaded from the internet or copied from a Network location are blocked by Windows Operating System SmartScreen Program/ File Security feature.
In some cases, though installation of the blocked file is allowed. However, this may affect the installation or the registration of certain components.
Also after installing the "Microsoft WCF Data Services 5.6" please reboot the server, before running the SharePoint Configuration Wizard. Rebooting the server appears to register the component. Therefore, this issue could be avoided.
WORKAROUND
=============
Workaround 1 ( with Internet Connectivity)
If the server where SharePoint Server 2016 is installed is connected to the internet, then use the PrerequisiteInstaller.exe to download the necessary prerequisites component using the prerequisite installer. “Microsoft WCF Data Services 5.6” component that was installed using the PrerequisiteInstaller.exe is not affected by this issue.
Workaround 2 (without Internet Connectivity)
If the SharePoint 2013 Server is not connected to the internet, then unblock the WCFDataServices.exe file from the File properties. Rerun the executable and click Repair to re-install/repair the component.
After a successful repair of the WCF Data Services component, rerun the SharePoint Configuration Wizard for a successful creation of a New SharePoint Farm.
SYMPTOMS
==========
SharePoint server 2016 is installed but while running the PSCONFIG
we are getting an error while creating the configuration DB. ERR LookupAccountName failed to get the SID for account @@@@@@@@@@@ ERR An exception of type System.ComponentModel.Win32Exception was thrown.
Additional exception information: No mapping between account names and security IDs was done System.ComponentModel.Win32Exception (0x80004005): No mapping between account names
and security IDs was done
at Microsoft.SharePoint.PostSetupConfiguration.Win32Wrapper.NativeMethods.
LookupAccountName(String accountName, String& domainName, SID_NAME_USE& use)
at Microsoft.SharePoint.PostSetupConfiguration.Common.ValidateAccount
(String username, SID_NAME_USE& type) at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.ValidateFarmCreds() ERR Task configdb has failed with an unknown exception ERR Exception: Microsoft.SharePoint.Upgrade.SPUpgradeException:
One or more types failed to load. Please refer to the upgrade log for more details.
CAUSE
=======The issue only appears to occur, if you are downloading the “Microsoft WCF Data Services 5.6” prerequisites component using the direct download (Offline installer) link or if you copy the “Microsoft WCF Data Services 5.6” executable from a network location.
Files that are downloaded from the internet or copied from a Network location are blocked by Windows Operating System SmartScreen Program/ File Security feature.
In some cases, though installation of the blocked file is allowed. However, this may affect the installation or the registration of certain components.
Also after installing the "Microsoft WCF Data Services 5.6" please reboot the server, before running the SharePoint Configuration Wizard. Rebooting the server appears to register the component. Therefore, this issue could be avoided.
WORKAROUND
=============
Workaround 1 ( with Internet Connectivity)
If the server where SharePoint Server 2016 is installed is connected to the internet, then use the PrerequisiteInstaller.exe to download the necessary prerequisites component using the prerequisite installer. “Microsoft WCF Data Services 5.6” component that was installed using the PrerequisiteInstaller.exe is not affected by this issue.
Workaround 2 (without Internet Connectivity)
If the SharePoint 2013 Server is not connected to the internet, then unblock the WCFDataServices.exe file from the File properties. Rerun the executable and click Repair to re-install/repair the component.
After a successful repair of the WCF Data Services component, rerun the SharePoint Configuration Wizard for a successful creation of a New SharePoint Farm.