The product group released the July 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 July 2019 CU will be available at the following Location in a couple of hours:
- KB 4475529 – July 2019 Update for SharePoint Server 2019 (language independent) – This is also a security update!
- There was no language dependent fix released this month. The most recent language dependent fix is KB 4462221 from April 2019
- There was no fix for Office Online Server released this month.
The download for July 2019 CU is available through the following link:
- Download July 2019 Update for SharePoint Server 2019 (language independent) – This is also a security update!
- There was no language dependent fix released this month. The most recent language dependent fix is KB 4462221 from April 2019
- There was no fix for Office Online Server released this month.
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 July 2019 CU Build Number:
Language independent fix: 16.0.10348.12104
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
I installed KB4475529 on a test server yesterday. Now the Central Admin site is coming up blank. I am able to see the Central Admin site from my desktop just not on the server. I have tried several things to resolve it but with no success. Has anyone else experienced this issue?
Permalink
I upgraded my test farm on last Friday and I did not experience this issue.
What I am missing now is the information about my upgrade session shown in Update Status page (CA > Upgrade and Migration > Check upgrade status). It is total blank despite my three update sessions in latest 2 months. I suppose that behind the scene there is similar mechanism that Stefan mentioned in his article “Changes in the TimerJobHistory table maintenance introduced in April 2018 CU for SharePoint 2013”
https://blog.stefan-gossner.com/2018/04/12/changes-in-the-timerjobhistory-table-maintenance-introduced-in-april-2018-cu-for-sharepoint-2013 (the fact that timerjob history is trimmed only for 3 days).
Permalink
I have the same behavior as Ladislav, the Upgrade Sessions will be cleared out by some internal process.
This is here documented as well but I am not sure if the mentioned workaround ist the best and MS supported approach.
https://social.msdn.microsoft.com/Forums/vstudio/en-US/88b196b5-5c7a-44c4-b547-1080a72850ea/adminupgradestatusaspx-page-is-blank-in-sharepoint-2019?forum=sharepointadminlegacy
Permalink
Hello Gabor, you should take a look on latest CU for ShPt Server 2019 (10/2020, KB4486676) and notice the information in “Improvements and fixes” section of related KB article. There is now the possibility to adjust timeframe for retaining upgrade sessions informations (parameter NumberOfDaysToSaveObjects for “job-upgrade-upgradesession-cleanup” timer job).
Permalink
Hello Ladislav,
thank you for this useful information.
Kind Regards,
Gabor
Permalink
Permalink
July CU also adds a new timer job “SecurityTokenServiceApplication” scheduled to run just one time.
Permalink
Are you sure? I went through my TJ list (job definitions) and did not see TJ with this name/title.
Permalink
If the July is the first CU we are installing on SP 2019, do we need to also install the April LOC? If yes, what should be installed first the July Core or April LOC?
Permalink
Hi Barry,
yes April language dependent fix is required as well.
Sequence does not really matter but personally I would start with the installation of the language independent fix.
Cheers,
Stefan