January 2023 CU for SharePoint Server 2019 is available for download

- - 27 Comments

The product group released the January 2023 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 January 2023 CU will be available at the following Location in a couple of hours:

  • KB 5002329 – January 2023 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 5002310 from December 2022 CU.

The downloads for January 2023 CU are available through the following links:

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.

Please ensure to have a look at the SharePoint Patching Best Practices before applying new fixes.

 
SharePoint 2019 January 2023 CU Build Number:

Language independent fix: 16.0.10394.20021

 
Related Links:

27 Comments


  1. 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. Hi Emil,
      as you can see in the KB article the issue is addressed in Jan 2023 CU.
      Cheers,
      Stefan

      Reply

  2. 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. 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. 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. For other DBs
          Get-SPContentDatabase | Upgrade-SPContentDatabase
          Then run psconfig

          Reply

        2. 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. 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. 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. 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. 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. 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. Hi Mirko,
      if you are installing KB5002329 then there is no need to install KB4461512.
      Cheers,
      Stefan

      Reply

      1. 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. Hi Tristan,
          Yes that is the correct method.
          Cheers,
          Stefan

          Reply

  5. 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. 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

  6. Has anyone else received errors with distributed cache since this update? Had an issue reported today and when checking the logs, it looks like there has been an issue with my DC since the update:

    Token Cache: Failed to initialize SPDistributedSecurityTokenCache Exception: ‘Microsoft.ApplicationServer.Caching.DataCacheException: ErrorCode:SubStatus:There is a temporary failure. Please retry later. (One or more specified cache servers are unavailable, which could be caused by busy network or servers. For on-premises cache clusters, also verify the following conditions. Ensure that security permission has been granted for this client account, and check that the AppFabric Caching Service is allowed through the firewall on all cache hosts.

    Reply

    1. Hi,
      please verify if the WSS_WPG group has permission on the following registry key:
      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurePipeServers\winreg
      Cheers,
      Stefan

      Reply

      1. Thank you, I will give that a try. Just on the Sharepoint servers correct?

        Reply

    2. Hello! We have also experienced problems with distibuted cache after the update. In our case the timer jobs are failing with error:
      The Execute method of job definition Microsoft.Office.Server.UserProfiles.FeedCacheRepopulationJob (ID 6802b777-fe99-498d-b425-370fccf95fee) threw an exception. More information is included below. Unexpected exception in FeedCacheService.IsRepopulationNeeded: Unable to create a DataCache. SPDistributedCache is probably down… (Correlation=efae8da0-efcf-10b2-a346-14e48612c4bc) The Execute method of job definition Microsoft.Office.Server.UserProfiles.LMTRepopulationJob (ID 5045a683-2272-43ba-983e-a39e057359a7) threw an exception. More information is included below. Unexpected exception in FeedCacheService.IsRepopulationNeeded: Unable to create a DataCache. SPDistributedCache is probably down… (Correlation=9bae8da0-1fbe-10b2-a346-16c05d3e0b6a) Both errors have the same event id : 6398

      I have made a support request and we have been trying to fix things with support engineer fot the past couple of weeks but nothing seems to repair the situation.

      Reply

      1. This is what my issue was as well. Everything was working fine until this update, then my issue above was caused by the DistributedCache.exe crashing constantly on our WFE, which threw the APP server off as well, Get-CacheHost returned “UNKNOWN” for both server until I rebooted the servers. Since that reboot, both servers are showing as “UP” but i still have something strange going on where locally they show up, but remotely they show “UNKNOWN”. Its not networking related, its something with the service I believe. But for the moment, everything has been functional on the site for the users. Had a ton of random issues before the reboot.

        I was referencing this guide for 2013, even though im on 2019….it seems like recreating the service might fix it, however with the retiring of 24×7 support from VLSC, im in support limbo right now 🙁 and i dont want to risk it further.

        https://aarohblah.blogspot.com/2016/01/troubleshooting-and-fixing-distributed.html

        Reply

        1. Only place we have noticed (so far) to malfunction for users is mysite newsfeed which shows general error message telling that the newsfeed (which is now empty) is being populated.

          We have tried to solve the problem in several ways without any success and breaking it further is not an option…

          Reply

      2. I’m also having errors with the user profile feed cache repopulation job, on SP2016. I have an ongoing support case open however it’s yet to be resolved. The error is:

        FeedCacheService.IsRepopulationNeeded: Unable to create a DataCache. SPDistributedCache is probably down, with event ID 6398 being logged. I’ve tried the wss_grp permissions as well as removing/re-adding the cache service & resetting the config cache on all the hosts with support.

        This job failing isn’t causing me much trouble as we don’t use mysite newsfeeds, but I’m concerned it could be a larger issue with the patch.

        Reply

        1. It seems we have exatly the same problem and situation, on SP2019.

          Permissions have been checked, Distributed Cache has been fine-tuned, SPDistributedCacheServiceInstance has repaired, removed and re-added, App Fabric has been even reinstalled but no effect, timer jobs keep failing.

          I am also concerned that the mysite newsfeed are only the tip of the iceberg because distributed cache affects so many places in SharePoint…

          Reply

    3. Hello,
      We’re seeing similar errors in our production farm. It started about 2 weeks ago, and seems to be breaking OneNote client app sync. When a user opens OneNote file from SharePoint in a local client, sync works initially. After some time, sync breaks and asks for username/password. We have looked at OneNote issue as well, but given that OneNote is dependent on DistributedCache, wondering if anyone else is seeing similar errors.

      Reply

  7. Thank you for your blog explaining about CU , it was really useful , because i had to install and config Sharepoint 2016 and 2019 and work well !

    Reply

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.