Error 1  Error occurred in deployment step 'Activate Features': Microsoft.Workflow.Client.ActivityNotFoundException: The activity named 'WorkflowXaml_89a963f7_e111_4556_a869_e7e93faf9414' from scope '/SharePoint/default/13e35c42-cb8c-4efa-a5a0-d0b2f58f85b1/1e1e2094-774b-44bb-b8f0-c6efd9e59449' was not found. HTTP headers received from the server - ActivityId: 09339c55-cbdc-4cb3-89f1-4309531e62e0. NodeId: WINGTIPSERVER. Scope: /SharePoint/default/13e35c42-cb8c-4efa-a5a0-d0b2f58f85b1/1e1e2094-774b-44bb-b8f0-c6efd9e59449. Client ActivityId : 8fba226a-9af7-4b70-
0 0 OPCW.SharePoint
Workflow Service Status is OK.

Solution :
Always remember to click Publish on workflows before saving the wf as a template and also make sure your workflows are associated with lists and library

Comments

Post a Comment

Popular posts from this blog

Metalogix Exception thrown: Server was unable to process request. ---> Value does not fall within the expected range. Solution : Look for app pool .Is posible reset iis .
Read more
REST API The Basics Before it can do anything with SharePoint, your remote Web or mobile application must obtain authorized access. In SharePoint 2013 there are two general approaches to authorizing access to a SharePoint site (regardless of whether you’re using REST). The first approach involves authenticating a SharePoint user, in which case your application has the same access to SharePoint data and capabilities as the user. The different ways you can authenticate a user from a Web or mobile application are outside the scope of this article, but we’ll briefly mention two new options in SharePoint 2013 because they affect the way you construct your REST requests: If you’re calling into SharePoint from a remotely hosted application that can’t use client-side code (HTML and JavaScript) exclusively, and there’s no firewall between SharePoint and your application, you can use OAuth 2.0 tokens with Microsoft Access Control Service (ACS) as the secure token server. If client-side ...
Read more
Image
Allow SharePoint 2013 site to load into IFRAME in non-SharePoint application add the code highligted to all of your master pages if you have multiple masterpages. <WebPartPages:AllowFraming runat="server" />
Read more