共用方式為

Offline SharePoint 2016 Beta 2 and earlier issue, when not using prerequisiteinstaller.exe with offline parameters

  • 發行項

If you are piloting SharePoint 2016 with the Beta 2 release or earlier and run into this issue be aware of the following resolution (this was the last version I tested at the time of this post):

Scenario:

You install the prerequisites manually instead of using the prequisiteinstaller.exe. This avoids a known issue with the way the prequisiteinstaller.exe handles the IIS installation, but can cause a different issue when attempting to create a farm through the SharePoint 2016 Products Configuration Wizard. The following error is displayed in this scenario when the wizard is creating the configuration database:

Configuration Failed

One or more configuration settings failed. Completed configuration settings will not be rolled back. Resolve the problem and run this configuration wizard again. The following contains detailed information about the failure:

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.

The issue can be resolved by removing all versions of WcfDataServices and then reinstalling the WcfDataServices using the prequisiteinstaller.exe with the appropriate parameter and follow any reboot prompts. Below is the command:

prequisiteinstaller.exe /wcfdataservices56:<location of WcfDataServices.exe>

Finally, to move forward clear the previous installation by removing the two created databases on the SQL server and re-attempt creating a farm using the SharePoint 2016 Products Configuration Wizard.

As always no warranty is implied.

Comments

  • Anonymous
    May 06, 2016
    Hi,THANK YOU VERY MUCH!It took me hours to understand what's going on. I can confirm that this issue still exists in the RTM Version.Regards
  • Anonymous
    June 20, 2016
    For the error Microsoft.SharePoint.Upgrade.SPUpgradeException at step 3, this fixed the issue for meThank you
  • Anonymous
    July 04, 2017
    The comment has been removed