Most of the forums and blogs I came across when troubleshooting this issue referred to workflows created in SharePoint Designer and then imported into Visual Studio before deploying. They refer to removing the lines containing the AssociationUrl, InstatiationUrl and ModificationUrl.
I did not have any of these lines in my xml files so obviously that was not my issue.
On further troubleshooting I noticed some conflict between the existing content types (from a previous version of the workflow) and the new content types being created.
As a workaround to this issue, when adding the workflow I selected a new Task list instead of using the default task list.
I now no longer received the above error and the workflow is working correctly.
I will continue investigating the issue regarding the conflicting content types. I will update this blog once I know more but for now I have a working workflow.
This comment has been removed by the author.
ReplyDeleteI came across the same issue today after I packaged a reusable workflow as a WSP file and deployed it onto another farm. I also had no AssociationUrl, InstatiationUrl and ModificationUrl in the Elements.xml file but I did discover the xml contained the following: InstantiationUrl="_layouts/IniWrkflIP.aspx"
ReplyDeleteI removed the line from the Elements.xml and packaged and deployed the workflow and reactivated the feature and this time it worked like a charm.