cancel
Showing results for 
Search instead for 
Did you mean: 

Workflow Failed to Run or Failed to Publish Workflow, after applying Microsoft Update

ISSUE
After a recent Microsoft Windows update, Nintex Workflows for 2010, 2013, 2016 no longer publish or fail to run.

 

The ULS logs may have the following entries:

 

===============================================================================================================
ServerServer was unable to process request. ---> Failed to publish workflow: <Error><CompilerError Line="-1" Column="-1" Text="Type System.CodeDom.CodeBinaryOperatorExpression is not marked as authorized in the application configuration file." /><CompilerError Line="0" Column="0" Text="Activity 'runIf2Activity1' validation failed: Property &quot;Condition&quot; has invalid value. Condition expression is invalid. The condition expression can not be null." /></Error>
 

===============================================================================================================
ServerServer was unable to process request. Failed to publish workflow: :CompiIerError Line: "-I " Column: "-I " Text: "Type System.CodeDom.Code8inaryOperatorExpression is not marked as authorized in the application configuration file
 

===============================================================================================================
RunWorkflow: Microsoft.SharePoint.SPException: <Error><CompilerError Line="0" Column="0" Text="Activity 'ID3' validation failed: Property &quot;Condition&quot; has invalid value. Condition expression is invalid. Couldn't find type WorkflowConditions.CustomConditions, WorkflowConditions
===============================================================================================================

 

Note: This will also affect Sharepoint Designer Workflows.
 
ERROR CODE
soapSmiley FrustratederverServer was unable to process request. ---> Failed to publish workflow
RESOLUTION
Here is a resolution from Microsoft for the fix: 

 

https://blogs.msdn.microsoft.com/rodneyviana/2018/09/13/after-installing-net-security-patches-to-add... 

 

In addition to the above solution, the following will need to be added to the web.config and OWSTIMER.exe.config files if workflows are stuck 'In Progress' after the updates.

 

<authorizedType Assembly="Microsoft.SharePoint.WorkflowActions, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" Namespace="Microsoft.SharePoint.WorkflowActions" TypeName="*" Authorized="True" />

 
Note: These updates need to be done for all web applications on all servers with the Microsoft Foundation Web Application Service running using the script provided by Microsoft. If you face any issues with the script or the steps provided in the link above, please reach out to Microsoft Support. 

 

In some cases, the OWStimer.Config file will also need to be updated, the steps to perform this are mentioned in the above video
ADDITIONAL INFORMATION
This is caused by security and Quality Rollup updates for .NET Framework 3.5, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, and 4.7.2 for Windows 8.1, RT 8.1, and Server 2012 R2

 

 
Labels: (1)
Version history
Revision #:
2 of 2
Last update:
2 weeks ago
Updated by:
 
Contributors