

The script name is:Īdd-CodeDomAuthorizedTypeToOWSTimerConfig.ps1 Note No line needs to be uncommented for this one. if you have the problem though, you need to rerun the script if a new machine is added to the farm.

This one should only run if you see the symptoms in ULS logs with process OWSTIMER.EXE. You do not need to undo the change before applying the SharePoint patch addressing it. The change is a permanent requirement from now on since the WF patch. Even if a new WFE is added to the farm, the entries will also be included in web.config. New web applications created after that will also include the changes. All web.config files related to SharePoint on all servers will be modified. The script needs to run only once on any WFE. If you have Nintex workflows you should run like this:Īdd-CodeDomAuthorizedType -IncludeNintexWorkflow PFE, put together this PowerShell script: For 2013, at c:\program files\common files\microsoft shared\web server extensions\ 15.

For SharePoint 2016, it is normally at c:\program files\common files\microsoft shared\web server extensions\ 16. The Hive Folder will change by version of SharePoint.

If you notice that the application showing the error is ULS logs in OWSTIMER.EXE, you should also include the authorized types in \bin\. Please notice that sometimes SharePoint Timer Service (SPTimerV4) runs workflows. The solution is to add explicitly the types to all web applications’ web.config: However, after the update, the following lines are necessary for SharePoint 2013 and beyond: 01:59:07.57 w3wp.exe (0x1868) 0x22FC SharePoint Foundation Workflow Infrastructure 72fs Unexpected RunWorkflow: : NET Security Only patch to resolve CVE-2018-8421 (Remote Code Execution Vulnerability), all SharePoint out of the box Workflows fail to execute and the log will show an error like this: I will update this post with my findings once this latest fix is applied.
