Skip to main content
Search Again

We think these articles could help you:

    See More
    Nintex Knowledge Base

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

    Status: Validated

     

    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
    RESOLUTION
     

    Update : 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
     
     The following are the KB for this updates :
    KB4457918 -- Security and Quality Rollup for .NET Framework 3.5.1 on Windows Embedded Standard 7, Windows 7, and Windows Server 2008 R2
    KB4457044 -- Security and Quality Rollup for .NET Framework 3.5.1 for Windows 7 SP1 and Server 2008 R2 
    KB4457919 -- Security and Quality Rollup for .NET Framework 3.5, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2 for Windows Embedded 8 Standard and Windows Server 2012
    KB4457920 -- Security and Quality Rollup for .NET Framework 3.5, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2 for Windows 8.1, Windows RT 8.1, and Windows Server 2012 R2
    KB4457921 -- Security and Quality Rollup for .NET Framework 2.0, 3.0, 4.5.2, 4.6 for Windows Server 2008
    KB4457131 -- Cumulative update for Windows Server 2016 for x64-based Systems 
    KB4457034 -- Security and Quality Rollup for .NET Framework 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 
    KB4457045 -- Security and Quality Rollup for .NET Framework 3.5 for Windows 8.1 and Server 2012 R2
    KB4457056 -- Security Only update for .NET Framework 3.5 for Windows 8.1 and Server 2012 R2
    KB4457026 -- Security Only update for .NET Framework 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, and 4.7.2 for Windows 8.1 and Server 2012 R2
    KB4457028 -- Security Only update for .NET Framework 4.5.2 for Windows 8.1 and Server 2012 R2


    Note: This is an issue with the Microsoft Windows patches you will need to remove them from all servers. 

     





     



     
    ADDITIONAL INFORMATION
    Here is the link to the issue with Microsoft ongoing issue for Workflows stopped working after September patch update 

    https://blogs.msdn.microsoft.com/rodneyviana/2018/09/13/after-installing-net-security-patches-to-address-cve-2018-8421-sharepoint-workflows-stop-working/

     Note: Any additional questions in regards to this article should be directed to Microsoft Support