SharePoint Server 2016 | Creating Configuration Database failed

Question

Could you suggest a better solution to fix this issue when creating the configuration database from the SharePoint Product Configuration Wizard 2016?

Here is the snapshot of the current error when shooting the query from the cmdlet, we are waiting for the fastest reply from the experts.

Cmdlets:

An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown. Additional exception information: Failed to call GetTypes on assembly Microsoft.Office.TranslationServices, Version=16.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c. Method 'BeginAddFileToCache' in type 'Microsoft.Office.ConversionServices.Local.Environment.CacheStorageAdapter' from assembly 'Microsoft.Office.TranslationServices, Version=16.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' does not have an implementation. Method 'TryGetClusterSpecificSettingNames' in type 'Microsoft.Office.ConversionServices.Local.Environment.ConfigAdapter' from assembly 'Microsoft.Office.TranslationServices, Version=16.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' does not have an implementation. Method not found: 'Void Microsoft.Office.Web.Common.EnvironmentAdapters.IWacExceptionReportingAdapter.ReportClientException(System.String, System.String, System.String, Int32, Int32, System.String, System.String, System.String, Common.OfficeAppType, Common.OfficeAppMode)'. Method not found: 'System.IAsyncResult Microsoft.Office.Web.Common.EnvironmentAdapters.IMainStorage.BeginDocumentWrite(Microsoft.Office.Web.Common.EnvironmentAdapters.BaseDocument, System.IO.Stream, System.String, System.AsyncCallback, System.Object)'. Method 'GetUserFromToken' in type 'Microsoft.Office.ConversionServices.Local.Environment.UserAdapter' from assembly 'Microsoft.Office.TranslationServices, Version=16.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' does not have an implementation.

Regards,
Colleen

Answer 1

@colleen ,

From this similar issue, installing SharePoint server 2016 Feature Pack 1 & 2 will fix the issue.

Since the Feature Pack 2 contains all of the new features that shipped with Feature Pack 1. we don't need to separately install Feature Pack 1 and then install Feature Pack 2.

Feature Pack 2 is included in all future Public Updates for SharePoint Server 2016, beginning with the September 2017 Public Update.

Please install the public update after September 2017 to compare the result.

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

---