The product group released the September 2019 Cumulative Update for SharePoint Server 2019 product family. SharePoint Server 2019 is patched with a language dependent and a language independent fix.
The KB article for September 2019 CU will be available at the following Location in a couple of hours:
- KB 4475596 – September 2019 Update for SharePoint Server 2019 (language independent) – This is also a security update!
- KB 4464557 – September 2019 Update for SharePoint Server 2019 (language dependent) – This is also a security update!
The download for September 2019 CU is available through the following link:
- Download September 2019 Update for SharePoint Server 2019 (language independent) – This is also a security update!
- Download September 2019 Update for SharePoint Server 2019 (language dependent) – This is also a security update!
Important: It is required to install both fixes (language dependent and independent) to fully patch a SharePoint server. This applies also to servers which do not have language packs installed. The reason is that each SharePoint installation includes a language dependent component together with a language independent component. If additional language packs are added later (only) the language dependent fix has to be applied again.
It is irrelevant which language you pick on the drop down in download center. Even the language dependent fixes are all in the same package for all languages.
After installing the fixes you need to run the SharePoint 2019 Products Configuration Wizard on each machine in the farm. If you prefer to run the command line version psconfig.exe ensure to have a look here for the correct options.
SharePoint 2019 September 2019 CU Build Number:
Language independent fix: 16.0.10350.20000
Language dependent fix: 16.0.10350.20000
Related Links:
- Technet: Updated Product Servicing Policy for SharePoint Server 2019
- Blog: SharePoint Patching demystified
- Blog: Why I prefer PSCONFIGUI.EXE over PSCONFIG.EXE
- Technet: Update Center for Microsoft Office, Office Servers, and Related Products
- Blog: SharePoint Server 2016 Zero-Downtime Patching Demystified (applies also to SharePoint Server 2019)
- Blog: SharePoint does not have a build version. Full Stop.
Permalink
Permalink
Encountered an error on one of our machines, pretty deep and no actual error message / cause:
Action 16.0.26.7 of Microsoft.SharePoint.Upgrade.SPIisWebSiteWssSequence failed.
09/21/2021 17:41:57.22 PSCONFIG (0x18C8) 0x247C SharePoint Foundation Upgrade AddXLMNSAttributeToDependentAssemblies (16.0.26.7) ajywe INFO Adding xlmns attribute to dependent Assemblies in web.config 00000000-0000-0000-0000-000000000000
09/21/2021 17:41:57.22 PSCONFIG (0x18C8) 0x247C SharePoint Foundation Upgrade AddXLMNSAttributeToDependentAssemblies (16.0.26.7) ajywf DEBUG Begin Upgrade() 00000000-0000-0000-0000-000000000000
INFO Microsoft.SharePoint.Administration.SPIisWebSite 00000000-0000-0000-0000-000000000000
09/21/2021 17:41:58.34 PSCONFIG (0x18C8) 0x247C SharePoint Foundation Upgrade SPIisWebSiteWssSequence ajywk ERROR Exception: Filename: \?\C:\Windows\system32\inetsrv\config\applicationHost.config Error: 00000000-0000-0000-0000-000000000000
09/21/2021 17:41:59.04 PSCONFIG (0x18C8) 0x247C SharePoint Foundation Upgrade SPIisWebSiteWssSequence ajywk INFO Microsoft.SharePoint.Administration.SPIisWebSite 00000000-0000-0000-0000-000000000000
09/21/2021 17:41:59.04 PSCONFIG (0x18C8) 0x247C 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, CreateInstanceDelegate
1 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.SPWebConfigIisSiteAction.get_AppWebConfig() at Microsoft.SharePoint.Upgrade.AddXLMNSAttributeToDependentAssemblies.Upgrade() at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade() 00000000-0000-0000-0000-000000000000Permalink
Running it a second time resolved it. (I changed nothing)
Permalink
Thanks for the confirmation! Just a quick update: the problem here did not occur in SharePoint but in Windows Server manager. PSConfig uses Windows Server Manager to read and update IIS settings (e.g. in the callstack above it was using Server Manager to get the path to the web.config file of the IIS website of a SharePoint web application).
Its not clear what went wrong from the callstack but if the issue reoccurs troubleshooting would have to start in Windows Server Manager rather than SharePoint.