12

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

11

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 '18 at 14:44
  • I'm afraid IT did this for me, I'm the Sharepoint Admin. Someone else on the site must have experienced the same issue. I also wouldn't know how to use the code; I believe it was done on the Sharepoint Server in the command console, but beyond that I would not know what to do. HELP - can someone else assist? – Tally Sep 26 '18 at 8:27
  • Hi Cheten, at the time of writing there are a couple of new Answers - did either of these provide the detailed instructions you need to solve your issue? – Tally Sep 28 '18 at 10:07
  • 1
    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. – Drew Paxton Oct 1 '18 at 23:01
  • 1
    This worked for me.. and fixed the issue ... – mzonerz Oct 2 '18 at 7:56
7
+100

Following up on my comment above. :)

As a solution for this problem, follow the instructions in this MS 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.

Cheers, -Drew

2

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.

0

I started seeing the same thing this morning. I am not a Farm Admin -- but, I understand from the link that the PowerShell Script, at the bottom of the ref'd link, needs to be run on one of the Farm WFEs. They say that that should resolve it.

  • whether that fixed the issue? running script – Chetan Sep 27 '18 at 8:34
0

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.

refresh

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.

  • 1
    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 '18 at 15:10
0

I can see it as answered but just wanted to share few links for others who turn up like me who have faced the same issue.

Blog confirming MS Patching issue: https://blogs.technet.microsoft.com/stefan_gossner/2018/09/14/after-applying-net-security-fixes-released-in-september-2018-to-address-cve-2018-8421-sharepoint-workflows-stop-working/

More Details about the fix : https://support.microsoft.com/en-us/help/4465015/sharepoint-workflows-stop-after-cve-2018-8421-security-update

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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