SharePoint 2007/2010/2013 – Workflows Failing with ‘Did not Begin’ Error

We not too long ago up to date our SharePoint occasion with the newest replace and realised that abruptly all of our workflows have been beginning to throw a ‘Did not Begin’ standing, which upon additional investigation, it was discovered that we have been seeing the next error within the SharePoint ULS Logs –

Kind System.CodeDom.CodeBinaryOperatorExpression just isn’t marked as licensed within the software configuration file.

Answer

SharePoint 2013

After a little bit looking on-line I found that the problem lies throughout the net.config for our SharePoint deployment and will be simply fastened by including the next Licensed Assemblies –

<authorizedType Meeting=”System, Model=4.0.0.0, Tradition=impartial, PublicKeyToken=b77a5c561934e089″ NameSpace=”System.CodeDom” TypeName=”CodeBinaryOperatorExpression” Licensed=”True” />

<authorizedType Meeting=”System, Model=4.0.0.0, Tradition=impartial, PublicKeyToken=b77a5c561934e089″ NameSpace=”System.CodeDom” TypeName=”CodePrimitiveExpression” Licensed=”True” />

<authorizedType Meeting=”System, Model=4.0.0.0, Tradition=impartial, PublicKeyToken=b77a5c561934e089″ NameSpace=”System.CodeDom” TypeName=”CodeMethodInvokeExpression” Licensed=”True” />

<authorizedType Meeting=”System, Model=4.0.0.0, Tradition=impartial, PublicKeyToken=b77a5c561934e089″ NameSpace=”System.CodeDom” TypeName=”CodeMethodReferenceExpression” Licensed=”True” />

<authorizedType Meeting=”System, Model=4.0.0.0, Tradition=impartial, PublicKeyToken=b77a5c561934e089″ NameSpace=”System.CodeDom” TypeName=”CodeFieldReferenceExpression” Licensed=”True” />

<authorizedType Meeting=”System, Model=4.0.0.0, Tradition=impartial, PublicKeyToken=b77a5c561934e089″ NameSpace=”System.CodeDom” TypeName=”CodeThisReferenceExpression” Licensed=”True” />

<authorizedType Meeting=”System, Model=4.0.0.0, Tradition=impartial, PublicKeyToken=b77a5c561934e089″ NameSpace=”System.CodeDom” TypeName=”CodePropertyReferenceExpression” Licensed=”True” />

As soon as added to the net.config, make sure to restart IIS for the change to take impact.


SharePoint 2007 & SharePoint 2010

SharePoint 2007 & SharePoint 2010 additionally at the moment have the identical situation, which will be resolved by following the identical steps as above however by including the next licensed assemblies to net.config as a substitute.

<authorizedType Meeting=”System, Model=2.0.0.0, Tradition=impartial, PublicKeyToken=b77a5c561934e089″ NameSpace=”System.CodeDom” TypeName=”CodeBinaryOperatorExpression” Licensed=”True” />

<authorizedType Meeting=”System, Model=2.0.0.0, Tradition=impartial, PublicKeyToken=b77a5c561934e089″ NameSpace=”System.CodeDom” TypeName=”CodePrimitiveExpression” Licensed=”True” />

<authorizedType Meeting=”System, Model=2.0.0.0, Tradition=impartial, PublicKeyToken=b77a5c561934e089″ NameSpace=”System.CodeDom” TypeName=”CodeMethodInvokeExpression” Licensed=”True” />

<authorizedType Meeting=”System, Model=2.0.0.0, Tradition=impartial, PublicKeyToken=b77a5c561934e089″ NameSpace=”System.CodeDom” TypeName=”CodeMethodReferenceExpression” Licensed=”True” />

<authorizedType Meeting=”System, Model=2.0.0.0, Tradition=impartial, PublicKeyToken=b77a5c561934e089″ NameSpace=”System.CodeDom” TypeName=”CodeFieldReferenceExpression” Licensed=”True” />

<authorizedType Meeting=”System, Model=2.0.0.0, Tradition=impartial, PublicKeyToken=b77a5c561934e089″ NameSpace=”System.CodeDom” TypeName=”CodeThisReferenceExpression” Licensed=”True” />

<authorizedType Meeting=”System, Model=2.0.0.0, Tradition=impartial, PublicKeyToken=b77a5c561934e089″ NameSpace=”System.CodeDom” TypeName=”CodePropertyReferenceExpression” Licensed=”True” />


 

For additional info I’d counsel referring to Rodney Viana’s wonderful put up on this which will be discovered on the hyperlink beneath, It’s value noting this situation is thought by Microsoft and is at the moment being labored on.

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

 

LEAVE A REPLY

Please enter your comment!
Please enter your name here