When attempting to copy a workflow, Sharegate displays the following error message:
An element associated with the workflow cannot be found.
|Any error code ending with: -117
This error can happen when a file required by the workflow is not found, or, when a list referenced by the workflow (such as the task or history list) is not found. It generally means that the source workflow is currently in a corrupted state. For this reason, the ShareGate migration tool cannot copy it.
- For system (out-of-the-box) workflows - Go to SharePoint in your browser and navigate to the settings of the problematic workflow. Make sure the selected Task List and History List (if applicable) are valid and save the workflow. It is best practice to save the workflow even if it appears valid since SharePoint will fix broken references when you do.
For Sharepoint 2007 workflows built with SharePoint Designer - Open SharePoint Designer and connect to your source site. Find the problematic workflow and publish it without making any changes. SharePoint Designer will correct the broken references and you should then be able to copy the workflow with ShareGate.
Note: As of November 2021, ShareGate is no longer able to provide full support for SharePoint Server 2003 and 2007, which are past the end of their Microsoft support lifetime. For more information, see Contacting our technical support team.
- For Sharepoint 2010 and more recent versions workflows built with Sharepoint Designer - Open Sharepoint Designer and connect to your source site. Find the problematic workflow and open it. In the Settings section, make sure that existing lists are selected in the Task List and History List fields. Publish the workflow. SharePoint Designer will correct the broken references and you should then be able to copy the workflow with ShareGate.
It is possible that SharePoint Designer will give you an error when trying to publish the workflow. This would mean that the workflow is currently invalid and that it needs to be fixed before ShareGate can copy it. Such a workflow can normally not be run, so it is possible that it is simply a workflow that is no longer used and that can be safely ignored when migrating.