Problem with November 2023 Update for SharePoint Server Subscription Edition (KB5002527)

Oliver Bär 0 Reputation points
2023-11-17T12:39:17.68+00:00

Hello Community,

I tried several times to run the configuration wizard (also directly in PowerShell) after the installation of the current November 2023 Update for SharePoint Server Subscription Edition (KB5002527) and always got the same error, but I can't find a solution for this.

Here is the log content:

11/15/2023 16:51:25  24  INF            Entering function TaskCommon.TraceToPsconfigLogAndUpgradeManagerLog 
11/15/2023 16:51:25  24  INF              Not spawning off the upgrade job, but rather running upgrade synchronously by calling SPFarm.Local.Upgrade() for inplace upgrade 
11/15/2023 16:51:25  24  INF            Leaving function TaskCommon.TraceToPsconfigLogAndUpgradeManagerLog 
11/15/2023 16:51:42  24  ERR            Task upgrade has failed with an unknown exception  
11/15/2023 16:51:42  24  ERR            Exception: Microsoft.SharePoint.Upgrade.SPUpgradeException: Action 15.0.2.0 of Microsoft.SharePoint.Upgrade.SPIisWebSiteWssSequence failed. ---> System.NullReferenceException: Object reference not set to an instance of an object. 
   at Microsoft.SharePoint.Upgrade.AddDirectInvokeHeader.EnsureCustomHeader(String headerName, String defaultValue) 
   at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade() 
   --- End of inner exception stack trace --- 
   at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade() 
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.RunUpgraders(Object o, List`1 lstClass) 
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse) 
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.ReflexiveUpgrade(Object o, Boolean bRecurse) 
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.RunRecursiveUpgrade(Object o, Boolean bNeedsUpgrade, SPTree`1 root, Double rootRatioOrg, SPChronoMeter chronoMeter) 
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse) 
   at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively) 
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.ReflexiveUpgrade(Object o, Boolean bRecurse) 
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.RunRecursiveUpgrade(Object o, Boolean bNeedsUpgrade, SPTree`1 root, Double rootRatioOrg, SPChronoMeter chronoMeter) 
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse) 
   at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively) 
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.ReflexiveUpgrade(Object o, Boolean bRecurse) 
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.RunRecursiveUpgrade(Object o, Boolean bNeedsUpgrade, SPTree`1 root, Double rootRatioOrg, SPChronoMeter chronoMeter) 
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse) 
   at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively) 
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.ReflexiveUpgrade(Object o, Boolean bRecurse) 
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.RunRecursiveUpgrade(Object o, Boolean bNeedsUpgrade, SPTree`1 root, Double rootRatioOrg, SPChronoMeter chronoMeter) 
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse) 
   at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively) 
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.ReflexiveUpgrade(Object o, Boolean bRecurse) 
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.RunRecursiveUpgrade(Object o, Boolean bNeedsUpgrade, SPTree`1 root, Double rootRatioOrg, SPChronoMeter chronoMeter) 
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse) 
   at Microsoft.SharePoint.PostSetupConfiguration.UpgradeTask.Run() 
   at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()

Can anyone help?

Thank you!

Oliver

SharePoint Server
SharePoint Server
A family of Microsoft on-premises document management and storage systems.
2,059 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Emily Du-MSFT 36,276 Reputation points Microsoft Vendor
    2023-11-20T07:57:50.69+00:00

    The logs you provided show the general error and the specific cause cannot be located. You could try to find more clues in the Event Viewer.

    Please make sure the account which run SharePoint Configuration Wizard is a farm account and it has "dbcreator" and "securityadmin" Server Roles in the SQL.

    And go to windows services, check whether SharePoint Timer Service is running.

    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.