March 2024 CU for SharePoint Server 2019 is available for download

15 Comments

1. 

   Jonathan Daugherty
   On 21. March 2024 Permalink

   I am curious of why Microsoft does not include the language packs on the CU. I believe that the SQL Server CUs do have them.

   Thanks

   Reply
   1. 

      Stefan Goßner
      On 26. March 2024 Permalink

      Hi Jonathan,
      Microsoft releases language dependent fixes (fixes for the language pack) and language independent fixes with each CU.
      There are situation where no language dependent fixes were implemented in a given month. In this case the most recent previous fix has to be applied.
      In SharePoint Server Subscription Edition the packaging model has been changed and language dependent and independent fixes are now bundled together in a single package.
      Cheers,
      Stefan

      Reply
2. 

   Danny
   On 22. March 2024 Permalink

   When installing this patch do I need to apply the language depended from December 2023 CU together with the independent update for March 2024. We are currently on a lower patch level then December 2023.

   Reply
   1. 

      Stefan Goßner
      On 22. March 2024 Permalink

      Hi Danny, yes that is the required step.

      Reply
3. 

   Alexandre Marfaing
   On 22. March 2024 Permalink

   Hi Stefan,

   I have the error in the ULS not in a SP page described here https://blog.stefan-gossner.com/2021/09/29/trending-issue-_layouts-15-viewlsts-aspx-shows-as-blank-page-in-sp2019-after-installing-september-pu/
   Is it because the language dependent and language independent patch level is different for the specific language ?

   Do I need to do something about it or it’s “normal” ?

   Thanks

   Reply
   1. 

      Stefan Goßner
      On 26. March 2024 Permalink

      Hi Alexandre,
      SharePoint requires to have a match between the language dependent fix and the language independent.
      A version mix is not supported and can lead to a variety of problems.
      If your SharePoint farm has a version mix between language dependent and independent patches you should plan to get this resolved asap.
      Be aware that there are situations where no language dependent fix was released in a given month. In this case the most recent language dependent fix released before has to be applied.
      Cheers,
      Stefan

      Reply
      1. 

         Alexandre Marfaing
         On 2. April 2024 Permalink

         Hi Stefan,

         Thanks for your reply.

         So in this case “Be aware that there are situations where no language dependent fix was released in a given month. In this case the most recent language dependent fix released before has to be applied.” we are supported ?

         Thanks

         Reply
         1. 

            Stefan Goßner
            On 2. April 2024 Permalink

            Yes.

            Reply
4. 

   Robin Jonsson
   On 2. April 2024 Permalink

   Hi!

   Does applying this patch remedy CVE-2023-24955?

   Reply
   1. 

      Stefan Goßner
      On 2. April 2024 Permalink

      Hi Robin,
      yes. The fix for CVE-2023-24955 was first included in the language independent package for May 2023 CU for SharePoint Server 2019.
      As SharePoint fixes are cumulative all future language independent packages also include the fix.
      Cheers,
      Stefan

      Reply
5. 

   Gerard
   On 5. April 2024 Permalink

   Hi Stefan,
   Not really clear regarding the patching but this is the situation we have.
   We have a SP2019 farm with CU Feb 2024 (independent) and CU Dec 2023 (dependent). We want to install CU March 2024, do we need to install the CU Dec 2023 (dependant) again ?

   Reply
   1. 

      Stefan Goßner
      On 5. April 2024 Permalink

      Hi Gerard,
      it is not possible to apply the same fix twice.
      If the language dependent fix from December 2023 CU has already been installed you only have to apply the language independent fix from March 2024.
      Cheers,
      Stefan

      Reply
6. 

   Anis BEN OUADDAI
   On 4. November 2024 Permalink

   Hi Stefan,
   After deploying this cumulative update on a farm that contains custom WSP packages, we have noticed that the timer jobs contained in these packages no longer appear in Central Administration. However, the WSPs seem to be correctly deployed on the farm.

   No custom timer job is visible.

   We have observed that the servers are configured such that the instances of the timer jobs have the following statuses:

   On the Frontend Servers:
   Allow Service Jobs: False
   Allow Content DB Jobs: False

   On the Application Servers:
   Allow Service Jobs: True
   Allow Content DB Jobs: True

   Thank you for looking into this issue.

   Reply
   1. 

      Stefan Goßner
      On 6. November 2024 Permalink

      Hi Anis,
      I have not heard about such an issue and would recommend to open a support case with Microsoft to get this investigated.
      Cheers,
      Stefan

      Reply
7. 

   Anis BEN OUADDAI
   On 8. November 2024 Permalink

   Hi Stefan,

   We have identified the source of the problem. The application of the CU blocked several custom timers, including those natively associated with Nintex workflows.

   We proceeded with the forced reactivation of the features related to these workflows. Subsequently, the timers reappeared in Central Admin and executed correctly.

   Best regards,

   Reply