Issue

Resolution

1. To resolve the issue, add the following lines to all of the SharePoint web application's web.config. These need to be added in the authorizedTypes config section (configuration -> configSections -> System.Workflow.ComponentModel.WorkflowCompiler -> authorizedTypes -> targetFx). Attached is also a PowerShell script that will add the required entries. <authorizedType Assembly="System.Workflow.ComponentModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Namespace="System.Workflow.*" TypeName="ArrayExtension" Authorized="True" /> <authorizedType Assembly="System.Workflow.ComponentModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Namespace="System.Workflow.*" TypeName="ArrayExtension" Authorized="True" /> <authorizedType Assembly="System.Workflow.ComponentModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Namespace="System.Workflow.*" TypeName="TypeExtension" Authorized="True" /> <authorizedType Assembly="System.Workflow.ComponentModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Namespace="System.Workflow.*" TypeName="TypeExtension" Authorized="True" />​
2. After making the update you will need to perform an IISReset. Also restarting the OWSTimer service may also be required in case workflows are running on the timer service process.

Additional Information

This issue is coming from a new change to address Common Vulnerabilities and Exposures that were delivered in the September Public Updates for SharePoint Server.

We will provide an update once the resolution has been included in an updated build of Nintex Workflow for SharePoint On Premises.

Related Links

https://docs.microsoft.com/en-us/officeupdates/sharepoint-updates

https://support.microsoft.com/en-us/topic/some-scenarios-of-sharepoint-2010-workflow-are-affected-after-applying-the-july-security-update-for-sharepoint-server-kb5004862-be361cd6-9f54-48c4-b890-2c4b7cf49d13