3

When I add an "if condition" to my working workflow, It doesn't work anymore and gives error: "Failed to Start". (Workflow was canceled by System Account.)

My "if condition" is in below image framed by blue, when I add blue section, workflow doesn't start. Can you help please ?

enter image description here

Improve this question
2
  • 1
    Try to Log in and start the workflow as a different user (rather than System Account) to test & check if it is working for you or not.
    – Hardik
    Jul 1, 2016 at 8:40
  • @Hardik Someone else tried to start the workflow, it did not work. The error is same
    – HOY
    Jul 1, 2016 at 8:46

2 Answers 2

Reset to default
5

For your issue, I recommend to follow the steps as below:

  1. Clear SharePoint Designer cache: How to Clear Your SharePoint Designer 2010/2013 Cache
  2. Deactivate all "Workflow" features at the Site Collection level.
  3. Enable all "Workflow" features at the Site Collection level.
  4. PSCONFIG (Not Necessary) (or run the SharePoint 2010 products configuration wizard)
  5. Delete the bad workflow.
  6. Create a new workflow on the list with an valid user.
Improve this answer
3
  • Did you tried above steps? Is that works for you?
    – Hardik
    Jul 1, 2016 at 9:48
  • Just step 1 resolved it, there was no need for other steps!
    – HOY
    Jul 1, 2016 at 10:17
  • Same issue here, just step 1 was enough :) Again weird behaviour of SP....
    – M.P.
    Aug 21, 2018 at 13:15
3

In case it might be helpful for someone:

I had a similar problem with a client today in a SP 2013 environment, but in my case turned out that it was a .Net security update that caused it.

The solution after this update was to add some types to the web.config file on the SharePoint server:

<authorizedType Assembly="System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" NameSpace="System.CodeDom" TypeName="CodeBinaryOperatorExpression" Authorized="True" />
<authorizedType Assembly="System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" NameSpace="System.CodeDom" TypeName="CodePrimitiveExpression" Authorized="True" />
<authorizedType Assembly="System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" NameSpace="System.CodeDom" TypeName="CodeMethodInvokeExpression" Authorized="True" />
<authorizedType Assembly="System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" NameSpace="System.CodeDom" TypeName="CodeMethodReferenceExpression" Authorized="True" />
<authorizedType Assembly="System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" NameSpace="System.CodeDom" TypeName="CodeFieldReferenceExpression" Authorized="True" />
<authorizedType Assembly="System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" NameSpace="System.CodeDom" TypeName="CodeThisReferenceExpression" Authorized="True" />
<authorizedType Assembly="System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" NameSpace="System.CodeDom" TypeName="CodePropertyReferenceExpression" Authorized="True" />

Here's the Microsoft article for reference:

SharePoint workflows stop working after you install .NET security updates for CVE-2018-8421

Improve this answer

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.