SharePoint issues after installing KB4457916 (.NET Update)

Windows Update[German]It seems that .NET security update KB4457916 breaks SharePoint 2010. After installing this security update, the Sharepoint workflow stop working. Here are a few details.


Advertising

Update KB4457916  for .NET Framework

Security update KB4457916 (Security Only 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 and Server 2012 R2) has been released on September 11, 2018. It addressed the .NET Framework Remote Code Execution Vulnerability CVE-2018-8421.

SharePoint 2010 workflow broken after update install

Blog reader Joydeep Roy pointed out in a comment (thanks for that), that .NET Framework security update KB4457916 is causing issues with SharePoint. Rodney Viana from Microsoft has published the blog post After installing .NET security patches to address CVE-2018-8421, SharePoint workflows stop working (KB 4457916) describing issues with SharePoint Server 2010.

After applying .NET Security Only patch KB4457916 to resolve CVE-2018-8421 (Remote Code Execution Vulnerability), all SharePoint out of the box Workflow fails to execute and the log will show an error like this:

09/13/2018 01:59:07.57 w3wp.exe (0x1868) 0x22FC SharePoint Foundation Workflow Infrastructure 72fs Unexpected RunWorkflow: Microsoft.SharePoint.SPException: <Error><CompilerError Line="-1" Column="-1" Text="Type System.CodeDom.CodeBinaryOperatorExpression is not marked as authorized in the application configuration file." /><CompilerError Line="-1" Column="-1" Text="Type System.CodeDom.CodeBinaryOperatorExpression is not marked as authorized in the application configuration file." /><CompilerError Line="-1" Column="-1" Text="Type System.CodeDom.CodeBinaryOperatorExpression is not marked as authorized in the application configuration file." /><CompilerError Line="-1" Column="-1" Text="Type System.CodeDom.CodeBinaryOperatorExpression is not marked as authorized in the application configuration file." /><CompilerError Line="-1" Column="-1" Text="Type System.CodeDom.CodeBinaryOperatorExpression is not marked as authorized in the application configuration file." /><CompilerError Line="-1" Column="-1" Text="Type System.CodeDom.CodeBinaryOperatorExpression is not marked as authorized in the application configuration file." /><CompilerError Line="-1" Column="-1" Text="Type System.CodeDom.CodeBinaryOperatorExpression is not marked as authorized in the application configuration file." /><CompilerError Line="-1" Column="-1"…

Rodney Viana  explains the reason for this error and outlines also a workaround within the blog post.

Similar articles:
Adobe Flash Player version 31.0.0.108 released
Microsoft Office-Updates (September 4, 2018)
Microsoft Security Update Summary September 11, 2018
Patchday: Updates for Windows 7/8.1/Server Sept. 11, 2018
Patchday Windows 10-Updates (September 11, 2018)
Patchday Microsoft Office Updates (September 11, 2018)
Microsoft Patchday: Other Updates September 11, 2018


Advertising

Patchday issues with updates & WSUS (September 11, 2018)


Cookies helps to fund this blog: Cookie settings
Advertising


##1

This entry was posted in issue, Software, Update and tagged , , , . Bookmark the permalink.

6 Responses to SharePoint issues after installing KB4457916 (.NET Update)

  1. Ashley Thompson says:

    Thanks! We kind of figured it was the .NET update but glad to confirm this. Anyone know if there is a PS script to trigger all workflows that Failed on Start by chance?

  2. Anthony G says:

    Rodney Viana's script worked for us. Thank you so much!

  3. Jason says:

    THANK you for this. How irritating to finally find a resolution to one similar KB issue, only for this .NET KB issue to creep in!

  4. Advertising

  5. Robert says:

    Sadly 2010 WF:s still fails after Rodney procedure, anyone facing the same issue?

  6. Jignesh Joshi says:

    Yes, 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.

Leave a Reply to Robert Cancel reply

Your email address will not be published. Required fields are marked *