January 2023 CU for SharePoint Server 2019 is available for download

17 Comments

1. 

   Emiel
   On 11. January 2023 Permalink

   Hi Stefan, do you have any updates regarding CVE-2023-21743? Don’t know if your blog is also covering this, but just wanted to make you and others aware.

   Reply
   1. 

      Stefan Goßner
      On 11. January 2023 Permalink

      Hi Emil,
      as you can see in the KB article the issue is addressed in Jan 2023 CU.
      Cheers,
      Stefan

      Reply
2. 

   Adeel
   On 16. January 2023 Permalink

   Hi Stefan

   Do you have any updates about the issue with subscription database getting status “Database is too old and upgrade is required” after installation of this CU ?

   I got it first time after installing CU November 2022 (I see people are getting this issue since CU for October 2022). Last time, after installing CU November 2022, we fixed it by granting the sp farm user db_owner on the subscription db it was complaining about. Now we get the same issue again after installing CU for January 2023.

   Any ideas what is causing this issue and how to fix it permanently ?

   Reply
   1. 

      Stefan Goßner
      On 16. January 2023 Permalink

      Hi Adeel,
      we haven’t been able to reproduce this issue inhouse.
      If you have a system that shows that problem I would recommend to open a support case with Microsoft.
      Cheers,
      Stefan

      Reply
      1. 

         Emiel
         On 17. January 2023 Permalink

         Probably running PSCONFIG.exe again will solve it.

         PowerShell command: PSCONFIG.exe -cmd upgrade -inplace b2b -wait -cmd applicationcontent -install -cmd installfeatures -cmd secureresources -cmd services -install

         We had the same issue last updates. First the DB wasn’t available (I forgot the exact message -> Not Responding or something like that). We solved that by granting the farm admin account DB owner permissions on the specific DB as you already did. Then “Database is too old and upgrade is required” appeared. That was solved after running the PSCONFIG.exe again. When it isn’t solved, check the logs of the PSCONFIG which are mostly stored in ..\SharePoint\ULSLog

         Reply
         1. 

            Emiel
            On 17. January 2023 Permalink

            For other DBs
            Get-SPContentDatabase | Upgrade-SPContentDatabase
            Then run psconfig

            Reply
         2. 

            Adeel
            On 17. January 2023 Permalink

            Thanks for the tips. Nothing alarming in the log. Got this. “database SubscriptionSettingsDatabase_ updated, needsRefresh”.

            Running the config wizard without granting db_owner to farm-account did no help. In the end we resolved the issue like the last time we got it: grant sp farm-account db_owner on Subscription Settings db, and run the config wizard again.

            Reply
3. 

   RoelSan
   On 17. January 2023 Permalink

   Any reason to change the build numbering ? Or was the 2nd for DEC a typo?
   Like this is is not possible to easy check the build using F12, response headers MicrosoftSharePointTeamServices: 16.0.0.10394

   JAN23 Language independent fix: 16.0.10394.20021 should be 10394 or 10395
   DEC22 Language independent fix: 16.0.10394.20016 should have been 10393
   DEC22 Language dependent fix: 16.0.10393.20000

   Reply
   1. 

      Stefan Goßner
      On 18. January 2023 Permalink

      Hi Roel,
      the original Dec CU fix was 10393. The rereleased one has 10394.20016 as the work on Jan CU had already started.
      Cheers,
      Stefan

      Reply
      1. 

         admin
         On 20. January 2023 Permalink

         Check on that. But that means we have no way to check using F12 on the actual build of the farm. We are still looking at the issue that the documentID has gone from the InfoPanel.

         Reply
         1. 

            Stefan Goßner
            On 25. January 2023 Permalink

            This method is not reliable as it relies on a custom http header which is set by one one of the packages of the CU.
            We also see frequently that this header is not updated when installing patches.

            Reply
4. 

   Mirko
   On 18. January 2023 Permalink

   Hi Stefan,
   we skipped previous update (december 2022 CU), can you tell me if with this we need to apply the KB4461512 too or just the dependent language from december 2022 CU?

   Reply
   1. 

      Stefan Goßner
      On 18. January 2023 Permalink

      Hi Mirko,
      if you are installing KB5002329 then there is no need to install KB4461512.
      Cheers,
      Stefan

      Reply
      1. 

         Tristan
         On 18. January 2023 Permalink

         Hi Stefan,

         just to be clear, it is safe to install this months CU KB5002329 with last months KB5002310 language dependent Update if we skipped december?

         Thanks and best regards
         Tristan

         Reply
         1. 

            Stefan Goßner
            On 19. January 2023 Permalink

            Hi Tristan,
            Yes that is the correct method.
            Cheers,
            Stefan

            Reply
5. 

   Bikram Pal
   On 26. January 2023 Permalink

   Hi Stefan,

   I have currently installed Oct 22 Patches in my SharePoint 2019 Farm KB 5002278 and KB 5002277. Can you please let me know if the below is the lastest CU Patches available till date and i can directly install them?

   Language Dependent – KB5002310
   Language Independent – KB5002329

   Thanks a ton. I follow your blogs and am very much impressed by your dedication towards your work.

   Reply
   1. 

      Stefan Goßner
      On 26. January 2023 Permalink

      Hi Bikram,
      yes these are the most current patches.
      Install both of them and run the config wizard and your system will be fully patched.
      Cheers,
      Stefan

      Reply