SharePoint security fixes released with December 2022 PU and offered through Microsoft Update

13 Comments

1. 

   Ashok
   On 14. December 2022 Permalink

   Thanks for details.

   Reply
2. 

   Walter
   On 19. December 2022 Permalink

   This is related to Office Online Server. Although there is no update this month for OOS, the Windows 2019 Server was updated, and now OOS is offline, and I can’t restore service. I have rebuilt the OOS farm with no success. The event viewer on the OOS server has constant warnings about ASP.NET 4.0.30319.0 with event code 3005, An unhandled exception has occurred.
   Are there any know issues with the Dec. OS updates and OOS? Thanks for any help you have to offer.

   Reply
   1. 

      Walter
      On 27. December 2022 Permalink

      Update – after further testing, it appears that the issue was the web front end server for an unknown reason. DNS is now pointing to one of the app servers (temporarily) so that Office Online service is restored to users. Not sure why the web front end stopped working with the OOS after the Dec 2022 Updates, but it did.

      Reply
3. 

   Nanda
   On 21. December 2022 Permalink

   December 2022

   Reply
4. 

   Michal
   On 21. December 2022 Permalink

   hi Steafan.
   Some people are reporting issues with “List People field Empty on Edit” https://techcommunity.microsoft.com/t5/sharepoint/sharepoint-list-people-field-empty-on-edit/m-p/3699187
   Are you aware of this ?

   Reply
   1. 

      Stefan Goßner
      On 21. December 2022 Permalink

      Yes. This is a known issue in December 2022 CU for SharePoint Server 2019.
      The product group is investigating the issue.

      Reply
      1. 

         Michal
         On 21. December 2022 Permalink

         Thank you Stefan for confirming 🙂

         Reply
5. 

   Jain Raj
   On 22. December 2022 Permalink

   getting below error while configuring the CU in SharePoint 2019. any idea

   Exception: Microsoft.SharePoint.Upgrade.SPUpgradeException: Action 16.0.26.8 of Microsoft.SharePoint.Upgrade.SPIisWebSiteWssSequence failed. —> System.Security.Principal.IdentityNotMappedException: Some or all identity references could not be translated.
   at System.Security.Principal.NTAccount.Translate(IdentityReferenceCollection sourceAccounts, Type targetType, Boolean forceSuccess)
   at System.Security.Principal.NTAccount.Translate(Type targetType)
   at System.Security.AccessControl.CommonObjectSecurity.ModifyAccess(AccessControlModification modification, AccessRule rule, Boolean& modified)
   at System.Security.AccessControl.CommonObjectSecurity.AddAccessRule(AccessRule rule)
   at Microsoft.SharePoint.Upgrade.SPUtility.UpdatePermissionForWebConfig(String webconfigFilePath, SPApplicationPool applicationPool)
   at Microsoft.SharePoint.Upgrade.UpdatePermissionForWebConfig.Upgrade()
   at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade()

   Reply
   1. 

      Stefan Goßner
      On 22. December 2022 Permalink

      Hi Jain,
      I would suggest to check this article:
      https://social.technet.microsoft.com/wiki/contents/articles/45563.sharepoint-2013-some-or-all-identity-references-could-not-be-translated.aspx
      Cheers,
      Stefan

      Reply
      1. 

         Surendran
         On 21. October 2024 Permalink

         Hi Stefan, Do you have any other solution for this issue?

         Reply
   2. 

      Michal
      On 22. December 2022 Permalink

      Have you tried running the PSconfig/config wizard again?

      Reply
6. 

   Naveen
   On 29. January 2023 Permalink

   Hi Stefan,

   Workflows are failing post applying Dec 2022 security updates on our sharepoint 2013 farm. Below is the log:
   Engine RunWorkflow: System.Workflow.ComponentModel.Compiler.WorkflowValidationFailedException: The workflow failed validation.
   at System.Workflow.Runtime.WorkflowDefinitionDispenser.ValidateDefinition(Activity root, Boolean isNewType, ITypeProvider typeProvider)
   at System.Workflow.Runtime.WorkflowDefinitionDispenser.LoadRootActivity(Type workflowType, Boolean createDefinition, Boolean initForRuntime)
   at System.Workflow.Runtime.WorkflowDefinitionDispenser.MruCache.GetOrGenerateDefinition(Type type, String xomlText, String rulesText, Byte[] md5Codes, Boolean initForRuntime, Boolean& exist)
   at System.Workflow.Runtime.WorkflowRuntime.InitializeExecutor(Guid instanceId, CreationContext context, WorkflowExecutor executor, WorkflowInstance workflowInstance)
   at System.Workflow.Runtime.WorkflowRuntime.Load(Guid key, CreationContext context, WorkflowInstance workflowInstance)
   at System.Workflow.Runtime.WorkflowRuntime.GetWorkflowExecutor(Guid instanceId, CreationContext context)
   at System.Workflow.Runtime.WorkflowRuntime.InternalCreateWorkflow(CreationContext context, Guid instanceId)
   at System.Workflow.Runtime.WorkflowRuntime.CreateWorkflow(Type workflowType, Dictionary2 namedArgumentValues, Guid instanceId)
at Microsoft.SharePoint.Workflow.SPWinOeHostServices.Send(SPWorkflow workflow, SPWinOeWorkflow winoeworkflow, SPWorkflowEvent e)
at Microsoft.SharePoint.Workflow.SPWinOeEngine.RunWorkflow(SPWorkflowHostService host, SPWorkflow workflow, Collection1 events, TimeSpan timeOut)

   Could you please help.

   Reply
7. 

   surendran
   On 21. October 2024 Permalink

   Hi Raj, Did you find any solution for this issue?

   Reply