Nintex Workflows 2010 stop working after Security Update (KB 4022207 & KB 4032215)

  • 1 October 2018
  • 2 replies
  • 2 views

Badge +1

Hello Nintex Community,

we installed the mentioned Updates and the Workflows stopped working, they start and immediately run into an Error.

It's not possible to edit specific Actions, like Set Field Value, and existing Workflows can't be published.

Nintex Support mentioned the following workaround:

A workaround is to add the below line to the <targetFx version="v4.0"> node under the <authorizedTypes> node of the web.config file <authorizedType Assembly="System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System.CodeDom" TypeName="*" Authorized="True"/>

But that seems not to be working, after the Updates are installed, the Problem remains.

Any suggestions what could be wrong?

Environment:

Windows Server 2008 R2 Enterprise - Service Pack 2

SharePoint 2010 - 14.0.7175.5000

Nintex Workflow 2010 - 2.3.14.0

Kind Regards, Milan


2 replies

Badge +8

HI Milan,

In addition to the above (which is specific only to Nintex) there are other additions you might need to add to the web.config file. Please refer to the community post by Andrew Glasser‌ 

 

Note - 

Please make these changes to the web.config file for the web application that your site collections is residing against. If you have multiple web applications then you would need to update config file for all of them. an IISReset/timerjob restart might also help.

Regards,

Shrini

Badge +3

Hello Milan,

we had the same issue at one of our clients which is still using SharePoint 2010.

We solved it by adding the following line to the web.config:

<System.Workflow.ComponentModel.WorkflowCompiler>
   <authorizedTypes>
      ...
      <authorizedType Assembly="System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System.CodeDom" TypeName="*" Authorized="True" />
   </authorizedTypes>
   ...
</System.Workflow.ComponentModel.WorkflowCompiler>

Workflows started again without issues after this change.

Reply