Workflow was cancelled by System Account. Workflow failed to start

Frank Martin 481 Reputation points
2025-03-24T07:20:13.99+00:00

I am using SharePoint 2010 SPD workflow on SharePoint 2016. Today I noticed that any new workflows are failing to start. Existing workflows are working fine. Is there a known bug/issue which is causing this? Because a day ago some patches/updates were installed by server team and now I am unable to start workflows. There is no information in logs.

SharePoint Workflow
SharePoint Workflow
SharePoint: A group of Microsoft Products and technologies used for sharing and managing content, knowledge, and applications.Workflow: An orchestrated and repeatable pattern of business activity, enabling data transformation, service provision, and information retrieval.
661 questions
{count} votes

2 answers

Sort by: Most helpful
  1. Emily Du-MSFT 51,781 Reputation points Microsoft External Staff
    2025-03-24T09:49:49.1333333+00:00

    It looks like you are also experiencing workflow issues after updating for SharePoint Server 2016.

    You might experience an issue in which SharePoint workflows can’t be restated because the unauthorized type is blocked. The issue also generates event tag “c42q0” in SharePoint Unified Logging System (ULS) logs.

    To work around this issue, register the safe types in the Web.config file. You can look for event tag “c42q0” in ULS logs to find the blocked type. If the type and assembly are safe, add the type to the authorized list in the Web.config file.

    For example:

    <System.Workflow.ComponentModel.WorkflowCompiler>
       <authorizedTypes>
         <targetFx version="v4.0">
            <authorizedType Assembly="Microsoft.SharePoint.WorkflowActions, Version=16.0.0.0, Culture=neutral, PublicKeyToken=null" Namespace="Microsoft.SharePoint.WorkflowActions.WithKey" TypeName="*" Authorized="True" />
        </targetFx>
       </authorizedTypes>
    
    

    Reference:

    https://blog.stefan-gossner.com/2024/09/13/trending-issue-problems-with-workflows-after-applying-september-2024-cu-for-sharepoint-2016-2019-se/


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  2. Frank Martin 481 Reputation points
    2025-04-06T11:47:53.6233333+00:00

    Today I started getting following error:

    Potentially malicious xoml node: <ns2:BuildAssignmentsXmlActivity __Context="{ActivityBind ROOT,Path=__context}" Value="&lt;my:Assignments xmlns:my=&quot;http://schemas.microsoft.com/office/infopath/2003/myXSD&quot; xmlns:pc=&quot;http://schemas.microsoft.com/office/infopath/2007/PartnerControls&quot;&gt;&lt;my:Assignment&gt;&lt;my:Assignee&gt;&lt;pc:Person&gt;&lt;pc:DisplayName/&gt;&lt;pc:AccountType/&gt;&lt;pc:AccountId&gt;[%ID4522.ReturnValue%]&lt;/pc:AccountId&gt;&lt;/pc:Person&gt;&lt;/my:Assignee&gt;&lt;my:Stage&gt;0&lt;/my:Stage&gt;&lt;my:AssignmentType&gt;Serial&lt;/my:AssignmentType&gt;&lt;/my:Assignment&gt;&lt;/my:Assignments&gt;" ReturnValue="{x:Null}" x:Name="ID4521" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" xmlns:ns2="clr-namespace:Microsoft.Office.Workflow.Actions;Assembly=Microsoft.Office.Workflow.Actions, Version=16.0.0.0, Culture=neutral, PublicKeyToken=null" />
    

    Added following entry in web.config, restarted timer job, restarted workflow but same issue.

    <authorizedType Assembly="Microsoft.Office.Workflow.Actions, Version=16.0.0.0, Culture=neutral, PublicKeyToken=null" Namespace="Microsoft.Office.Workflow.Actions" TypeName="*" Authorized="True" />
    

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.