A SharePoint Server 2013 workflow goes into a canceled state when you start an existing SharePoint Server 2007 or SharePoint Server 2010 workflow

Article translations Article translations
Article ID: 2738553 - View products that this article applies to.
Expand all | Collapse all


Consider the following scenario.
  • You use the "Start a List Workflow" or "Start a Site Workflow" action from the Microsoft SharePoint Server 2013 Workflow Platform to start an existing SharePoint Server 2007 or SharePoint Server 2010 workflow.
  • You gain access to the list or site workflow's local variables.
  • The String data type or the List Item ID data type is used. However, its value is null. 
In this scenario, the SharePoint 2013 workflow goes into a canceled state, and the following exception is displayed on the Workflow Status page:
Source at Microsoft.Activities.GetDynamicValueProperty`1.Execute(CodeActivityContext context)
at System.Activities.CodeActivity`1.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager)
at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)
Note This issue does not occur for other data types.


To work around this issue, use the "Set Workflow Variable" action to make sure that the String data type and the List Item ID data type are not empty.


Article ID: 2738553 - Last Review: November 16, 2012 - Revision: 1.0
Applies to
  • Microsoft SharePoint Server 2013
kbsurveynew kbtshoot kbexpertiseinter KB2738553

Give Feedback


Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com