locked
Sharepoint 2013 - "Collect Signatures Sharepoint 2010" Workflow - "Type System.CodeDom.CodeBinaryOperatorExpression is not marked as authorized in the application configuration file" after september 2018 update RRS feed

  • Question

  • After september 2018 Sharepoint update KB4092470 all "Collect Signatures - Sharepoint 2010" workflows do not run or publish any more.

    Along with SP update the following have been also applied: KB4457915, KB4457919 (.NET); KB4457140, KB4457135 (Windows 2012 Server), KB4457426 (IE10)

    Error from logs:

    Type System.CodeDom.CodeBinaryOperatorExpression is not marked as authorized in the application configuration file 

    I added in web.config from C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\CONFIG folder and also in web.config file from the web app dir in C:\inetpub\wwwroot\wss\VirtualDirectories\8190 the following line:

                <authorizedType Assembly="System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System.CodeDom" TypeName="CodeBinaryOperatorExpression" Authorized="True"/>

    but with no effect.

    Windows Server 2012, Sharepoint 2013 SP1

    All Sharepoint 2010 Worflows (Approval, Collect Feedback, Collect Signatures) have the same issue.

    Need some help please.




    • Edited by iamdon Wednesday, September 12, 2018 12:13 PM
    Wednesday, September 12, 2018 11:06 AM

Answers

  • Resolution from Microsoft:

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

    Friday, September 14, 2018 1:34 AM

All replies

  • I've the same issue is there any update?

    Hamed Abdelraof, Senior System Admin. ITIDA, Egypt

    Wednesday, September 12, 2018 12:56 PM
  • Need some help, also have the same error

    Windows 2008 R2 sp1 and sharepoint 2010 sp2 all nintex workflows failed.


    Wednesday, September 12, 2018 5:33 PM
  • Sharepoint 2010 with Workbox workflows. Server 2008 R2. All workflows have the same error starting earlier this morning.

    Only received updates KB4457044 and KB4457144 last night.

    Help!


    • Edited by FrodoCl Wednesday, September 12, 2018 5:49 PM
    Wednesday, September 12, 2018 5:43 PM
  • I am having similar issues; SharePoint 2010 on Windows Server 2008 R2.  Looking at just rolling back the patch tonight.

    Wednesday, September 12, 2018 6:01 PM
  • Confirmed. This patch makes all Nintex workflows fail and you cannot publish new versions of any workflow. We solved this quickly by rolling back the patch.

    Now working on restarting all the failed workflows.

    Wednesday, September 12, 2018 6:29 PM
  • How did you roll back the patch
    Wednesday, September 12, 2018 6:53 PM
  • Piling on here. w2k8 SP2010 SP2 using some third-party workflow actions (specifically, ilovesharepoint's execute powershell) This issue has eaten my afternoon. Now attempting to roll back updates. 
    Wednesday, September 12, 2018 7:20 PM
  • Which specific update did you roll back?
    Wednesday, September 12, 2018 7:28 PM
  • We work in a virtual environment and we just restored the web front end to a day before the patch auto installed, then immediately stopped updates in that server.
    Wednesday, September 12, 2018 7:40 PM
  • Think the .NET one is the one that breaks it, but we rolled back everything installed over night by restored a VM backup.
    Wednesday, September 12, 2018 7:41 PM
  • I thought this one was the one that broke it: https://support.microsoft.com/en-us/help/4022207/description-of-the-security-update-for-sharepoint-server-2010  (2010 version of the patch).  I'm going to try rolling just that one back tonight.
    Wednesday, September 12, 2018 8:12 PM
  • UkiMagic209, we did not receive that patch. I assume because we are still on 2010 SP1, and this patch requires SP2.

    So, I'm not sure that this is the patch that broke it.

    Wednesday, September 12, 2018 8:23 PM
  • UkiMagic209 I really hope it's not that one. That patch is showing as not removable for me.

    *Edit: I'm pretty sure that's not it. I just check and I'd installed that patch at 8:06 this morning but had a workflow error around 7.

    *Edit2: I just uninstalled kb4457043 and my workflows are working again!! 
    • Edited by steam23 Wednesday, September 12, 2018 9:38 PM
    Wednesday, September 12, 2018 9:21 PM
  • Thanks Steam23!  I had to remove KB4457044 (.NET 3.5.1 rollup) to get things working again!  We are on SharePoint 2010 SP2, Server 2008 R2 SP1.

    You're right; the SharePoint-specific patches don't have the uninstall option!  I was looking at a possible full server restore to revert.  Glad removing that .NET patch did the trick 😊.


    • Edited by UkiMagic209 Wednesday, September 12, 2018 11:47 PM
    Wednesday, September 12, 2018 11:46 PM
  • I wanted to chime in and say that after installing patches last night my 2010, extremely generic workflows stopped working as well.  Rollback of .net patches fixed issue.

    Stuart


    • Edited by slhilbert Thursday, September 13, 2018 12:29 PM
    Thursday, September 13, 2018 1:47 AM
  • yes, we have SharePoint 2013, and we updated our server earlier today and now our workflows "fail on start" and we cant even update/publish old or new workflows. problem is our server hasn't rebooted in a while and over 40 updates happened, but none are for .net framework. the hunt continues... or roll backs I guess I should say... if I find it ill post it...

    The only updates I see that have to deal with .net are KB4054566 and KB4457920 but unfortunately the only place I can see them us under Windows Update ("View Windows Updates") and I cant remove them...


    So running "wusa /uninstall /kb:4457920" from an elevated command prompt told me that KB4457920 wasn't installed even though it says it was successful.. so I moved on and ran the same command but for KB4054566 and it was removed successful. I ended up rebooting, with no luck so then I decided to try removing the rollup KB4557129 again with no luck... the search continues.
    • Edited by SPassler Thursday, September 13, 2018 2:50 AM
    Thursday, September 13, 2018 1:54 AM
  • Same here. Sharepoint 2013, September updates installed today (September 12, 2013) at 4am.

    Users reported that 2010 workflows were failing to run with workflow statuses of "Failed to Start" and "...was canceled by System Account."

    Further investigation found that the workflows wouldn't publish either. Still talking about only 2010 workflows. A couple of unusual errors are produced during publish...

    • Type System.CodeDom.CodeBinaryOperatorExpression is not marked as authorized in the application configuration file.
    • Activity 'IDxxx' validation failed: Property "Condition" has invalid value. Condition expression is invalid. The condition expression can not be null.

    Removing the conditions (if statements) eliminated these two errors, but the workflows still fail with the same statuses mentioned above.

    2013 workflows appear to be unaffected.

    After the users left for the day I applied all current patches to my farm. Updates completed successfully. Installed KB4092470, KB4018392, KB4022243, KB4022234, KB 4022236 along with Windows updates. The KB's mentioned in this thread weren't installed on my 2008R2 box.

    Opening a Microsoft case now.


    Jamie T

    Thursday, September 13, 2018 3:17 AM
  • good morning

    we are running SP2016 and Nintex 2016 on premise  and after installing KBKB4457045 and KB4457034 on Windows Server 2016 and 2012 R2 all Workflows stopped , Roolback both did the trick!


    mfg/regards M. Funck

    • Proposed as answer by SPassler Thursday, September 13, 2018 4:05 AM
    Thursday, September 13, 2018 3:28 AM
  • Rolling back the .NET updates did not resolve the issue for us. 2008 R2, SharePoint 2010.
    • Edited by FrodoCl Thursday, September 13, 2018 2:09 PM
    Thursday, September 13, 2018 4:02 AM
  • good morning

    we are running SP2016 and Nintex 2016 on premise  and after installing KBKB4457045 and KB4457034 on Windows Server 2016 and 2012 R2 all Workflows stopped , Roolback both did the trick!


    mfg/regards M. Funck


    Removing these two updates worked for me as well.
    Thursday, September 13, 2018 4:06 AM
  • We are also facing the same issue from yesterday. All the workflows are Cancelled and Failed to Start.

    We are running SharePoint 2013 and Nintex Workflow 2013.

    Are you sure uninstalling the upgrade will fix the issue?

    Thursday, September 13, 2018 7:09 AM
  • Same Problem Server 2012 R2 Sharepoint 2013, workflows not working since update.

    We are trieng to restore the VM web Frontend befor the update was installed.


    Thursday, September 13, 2018 7:27 AM
  • Same issue

    Windows 2008R2 SP1

    SharePoint 2013

    Removing KB4457035 (.NET) resolve the issue. 

    Thursday, September 13, 2018 7:29 AM
  • solved by uninstalling these updates and restarting server KB4457044 and KB4457144

    Hamed Abdelraof, Senior System Admin. ITIDA, Egypt

    Thursday, September 13, 2018 8:31 AM
  • Please contact us at support@datapolis.com and we will try to help.
    Thursday, September 13, 2018 8:50 AM
  • Same issue

    Windows 2008R2 SP1

    SharePoint 2013

    Removing KB4457035 (.NET) resolve the issue. 

    +1 

    Removing this update works for me.

    Thursday, September 13, 2018 9:19 AM
  • Thanks for this, we had to remove the September CU from our SP servers.

    Using elevated command prompt, we ran WUSA /uninstall /kb:4457131

    This has resolved the issue for us

    Thursday, September 13, 2018 10:19 AM
  • We are on Windows 2012 R2 standard and running SP 2013 and Nintex. The Workflows fail to publish. 

    I have uninstalled KB4457045 and KB4457034 on all the servers and restarted them, but the issue is still there. 

    Is there anything else I need to do, I can try uninstalling all the updates and see, but before I do that wanted to check if I was missing a step ! 

    Update: uninstalling all the patches that were installed today did the trick for us.


    Thursday, September 13, 2018 10:44 AM
  • We are currently running the following below:
    SharePoint Server 2016
    Windows Server 2012 R2 x64

    After investigating on what broke SharePoint Workflows, it looks like removing the following “updates” did the trick. The KB may be a different number, which is based on your Server (Server 2008, 2012 or 2016) and System Type (x64 or x86). The way I found it was by opening Windows Update and selecting "View Update History" and from there I saw the recent updates installed which others in this thread recommended removing the "Security and Quality Rollup for .NET Framework", which is true for me. After I removed it and restarted the Server, my SharePoint Workflows started to work again (Was able to Publish in SharePoint Designer and Start Workflows manually). 

    Using Elevated Command Prompt (Run as Administrator), I ran the following below:
    WUSA /uninstall /kb:4457045
    WUSA /uninstall /kb:4457034

    A few things to consider:

    • If you have any workflows that show "Failed on Start", you're going to need to restart them.
    • I would go to Windows Update and hide "Security and Quality Rollup for .NET Framework". Depending on your Windows Update Settings, it could download/install that update again unintentionally and then you are now back to square one.

    Security and Quality Rollup for .NET Framework 3.5 for Windows 8.1 and Server 2012 R2 (KB 4457045)
    https://support.microsoft.com/en-us/help/4457045/description-of-the-security-and-quality-rollup-for-net-framework-3-5-f

    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 (KB 4457034)
    https://support.microsoft.com/en-us/help/4457034/description-of-the-security-and-quality-rollup-for-net-framework-4-6-4

    Those two KBs above were inside the main update that was downloaded/installed through Windows 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 (KB 4457920)
    https://support.microsoft.com/en-us/help/4457920/security-and-quality-rollup-updates-for-net-framework-3-5-4-5-2-4-6-4


    Thursday, September 13, 2018 1:14 PM
  • I have the same problem and I can't find a software update that I can remove to fix the problem.  We are on SharePoint 2013 on-premises running Workflow 2010.  No workflows will publish and all workflows 'fail on start' with canceled by System Account.
    Thursday, September 13, 2018 2:37 PM
  • Our System Administrator removed a Microsoft patch and resolved our problem!  I don't know what the patch was or I would share it.  Thank you for helping me!  
    Thursday, September 13, 2018 3:57 PM
  • We ended up uninstalling KB4457026, KB4457034 and KB4457045 and then the workflows starting flowing again.  This thread was gold thank you everyone.

    Fred Bainbridge | Enterprise Mobility MVP | Automation Engineer | fredbainbridge.com

    Thursday, September 13, 2018 5:04 PM
  • I have the same issue here however I see the history (the log) of the update being installed for .net (KB4457920) but when looking in the installed updates that system does not show it was installed. Has anyone seen this yet? Basically, I can't uninstall it.
    Thursday, September 13, 2018 6:06 PM
  • Spent the last 3 hours on the phone with Microsoft support. We finally were able to resolve it.

    It was several security updates that had to be uninstalled. The first one was KB4457035 (.NET update). But that alone did not fix it.

    it was not easy to find the rest. Some updates were not showing in the installed updates list, even when filtering only on the last two days, and sorting. Had to use the search box to find the word "sharepoint". Several security updates were found (that were installed in the last two days) that were not showing in the default list. Un-installed all of them. Rebooted.

    Still not working. Then we found that one of these sharepoint security updates had mysteriously come back (only found by searching for sharepoint), even though automatic updates was already disabled. Uninstalled it again, and re-booted. It did not come back.

    Finally fixed.


    Thursday, September 13, 2018 6:41 PM
  • Thanks for sharing.  Did Microsoft provide a long term fix for this by chance?  Or give any indication of next steps?  These servers need to be patched eventually.

    -Fred


    Fred Bainbridge | Enterprise Mobility MVP | Automation Engineer | fredbainbridge.com

    Thursday, September 13, 2018 7:18 PM
  • Fred, yes he told me this issue was gaining a lot of attention at Microsoft, and eventually there should be a permanent fix. Could not give me a time frame though.
    Thursday, September 13, 2018 7:27 PM
  • Fred, yes he told me this issue was gaining a lot of attention at Microsoft, and eventually there should be a permanent fix. Could not give me a time frame though.

    "gaining a lot of attention at Microsoft"

    That's quite humorous. It has gained a lot of attention in my organization too over the past few days .

    Thursday, September 13, 2018 7:51 PM
  • Resolution from Microsoft:

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

    Friday, September 14, 2018 1:34 AM
  • that article sadly does not direct me to the file I need to edit. there are loads of 'config' files on my sharepoint server. is it talking about a special .net 4 one, or the web server one, or what?

    Mark

    Friday, September 14, 2018 7:49 AM
  • Please post more info. The article is very vague regarding Sharepoint 2010
    Friday, September 14, 2018 9:30 AM
  • You need to edit web.config of SharePoint web applications.

    Friday, September 14, 2018 10:39 AM
  • I've uninstalled the newest .net updates but the error was still there.  I put into (web config of SharePoint web apps) :

    <System.Workflow.ComponentModel.WorkflowCompiler>
        <authorizedTypes>
          <targetFx version="v4.0">HERE</targetFx>

    this following extra line:

    <authorizedType Assembly="System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" Namespace="System.CodeDom" TypeName="*" Authorized="True"/>

    It works for me, but I'm not sure if its the right solution.
    Friday, September 14, 2018 12:39 PM
  • We have a SharePoint 2016 farm on Windows 2016 and the KB4457131 patch broke the SharePoint 2010 workflows after the reboot.  Uninstalling the KB4457131 patch did fix the issue, but took a very long time to uninstall.

    The post regarding updated the config file also works, so we will move forward w/ the KB4457131 and the Config file updates.

    Thanks for everyone input.
    Friday, September 14, 2018 3:16 PM
  • Hi Jamie T,

    Any word or solution you found working for you? I am getting the same error messages. 

    Thanks in advance.

    John

    Friday, September 14, 2018 6:36 PM
  • Greetings SharePoint Friends,

    I uninstalled the following KB's and was able to get my 2010 workflows to function again. I am not sure which one or if all three needed to be uninstalled but here we are.

    KB4457135
    KB4457033
    KB4457042

    Please let me know if you find which particular one was the culprit.

    Best of luck!

    John

    Monday, September 17, 2018 11:47 AM
  • These are the three updates that worked for me as well. I removed KB4457034 and KB4457045, rebooted, but no luck. Removed KB4457026, rebooted, back in action. Not sure the if the culprit is KB4457026 or the combination of the three but that did the trick for me.
    Monday, September 17, 2018 3:33 PM
  • Resolution from Microsoft:

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

    This helped me to get workflow running again.

    Tuesday, September 18, 2018 9:33 AM
  • This worked for me perfectly. Do a find  on "targetFx version="v4.0" in the web.config file to take you directly to the right place not what i did and search "system.workflow" as there are too many of them.
    Wednesday, September 19, 2018 6:50 AM
  • The updates are split into 3 distinct updates, this is why I could not find for an uninstall. The KB article shows which of the 3 numbers you will need to uninstall. I used the wusa /uninstall /kb:numberGoesHere command to get these off my machines and it resolved the issue. You could use the GUI also to uninstall the 3 related KB's though too.

    KB4458613 (KB4457009, KB4457017, and KB4457015) also seems to cause the same problem KB4457920 did. I didn't try the fix but uninstall them again from my farm and it seems to be working again.

    Wednesday, September 26, 2018 2:48 PM
  • Removal of the following updates fixes the issue, until further notice:

    From last week: KB4457034
    From yesterday: KB4457056, KB4457026, KB4457045,
    From today: KB4457129

    Friday, September 28, 2018 6:37 PM
  • I think it's better now using the PowerShell script in this article https://blogs.msdn.microsoft.com/rodneyviana/2018/09/13/after-installing-net-security-patches-to-address-cve-2018-8421-sharepoint-workflows-stop-working instead of uninstalling the security updates.
    • Edited by Lucian85 Friday, September 28, 2018 6:57 PM
    Friday, September 28, 2018 6:56 PM
  • The script didn't work for us, only uninstall of the .net patches worked. 

    What is the path forward at this point?


    @Elwha101

    Tuesday, October 2, 2018 1:14 PM
  • We are facing some other issues with this patch on SP 2013 farm.

    Drop off library functionality is not working fine and content types mapping also.

    Valuable suggestions are appreciated.

    Thanks

    San


    • Edited by Santoo G Wednesday, October 3, 2018 5:36 PM
    Wednesday, October 3, 2018 5:36 PM
  • @elwha, There are 3 scripts, 2 on GitHub, one in KB 4465015. Which did you run, what parms and what, if any errors were generated (or dropped in EventVwr, ULS)? I would keep checking Rodney's blog to see if others have run in to the same/similar issue and what resolution they have.

    As for the long-term fix, it is currently being worked, but no established time-frame for release. I suspect (my opinion only, so don't hold me to it), that it will be out before end of calendar year.

    -- AntGut

    Refs:


    Thursday, October 4, 2018 3:38 AM