SPConfigWizard fails

Details of the scenario you tried and the problem that is occurring

When installing a CU using SPProductUpdate and executing SPConfigWizard it fails on all SharePoint servers except those with MinRole Search.

When executing PSConfig manually on these servers, it completes successfully.

Any help is aprreciated…

Verbose logs showing the problem

12/17/2020 12:42:31.91 PSCONFIG (0x07A8) 0x0EF4 SharePoint Foundation Upgrade SPIisWebSiteWssSequence ajywk ERROR Action 16.0.13.0 of Microsoft.SharePoint.Upgrade.SPIisWebSiteWssSequence failed. 00000000-0000-0000-0000-000000000000 12/17/2020 12:42:31.91 PSCONFIG (0x07A8) 0x0EF4 SharePoint Foundation Upgrade SPIisWebSiteWssSequence ajywk ERROR Exception: Filename: \?\C:\WINDOWS\system32\inetsrv\config\applicationHost.config Error: 00000000-0000-0000-0000-000000000000 12/17/2020 12:42:31.91 PSCONFIG (0x07A8) 0x0EF4 SharePoint Foundation Upgrade SPIisWebSiteWssSequence ajywk ERROR at Microsoft.Web.Administration.Interop.IAppHostAdminManager.GetAdminSection(String bstrSectionName, String bstrPath) at Microsoft.Web.Administration.Configuration.GetSectionInternal(ConfigurationSection section, String sectionPath, String locationPath) at Microsoft.Web.Administration.ServerManager.SitesSectionCreator() at Microsoft.Web.Administration.Lazy.Initialize[T](T& target, CreateInstanceDelegate1 valueFactory) at Microsoft.Web.Administration.ServerManager.SitesCollectionCreator() at Microsoft.Web.Administration.Lazy.Initialize[T](T& target, CreateInstanceDelegate1 valueFactory) at Microsoft.SharePoint.Administration.SPIisVirtualDirectory…ctor(SPIisWebSite parent, String path) at Microsoft.SharePoint.Upgrade.SPWebConfigIisSiteAction.get_AppWebConfigPath() at Microsoft.SharePoint.Upgrade.RemoveJsonHandlerForVroom.Upgrade() at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade() 00000000-0000-0000-0000-000000000000

12/17/2020 12:42:32 15 ERR An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown. Additional exception information: Action 16.0.13.0 of Microsoft.SharePoint.Upgrade.SPIisWebSiteWssSequence failed. Microsoft.SharePoint.Upgrade.SPUpgradeException: Action 16.0.13.0 of Microsoft.SharePoint.Upgrade.SPIisWebSiteWssSequence failed. —> System.Runtime.InteropServices.COMException: Filename: \?\C:\WINDOWS\system32\inetsrv\config\applicationHost.config Error: at Microsoft.Web.Administration.Interop.IAppHostAdminManager.GetAdminSection(String bstrSectionName, String bstrPath) at Microsoft.Web.Administration.Configuration.GetSectionInternal(ConfigurationSection section, String sectionPath, String locationPath) at Microsoft.Web.Administration.ServerManager.SitesSectionCreator() at Microsoft.Web.Administration.Lazy.Initialize[T](T& target, CreateInstanceDelegate1 valueFactory) at Microsoft.Web.Administration.ServerManager.SitesCollectionCreator() at Microsoft.Web.Administration.Lazy.Initialize[T](T& target, CreateInstanceDelegate1 valueFactory) at Microsoft.SharePoint.Administration.SPIisVirtualDirectory…ctor(SPIisWebSite parent, String path) at Microsoft.SharePoint.Upgrade.SPWebConfigIisSiteAction.get_AppWebConfigPath() at Microsoft.SharePoint.Upgrade.RemoveJsonHandlerForVroom.Upgrade() 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, List1 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, SPTree1 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, SPTree1 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, SPTree1 root, Double rootRatioOrg, SPChronoMeter chronoMeter) at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse) at Microsoft.SharePoint.Upgrade.SPManager.InplaceUpgradeAdministrationWebApplication() at Microsoft.SharePoint.PostSetupConfiguration.UpgradeTask.Run() at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()

The operating system the target node is running

Windows Server 2016

Version of SharePoint that is used (e.g. SharePoint 2016)

SharePoint 2019

Version and build of PowerShell the target node is running

5.1

Version of the DSC module that was used

4.4.0

[ThomasLie]

Hi Yorick,

short update on this:

Currently working with Vlad on this issue, it seems the changes in applicationHost.config (implemented with March 2020 CU) causes the issue. In Windows Eventlog 2 errors came up related to ntdll.dll and clr.dll. Looks like a permission issue, however the account running psconfig remotely is local admin on each of the SharePoint servers…

We’re still investigating, will keep you updated…

[ThomasLie]

I like the idea to add a new parameter… However, this should run before psconfig and should allow to perform a parallel upgrade… Actually, I do have some code for this 😉

Mit freundlichen Grüßen

Thomas Lieftüchter

Lieftüchter IT-Consulting & Hausverwaltung GbR Römerweg 10a 63303 Dreieich - Germany Fon: +49 171.2625166 Email: @.*** Web: http://www.lieftuechter.com/TL

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

---

Von: Yorick Kuijs @.> Gesendet: Thursday, April 29, 2021 10:14:18 PM An: dsccommunity/SharePointDsc @.> Cc: Thomas Lieftüchter @.>; Mention @.> Betreff: Re: [dsccommunity/SharePointDsc] SPConfigWizard fails (#1277)

That is great, then it indeed would be simply adding one line 😄

What exactly is your idea behind upgrading a content database? Attaching a database from a previous SharePoint version (migration)? Or upgrading a database that is running in backwards compatibility mode?

In either case, it would make sense to extend the SPContentDatabase to allow this. Haven’t tested this yet, but I think the resource already upgrades a database from a previous SP version (it uses Mount-SPContentDatabase, which upgrades the DB when needed). For databases in backwards compatibility mode we could add a parameter like PerformUpgrade, which is false by default. If you specify that parameter as true, the resource upgrades the databases when needed.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/dsccommunity/SharePointDsc/issues/1277#issuecomment-829565200, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALR4I4YEHQRWASE2AUHGTITTLG4ZVANCNFSM4VVMQUSA.