I am using SharePoint 2013 farm if I try to publish Workflow for Document library getting below error.

(-1, -1) Type System.CodeDom.CodeBinaryOperatorExpression is not marked as authorized in the application configuration file.) (0, 0) Activity 'ID5' validation failed: Property "Condition" has invalid value. Condition expression is invalid. The condition expression cannot be null.)

if I check for errors before publishing, there were no errors. enter image description here

  • We have tried this but this not working. We are still getting the same error. What else can be missing? We have checked on the server, there is no update installed (KB4457916/KB4457035). Still we are facing this issue.
    – Jignesh
    Oct 23, 2019 at 10:01

4 Answers 4


I've had this too, it started yesterday I think. This Microsoft link fixed it for me.

The ​problem was caused by a .Net update. If only these things were tested before they were released!

Below is my workflow error message - all workflows had stopped working in the Sharepoint Farm.

I was told that the MS fix in the above link, running IISRESET and also a WakeUp script fixed it.

my workflow error message

  • Yeah, I went through the link you suggested. could you please tell me where you inserted the code or how you fixed it. I am confused with the steps they mentioned in the article.
    – Chetan
    Sep 25, 2018 at 14:44
  • 2
    Tally and Chetan, the code referenced in the MS link above needs to be added to web.config file on the server. In our case, we had to update only the web front end servers, but depending on how your farm is configured then it may differ for you. Oct 1, 2018 at 23:01

As a solution for this problem, follow the instructions in this Microsoft support article by adding the code referenced to the web.config file on your SP server. In my organization's case, this was applied only to web front end servers, but check with your IT team to verify that against the topology of your farm.


Microsoft released a .NET update which causes lots of problems with SharePoint workflows.

The article also contains a PowerShell-Script which fixes the problems caused by the patch: Add-CodeDomAuthorizedType.ps1

Simply download the script on one SharePoint-Server and execute it in SharePoint PowerShell. The changes are automatically propagated within the entire farm (if you have mulitple servers).

Important: This script causes an IIS-Reset on every server. So SharePoint will not be available for some minutes.


If a column has changed in SharePoint while Designer was opened, Designer may need a quick refresh.

This can be achieved by either restarting Designer, or by clicking the data refresh icon at the top left corner of the window.


Another thing I've done to fix Designer workflow errors is:

  • Select All of the workflow
  • Copy everything to clipboard
  • Delete everything
  • Paste everything back in from clipboard

Surprisingly, this fixes certain errors to do with designer workflow activities.

  • 2
    while this is a good tip, I'm pretty sure the error Chetan had was caused by a .net update Microsoft released - the fix for this bug is contained in my Answer. Chetan just needs to know how and where to run the code.
    – Tally
    Sep 27, 2018 at 15:10
  • This does not address the question asked by OP.
    – TylerH
    May 19, 2020 at 21:09

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.