SharePoint 2016: Failed to create the configuration database. An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown

In this article, I will solve the below SharePoint 2016 Configuration Wizard issue

Failed to create the configuration database.
An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown. Additional exception information: One or more types failed to load. Please refer to the upgrade log for more details.


Scenario

Unfortunately, I didn’t have an internet connection on the SharePoint Servers to can install the SharePoint 2016 Prerequisites over the internet automatically.

So I went to install the SharePoint 2016 Prerequisites offline that has been installed properly and the SharePoint installation has been started without any complaint.

Once the SharePoint 2016 installation is finished, I tried to run the SharePoint 2016 Configuration wizard to configure the SharePoint 2016 farm.

The SharePoint 2016 Configuration wizard has been started and passed all the pre-steps properly. but when it started to create the SharePoint configuration database (specifically in step 3), it has been failed with the below error.

Failed to create the configuration database.
An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown. Additional exception information: One or more types failed to load. Please refer to the upgrade log for more details.

Failed to create the configuration database in SharePoint 2016 - Failed to create the configuration database An exception of type Microsoft SharePoint Upgrade SPUpgradeException was thrown

I have checked the log and event viewer as shown below. but it was not helpful!!


Failed to create the configuration database.
An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown. Additional exception information: One or more types failed to load. Please refer to the upgrade log for more details.
Microsoft.SharePoint.Upgrade.SPUpgradeException: One or more types failed to load. Please refer to the upgrade log for more details.
at Microsoft.SharePoint.Upgrade.SPActionSequence.LoadUpgradeActions()
at Microsoft.SharePoint.Upgrade.SPActionSequence.get_Actions()
at Microsoft.SharePoint.Upgrade.SPActionSequence.get_ActionsInternal()
at Microsoft.SharePoint.Upgrade.SPUtility.GetLatestTargetSchemaVersionBeforeMajorVersion(Type typeActionSequence, Int32 majorVer)
at Microsoft.SharePoint.Upgrade.SPSiteSequence.get_PreviousTargetSchemaVersion()
at Microsoft.SharePoint.Upgrade.SPUpgradeSession.PopulateSequencesTable(StringBuilder sqlstr, Boolean siteSequence)
at Microsoft.SharePoint.Upgrade.SPUpgradeSession.ConstructSiteNeedsUpgradeQuery(Guid siteId)
at Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence.GetSiteNeedsUpgrade(SPUpgradeSession session, SPContentDatabase database, Dictionary`2& dictSitesNeedUpgrade, Dictionary`2& dictSitesNeedFeatureUpgrade)
at Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence.AddNextLevelObjects()
at Microsoft.SharePoint.Upgrade.SPHierarchyManager.Grow(SPTree`1 root, Boolean bRecursing, SPDelegateManager delegateManager)
at Microsoft.SharePoint.Upgrade.SPHierarchyManager.Grow(SPTree`1 root, SPDelegateManager delegateManager)
at Microsoft.SharePoint.Upgrade.SPUpgradeSession.NeedsUpgrade(Object o, Boolean bRecurse)
at Microsoft.SharePoint.Upgrade.SPUpgradeSession.ReflexiveNeedsUpgrade(Object o, Boolean bRecurse)
at Microsoft.SharePoint.Upgrade.SPUpgradeSession.NeedsUpgrade(Object o, Boolean bRecurse)
at Microsoft.SharePoint.Upgrade.SPUpgradeSession.ReflexiveNeedsUpgrade(Object o, Boolean bRecurse)
at Microsoft.SharePoint.Upgrade.SPUpgradeSession.NeedsUpgrade(Object o, Boolean bRecurse)
at Microsoft.SharePoint.Upgrade.SPUpgradeSession.ReflexiveNeedsUpgrade(Object o, Boolean bRecurse)
at Microsoft.SharePoint.Upgrade.SPUpgradeSession.NeedsUpgrade(Object o, Boolean bRecurse)
at Microsoft.SharePoint.Upgrade.SPUpgradeSession.ReflexiveNeedsUpgrade(Object o, Boolean bRecurse)
at Microsoft.SharePoint.Upgrade.SPUpgradeSession.NeedsUpgrade(Object o, Boolean bRecurse)
at Microsoft.SharePoint.Administration.SPServerProductInfo.DetectLocalUpgradeStatus()
at Microsoft.SharePoint.Administration.SPServerProductInfo.DetectLocalProductVersions(SPProductVersions prodVer)
at Microsoft.SharePoint.Administration.SPServerProductInfo.UpdateProductInfoInDatabase(Guid serverGuid)
at Microsoft.SharePoint.Administration.SPFarm.Join(Boolean skipRegisterAsDistributedCacheHost, Nullable`1 serverRole)
at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.CreateOrConnectConfigDb()
at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.Run()
at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()

I also checked the database server to make sure that the issue is not related to the Farm Account permission (DBcreator, SecurityAdmin). but I have noticed that the SharePoint Config database and Admin Content database have been created properly!

I have the below environment.

  • SharePoint Server 2016.
  • Windows Server 2012 R2.
  • SQL Server 2014 SP2.

Cause

The WCF Data Services 5.6 tool is not installed properly.

Note: I have tried to uninstall it and install it again, unfortunately, the issue still persists and the SharePoint Configuration wizard has been failed to create the SharePoint Config Database.


Solution

Failed to create the configuration database in SharePoint 2016

You have two option to overcome “Failed to create the configuration database.” SharePoint 2016 issue:

  1. You must have internet connection on the SharePoint Server to Install and download the SharePoint 2016 prerequisites online using “prerequisiteInstaller.exe” that will automatically install these prerequisites without any issue.
  2. If no way to use internet on the SharePoint Servers, so you must let “prerequisiteInstaller.exe” to install WCF Data Services 5.6 tool offline as the following:
Offline Install for WCF Data Services 5.6 tool
  • Download WCF Data Services 5.6 tool.
  • Specify its downloaded Path and copy it.
  • Open CMD as Administrator.
  • Navigate to the SharePoint media folder.
  • Type the below cmdlet

prequisiteinstaller.exe /wcfdataservices56:"WCF Services Tool Path"

Example

Consider the SharePoint 2016 Media has been mounted to the D:\ volume, and WCF Services Tool is located in “C:\Software\WCFDataServices.exe“, so the command should be

D:\prequisiteinstaller.exe /wcfdataservices56:"C:\Software\WCFDataServices.exe"

SHarePoint 2016: Additional exception information One or more types failed to load

  • You will note that the SharePoint 2016 prerequisites wizard has been started.
  • Click Next to install the WCF Data Services 5.6 tool.

Install WCF Data Services 5.6 tool in SharePoint 2016

  • The WCF Data Services 5.6 tool should be now installed successfully.

An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown

  • Try now to run the SharePoint 2016 Configuration wizard that should be now completed properly.

Install and Configure Project Server 2016 Completed


Applies To
  • SharePoint 2016.
  • SharePoint 2013.
Conclusion

In this article, I have solved Failed to create the configuration database.
An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown In SharePoint 2016.

See Also

Install SharePoint 2016 Step By Step.

 

 

Advertisements

2 thoughts on “SharePoint 2016: Failed to create the configuration database. An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown

  1. Awesome, you saved my day , I spent about 4 hours to install it, your solution helped me to solve my issue, thanks for sharing,

    Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

w

Connecting to %s