October 2022 CU for SharePoint Server 2019 is available for download

12 Comments

1. 

   Girish
   On 13. October 2022 Permalink

   In the C:\Windows\Installer folder, I noticed that there are about 12 GBs of patch installers for Microsoft SharePoint Server 2019. It looks to be a cumulation of patches from January of 2019 to today. It seems like when a patch is applied for SharePoint, it stores the patch installer into this directory to be used just in case if you need to uninstall it. The problem is that over time, this starts to get huge.

   Is there a way to cleanup C:\Windows\Installer folder?

   Reply
   1. 

      Stefan Goßner
      On 13. October 2022 Permalink

      Hi Girish,
      you should not touch this directory. Removing elements can lead to a situation where you are no longer able to apply further patches.
      Cheers,
      Stefan

      Reply
2. 

   sdrspnation
   On 13. October 2022 Permalink

   Hi Stefan,

   Post installing the Oct 2022 SP 2019 Patch , After the latest patch we have noticed that some of out SharePoint Designer workflows have started to fail and throw the following error in ULS Logs :

   Microsoft.Workflow.Client.ScopeNotFoundException
   HResult=0x80131500
   Message=Scope ‘/SharePoint/default/1412b875-e1f4-4829-b8c4-248635a4bbd2/67a41b16-64eb-43cd-a678-9bd00db33785’ was not found. HTTP headers received from the server – ActivityId: 4a114c79-e50a-4a67-b89a-f92a27044ec7. NodeId: 04ADC15301. Scope: /SharePoint/default/1412b875-e1f4-4829-b8c4-248635a4bbd2/67a41b16-64eb-43cd-a678-9bd00db33785. Client ActivityId : b90b6ea0-a05d-e095-c20d-a64be0dbb44e.
   Source=Microsoft.Workflow.Client
   StackTrace:
   at Microsoft.Workflow.Client.ClientHelpers.SendRequest[T](HttpWebRequest request, T content)
   at Microsoft.Workflow.Client.WorkflowManager.StartInternal(String workflowName, WorkflowStartParameters startParameters)
   at Microsoft.SharePoint.WorkflowServices.FabricWorkflowManagementClient.StartInstance(String serviceGroupName, String workflowName, String monitoringParam, String activationKey, IDictionary2 payload)
at Microsoft.SharePoint.WorkflowServices.FabricWorkflowInstanceProvider.StartWorkflow(WorkflowSubscription subscription, IDictionary2 payload)
   at Microsoft.SharePoint.WorkflowServices.FabricWorkflowInstanceProvider.StartWorkflowOnListItem(WorkflowSubscription subscription, Int32 itemId, IDictionary`2 payload)
   at NGS.SharePoint.SOPWorkflowEventReceiver.InitializeSOP.InitializeSOP.<>c__DisplayClass3_0.

   Reply
   1. 

      Stefan Goßner
      On 13. October 2022 Permalink

      It sounds to me as if the workflow manager registration on this farm is no longer valid.
      The scope “SharePoint” seems to be missing.

      You can reestablish it using the command below (ensure to fill in the missing parts)

      Register-SPWorkflowService -SPSite -WorkflowHostUri -ScopeName “SharePoint” -Force

      See below for details:
      https://learn.microsoft.com/en-us/sharepoint/dev/general-development/using-the-pairing-cmdlet-register-spworkflowservice

      If this does not help I would suggest to open a support case with Microsoft to get this analyzed in more details.

      Cheers,
      Stefan

      Reply
3. 

   Karthikeyan
   On 20. October 2022 Permalink

   Hi Stefan, we wanted to know the steps to identify and address .xoml file encoding known issue reported in the 2016 & 2019 KB’s (KB5002278 & KB5002287) . The below mentioned blog doesn’t contain any details on how to address it and we don’t have any resolution from our end . Could you please guide us ?

   https://support.microsoft.com/en-us/topic/sharepoint-2010-workflows-might-be-blocked-by-enhanced-security-policy-kb5020238-eb91e24d-eea4-4490-a281-86503adc8b27

   Reply
   1. 

      Stefan Goßner
      On 24. October 2022 Permalink

      Hi Karthikeyan,
      if you need assistance for this I would recommend to open a support ticket with Microsoft.
      Cheers,
      Stefan

      Reply
4. 

   Wishnu
   On 21. October 2022 Permalink

   Do we have to apply the fixes mentioned in September 2022 CU after installing October 2022 CU if we are directly going from June 2022 CU?

   Reply
   1. 

      Stefan Goßner
      On 24. October 2022 Permalink

      Hi Wishnu,
      SharePoint fixes are cumulative. If you install both fixes from October CU they include all fixes from September CU as well.
      Cheers,
      Stefan

      Reply
5. 

   dodiamond
   On 28. October 2022 Permalink

   Stefan, after applying the October 2022 CU to our On-Prem SharePoint 2019 dev farm, we are now seeing errors when trying to use “Share” or “Shared with” on list items: “Sharing context retrieval failed: SyntaxError: Unexpected end of JSON input”. However, when we examine the actual web calls being made, we see a 404 Not Found for “https://CONTOSO.com/sites/CONTOSO/_api/SP.Web.GetObjectSharingSettings”, whereas that same call works without issues in our production site, which has not had the October 2022 CU applied yet. Have you seen this problem reported yet?

   Reply
   1. 

      Stefan Goßner
      On 7. November 2022 Permalink

      Hi,

      I haven’t heard about such an issue. If you need assistance to resolve it I would recommend to open a ticket with Microsoft Support.

      Cheers,
      Stefan

      Reply
   2. 

      Ahmed M. Abdelsabour
      On 25. January 2023 Permalink

      Hello,
      did you fix this issue? I need help

      Reply
6. 

   Carl Dalton
   On 9. December 2022 Permalink

   Be aware there is also an issue that was introduced soem time between Jan21 and Oct22 that causes RDB refresh to fail and leave the RDB schema out of sync with PWA. We are running an incident on this, and it is seen on OCT22CU and NOV22CU (though could have been introduced earlier)

   Reply