Sharepoint 2010 workflows stopped working after applying multiple windows uupdates

Question

After installing multiple security updates in our Sharepoint server, suddenly all the workflows stopped working with Failed to Start errors. I have added the Authoryzed types entries in the web config as suggested by other users but the issue persists.

We are running an On Premise Sharepoint 2019 farm with 2010 workflows running in a site collection.

The installed updates are: KB5002639, KB5043051, KB5043124

In the logs i get this error:

RunWorkflow: System.InvalidOperationException: This feature has been temporarily disabled.
at Microsoft.SharePoint.Workflow.SPNoCodeXomlCompiler.CompileBytes(Byte[] xomlBytes, Byte[] rulesBytes, Boolean doTestCompilation, String assemblyName, SPWeb web, Boolean forceNewAppDomain)
at Microsoft.SharePoint.Workflow.SPNoCodeXomlCompiler.LoadXomlAssembly(SPWorkflowAssociation association, SPWeb web)
at Microsoft.SharePoint.Workflow.SPWinOeHostServices.LoadDeclarativeAssembly(SPWorkflowAssociation association, Boolean fallback)
at Microsoft.SharePoint.Workflow.SPWinOeHostServices.CreateInstance(SPWorkflow workflow)
at Microsoft.SharePoint.Workflow.SPWinOeEngine.RunWorkflow(SPWorkflowHostService host, SPWorkflow workflow, Collection1 events, TimeSpan timeOut) at Microsoft.SharePoint.Workflow.SPWorkflowManager.RunWorkflowElev(SPWorkflow workflow, Collection1 events, SPWorkflowRunOptionsInternal runOptions)

Answer 1

Hi @Jorge Cerbo ,

Welcome to Q&A forum!

This could be due to the recent security updates that were installed on your SharePoint server.

There are some methods you can try:

1, According to KB5002639,this update will affect SharePoint workflows. It is recommended to check the ULS logs.

You might experience an issue in which SharePoint workflows can't be published because the unauthorized type is blocked. The issue also generates event tag "c42q0" in SharePoint Unified Logging System (ULS) logs.

If this is the case, you can try the solution provided in the article.

2, You can try restarting the SharePoint Timer Service and see if that resolves the issue. If not, you may need to check if there are any other updates or patches that need to be installed to fix this issue.

3, Check if the SharePoint 2010 Workflow service is running properly. You can do this by going to Central Administration -> Application Management -> Manage services on server and checking if the service is started. If it is not started, try starting it and see if that resolves the issue.

Good day!

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.