June 2024 CU for SharePoint Server 2019 is available for download

13 Comments

1. 

   Evgeny
   On 13. June 2024 Permalink

   Hi, Stefan!
   A few months ago, I wrote to you about my problem with installing updates on a large SharePoint farm. Unfortunately, I don’t remember which post my comment was in and attach link. 🙁

   At that time, you advised me to update my 1200 content databases in parallel using PowerShell. I took your advice and ran 4 sessions simultaneously (one for each SQL cluster). As a result, the database update time was reduced from 11 hours to 2.5 hours. Great result!

   However, after updating the databases, I need to run the Configuration Wizard on the servers, and it can’t be run in parallel. On each of my 20 servers, the Wizard runs for 10-15 minutes (depending on the server). The most time-consuming step is the last one – “Finalizing upgrade”. According to the logs, at this step, the Wizard goes through all the databases again and just checks their version. And this happens on each server.

   Do you have any ideas on how to speed up this process?

   Reply
   1. 

      Stefan Goßner
      On 13. June 2024 Permalink

      Hi Evgeny,
      you cannot run it in parallel completely – but you can executed it first on one server to ensure that all the database specific operations are completed and after this is done you can run it on all other servers in parallel.
      Cheers,
      Stefan

      Reply
2. 

   Tom Crawford
   On 18. June 2024 Permalink

   I don’t know if Stefan will see this response, but his instructions explaining that you can run the Configuration Wizard in parallel after you run it successfully once on the first server is huge. We also upgrade 100 content databases in multiple sessions to speed up the process, plus to also allow for monitoring since you can view this step’s progress in CA.

   We have only 7 servers in our farm, but running the Configuration Wizard in parallel for 6 of these servers will save over an hour in the process.

   Nice tip to learn after 10 years with a company that requires the monthly patch to be installed within two weeks of release.

   Thanks Stefan!

   Reply
   1. 

      Stefan Goßner
      On 18. June 2024 Permalink

      My pleasure! 🙂

      Reply
3. 

   Emma
   On 28. June 2024 Permalink

   I encountered “06/28/2024 10:42:23 16 WRN Failed to add the service connection point for this farm” error when I ran “psconfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures” after the installation of the June 2024 cumulative update.

   @Stefan, I need help with solution to this issue. Assuming I am unable to create any new SharePoint Service accounts or groups in Active Directory.

   Log details below:

   06/28/2024 10:42:23 16 INF Successfully created security token service application
   06/28/2024 10:42:23 16 INF Creating service connection point for this farm …
   06/28/2024 10:42:23 16 WRN Failed to add the service connection point for this farm
   06/28/2024 10:42:23 16 INF Entering function StringResourceManager.GetResourceString
   06/28/2024 10:42:23 16 INF Resource id to be retrieved is ServiceConnectionPointNotCreatedEventLog for language English (United States)
   06/28/2024 10:42:23 16 INF Resource retrieved id ServiceConnectionPointNotCreatedEventLog is Unable to create a Service Connection Point in the current Active Directory domain. Verify that the SharePoint container exists in the current domain and that you have rights to write to it.
   06/28/2024 10:42:23 16 INF Leaving function StringResourceManager.GetResourceString
   06/28/2024 10:42:23 16 WRN Unable to create a Service Connection Point in the current Active Directory domain. Verify that the SharePoint container exists in the current domain and that you have rights to write to it.
   Microsoft.SharePoint.SPException: The object LDAP://CN=Microsoft SharePoint Products,CN=System,DC=mems,DC=root,DC=local doesn’t exist in the directory.
   at Microsoft.SharePoint.Administration.SPServiceConnectionPoint.Ensure(String serviceBindingInformation)
   at Microsoft.SharePoint.PostSetupConfiguration.UpgradeTask.Run()

   Reply
   1. 

      Stefan Goßner
      On 28. June 2024 Permalink

      Hi Emma,

      the service connection point is optional. There is no need to create one.
      This should not lead to a failing psconfig run. As you can see it is only a Warning and not an error.

      Cheers,
      Stefan

      Reply
      1. 

         Emma
         On 28. June 2024 Permalink

         Total number of configuration settings run: 5
         Total number of successful configuration settings: 4
         Total number of unsuccessful configuration settings: 1
         Successfully stopped the configuration of SharePoint Products.
         Configuration of SharePoint Products failed. Configuration must be performed before you use SharePoint Products. For further details, see the diagnostic log located at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\16\LOGS\PSCDiagnostics_6_28_2024_10_41_20_544_1313718647.log and the application event log.

         Reply
      2. 

         Emma
         On 28. June 2024 Permalink

         06/28/2024 10:47:06 16 INF SyncUpgradeTimerJob: Upgrade timer job failed. Return -1.
         06/28/2024 10:47:06 16 ERR The exclusive inplace upgrader timer job failed.

         Reply
4. 

   Dominique
   On 10. July 2024 Permalink

   Anyone have an issue with the Suite Navigation after this update? I just posted my issue on QA but thought I should mention it here too.

   Reply
   1. 

      Egor
      On 24. July 2024 Permalink

      Can you link the issue here please?

      Reply
      1. 

         Dominique
         On 25. July 2024 Permalink

         Funny story, I had written up my issue on the Microsoft QA site but I got an error when I tried to submit my entry. So i lost all my notes. BUT I do have an update. After investigating the ULS logs I found reference to “EXECUTE permission was denied on the object ‘Admin_FetchPartitionProperties’, database ‘SHPT_Profile’ schema ‘upa’. So we evaluated the permissions on that schema and found that a user mapping to the SPDataAccess role as missing. Once we corrected it the SuiteNav reappeared.

         So this leads to another question I have… It seems that lately, every time we install a farm update, the roles and permissions get modified. This is frustrating for my DBA because we are DOD and have to adjust permissions to Microsoft best practice and comply with DISA STIGs. Is this expected behavior that the farm update modifies permissions on the databases???

         Reply
         1. 

            Stefan Goßner
            On 26. July 2024 Permalink

            Hi Dominique,
            depends on the fix. Fixes which update the database schema perform modifications on database objects and in this context they are sometimes also assigning the specific permissions required by SharePoint.
            If these get manually changed afterwards the CU might revert this change.
            Cheers,
            Stefan

            Reply
            1. 

               Dominique
               On 27. July 2024 Permalink

               Thank you!