次の方法で共有

Sharepoint 2016 : The CU upgrade fails during PSconfig execution

  • [アーティクル]

Symptom:

The SharePoint configuration wizard fails with the following message after the installation of CU / Language pack / security patch etc

 Failed to upgrade SharePoint Products.

This is a critical task. You have to fix the failures before you can continue. Follow this link for more information about how to troubleshoot upgrade failures: https://go.microsoft.com/fwlink/?LinkId=259653

An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException was thrown. Additional exception information:

Feature upgrade action 'CustomUpgradeAction.AddSwitchField' threw an exception upgrading Feature 'CustomTiles' (Id: 15/'68642d38-a556-4384-888c-082844fbf224') in WebApplication 'SharePoint - 80: List |0

Feature upgrade incomplete for Feature 'CustomTiles' (Id: 15/'68642d38-a556-4384-888c-082844fbf224') in WebApplication 'SharePoint - 80. Exception: List |0

Upgrade completed with errors. Review the upgrade log file located in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\16\LOGS\Upgrade-20180220-162221-353-19435b7e3e40479183e3ca8d9f3155fa.log. The number of errors and warnings is listed

To diagnose the problem, review the application event log and the configuration log file located at:C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\16\LOGS\PSCDiagnostics_2_20_2018_16_22_10_998_970437191.log

The behavior is observed when the web application is created with farm build level 16.0.4456.1000

Resolution:

The corrective action to perform is to Enable the custom tiles feature to force the creation of the Custom tiles list to move past this road block in running PSConfig.

Enable-spfeature -URL https://webappurl -identity "68642d38-a556-4384-888c-082844fbf224"

 

POST BY : Shiva Prasad [MSFT]

Comments

  • Anonymous
    May 16, 2018
    hi Shiva,i also run into a similar error because i dismounted all of my Content Dbs before running psconfig. i had the error with message no root site Collection is available. it is logically that you have no Root SC when dismounting Content dbs.i solved it with workaround to have run psconfig three times on every SP Server. Not Good as i suppose!