SharePoint 2013 Workflow Not Updating on Deployment

Developing a 2013 Workflow on SharePoint 2013 using Visual Studio 2012, deploying workflow changes does not update the workflow that runs. This has already been posted on the SP 2013 dev forum, but I wanted to check here with the workflow folks. Anyone run
into this issue before and/or have tips for solving?
Thanks.
http://social.msdn.microsoft.com/Forums/en-US/sharepointdevelopment/thread/cd543a00-f3ab-4a4a-8682-b81d8330b677
http://blog.randomdust.com

This issue is reported and I'll post about it once I have an update. For now to workaround this issue, you can try these steps
Change the default deployment option to “No Activation”
Retract the solution using Visual Studio
Deploy the solution. This time feature will not be activated by default as we have changed to “No Activation”
Open the SharePoint designer and click on the “Workflow” section. You will see your workflow already present there. Delete the workflow which you have created.
Activate the feature manually.
Now you should see your updated version.
Chandrasekar Natarajan

Similar Messages

Sharepoint 2013 Workflow not available on Site created from Sharepoint 2013 Foundation Solution Template

If I create a template on SharePoint 2013 Foundation, then create a site on SharePoint Enterprise (or Office/365) fully configured to support SharePoint 2013 workflows. When I access the site through SharePoint Designer 2013, and attempt to create a workflow
SharePoint 2013 Workflows are not available -- you get message that SharePoint 2013 Workflow platform is not available because it is not configured on the server. This appears to be a bug in SharePoint Designer as the 2013 Workflows are available on the team
site on the same site collection. There is no reason that a site created from a SharePoint 2013 foundation template should have this restriction.   To make matters worse if you then save that site as a template on the SharePoint 2013 Enterprise (or
Office/365) system and create a new site from the that template you get the same issue.
Anyone know a workaround/fix to this issue.   Have imported the template into Visual Studio but I can not find any way in Visual Studio to enable SharePoint 2013 workflows.   A solution that involves Visual Studio import would work fine
for me.
Earllibby

Apparently you did not read my question very carefully.   The workflow manager is configured properly on this server and for the basic Team site in this site collection the full SharePoint 2013 workflows are available in SharePoint Designer 2013.
BUT they are not available on another site in the SAME SITE COLLECTION that was created from a solution template that was created on a SharePoint Foundation server.
Earllibby

SharePoint 2013 Workflows not working

Hi All,
I am currently attempting to get SharePoint 2013 workflows working, i have installed the workflow manager and linked it to SharePoint but when i run any 2013 workflow i get the following error:
RequestorId: 26c49394-eb06-737a-7fde-d5bbfe4f6505. Details: System.ApplicationException: HTTP 401 The remote server returned an
error: (500) Internal Server Error. {"SPRequestGuid":["8c76bcc4-3979-41a9-ae18-7221aa418528"],"request-id":["8c76bcc4-3979-41a9-ae18-7221aa418528"],"X-FRAME-OPTIONS":["SAMEORIGIN"],"SPRequestDuration":["24"],"SPIisLatency":["0"],"Server":["Microsoft-IIS\/8.0"],"WWW-Authenticate":["Bearer
realm=\"8de50181-fbf8-48a5-9cd6-5edb37403fbd\",client_id=\"00000003-0000-0ff1-ce00-000000000000\",trusted_issuers=\"00000005-0000-0000-c000-000000000000@*,[email protected]37403fbd\"","NTLM"],"X-Powered-By":["ASP.NET"],"MicrosoftSharePointTeamServices":["15.0.0.4569"],"X-Content-Type-Options":["nosniff"],"X-MS-InvokeApp":["1;
RequireReadOnly"],"Date":["Thu, 04 Sep 2014 09:46:31 GMT"]} at Microsoft.Activities.Hosting.Runtime.Subroutine.SubroutineChild.Execute(CodeActivityContext context) at System.Activities.CodeActivity.InternalExecute(ActivityInstance
instance, ActivityExecutor executor, BookmarkManager bookmarkManager) at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)
Its worth noting that 2010 workflow run without a problem.
Any help would be greatly appreciated
Thanks
Jamie

Hi,
Based on your description, my understanding is that when you ran SharePoint 2013 workflow, an error occurred.
You can try to re-register the Workflow Service.
Here is
a link about how to configure workflow for SharePoint Server 2013, you can use as a reference:
http://technet.microsoft.com/en-us/library/jj658588(v=office.15).aspx
Best Regards,
Lisa Chen

SharePoint Online workflow not starting

Hi All,
I am an administrator for a company and I have been asked to create a workflow for them.
I created 2 workflows using SharePoint designer 2013. The 2010 workflow works as expected.
I created the 2013 workflow because I can use loops. However the 2013 workflow doesn't automatically start when an item is created. but works if I start it manually. I have checked and made sure that the check box is ticked for the workflow to start automatically.
The workflows go like this.
Step: Query Type
If Current Item:Query_Type equals Phone
  Set Status to Opportunity
Else
If Current Item:Query_Type equals Email
  Email Current Item:Sales_Rep2
  Pause for 0 days, 0 hours, 15 minutes
  If Current Item:Follow_Up equals No
   Email Current Item:Sales_Rep2
Step: Rental or Not
If Current Item:Rental equals Yes
  Email Current Item:Sales_Rep2
  Pause for 0 days, 1 hours, 0 minutes
  If Current Item:Quote_Sent equals No
   Email Current Item:Sales_Rep2
  Else
  If Current Item:Rental equals No
   Email Current Item:Sales_Rep2
   Pause until Current Item:Date to Send Quote
   Email Current Item:Sales_Rep2
And the 2013 one goes like this
Stage:Follow Up
Loop: Email to manager
  The contents of this loop will run repeatedly while: Current Item:Follow_Up equals No
   Pause for 0 days, 1 hours, 0 minutes
   If Current Item:Follow_Up equals No
    Email Current Item:Manager
If Current Item:Follow_Up equals Yes
  Set Status to Opportunity
Transition to stage
Go to Rental or Not
Stage:Rental or Not
Loop: Escalation
  The contents of this loop will run repeatedly while: Current Item:Quote_Sent equals No
   Pause for 2 days, 0 hours, 0 minutes
   If Current Item:Quote_Sent equals No
    Email Current Item:Manager
Loop: Escalation
  The contents of this loop will run repeatedly while: Current Item:Quote_Sent equals No
   Pause for 7 days, 0 hours, 0 minutes
   If Current Item:Quote_Sent equals No
   and Current Item:Date to Send Quote is greater than Current Item:Date to Send Quote
    Email Current Item:Manager
Transition to stage
Go to End of Workflow
If this makes sense? If not can anybody give me advice on how to get this working the way it is expected to work?

Hi,
From your description, After you modified the workflow and added "App Step" to it and "Pause" actions apart from few other modifications, you got the issue that
SharePoint 2013 Workflow not starting when a new item is crated.
Whether you got the issue Before you modified the workflow.
I have done a test in my SharePoint 2013 and it works fine.
I suggest you update SharePoint to the latest CU.
Here is an blog similar with your issue, you can use as a reference:
http://blogs.msdn.com/b/sridhara/archive/2014/08/19/fix-sharepoint-2013-workflow-recursion-prevention-part-1.aspx
Best Regards,
Lisa Chen
Lisa Chen
TechNet Community Support

SharePoint 2013 workflow deployment doens't update workflow definition

In Visual Studio 2013, we can develop SharePoint 2013 workflow and deploy directly in SharePoint. However, once a workflow is deployed and later modified and redeployed, the modified workflow definition doesn't take effects. Even if you retract the solution
and redeploy, the associated workflow with the sharepoint solution doesn't get updated in the SharePoint. Retracting the SharePoint solution then restarting the development server and finally redeploying will reset the workflow definition.

try this link:
https://connect.microsoft.com/VisualStudio/feedback/details/779905/sharepoint-2013-workflow-deployment-doenst-update-workflow-definition
http://www.sharepointeurope.com/blog/2011/8/30/5-easy-ways-to-turn-sharepoint-workflow-solution-into-a-failure-by-pawe%C5%82-wr%C3%B3bel-datapolis
http://ranaictiu-technicalblog.blogspot.in/2013/02/sharepoint-2013-workflow-manager.html
according to links workflow is cached in site so delete it from designer also.

Updating In-Flight SharePoint 2013 Workflows (Visual Studio)

Is there any guidance on the best strategy for upgrading in-flight SharePoint 2013 Workflows? I am currently developing a SharePoint 2013 Workflow using Visual Studio 2012. The workflow has 6 phases and may take up to a month to complete.
I need a plan for when I will inevitably need to make a change to the workflow.
I am concerned that simply deploying a new version of a WSP with new XAML might cause a breaking change to in-flight workflows. This was a major problem in 2007/2010, and in the past I have created a new version of the workflow when deploying a change.
SharePoint 2013 designer workflows automatically create a new version when published, but unfortunately with Visual Studio workflows this is not the case. Updating the WSP and reactivating the feature will force new workflow code to run, but I think
this could cause issues when the workflow state data is de-serialized.

Hi,
According to your post, my understanding is that you want to update in-flight SharePoint visual studio workflow.
To update the in-flight workflow, such as in the production environment, we can do the steps as below(Make sure you test this first on a DEV server).
Updated the solution (Update-SPSolution)
Disabled the feature(Disable-SPFeature)
Enabled the feature again (Enable-SPFeature)
Then the existing workflow would use the old version workflow, the new workflow instances would use the new version workflow definition.
For more information:
https://social.technet.microsoft.com/Forums/en-US/f3ae607b-a16c-477e-9c2f-f0dc76f6849f/updating-sharepoint-2013-workflow-in-production-environment-not-during-development?forum=sharepointdevelopment
More reference:
http://sp2013workflows.blogspot.com/2014/06/update-workflow-definition-in.html
Thanks,
Jason
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Jason Guo
TechNet Community Support

SharePoint 2013 workflow can not be completed

I use Visual studio 2013 to create an sharepoint 2013 workflow and just insert a single task into it. I fill the assignto property directly and the account does recieve the mail. Then I approve the created task but the workflow is still there and it can't
be completed after that. I have spend several days just try to make the workflow completed but I can't. Any clues?

Hi Kevin,
As I know, there's two properties for task - one is Status with values 'In Progress', 'Completed' etc. Another property is 'Task outcome' with values 'approved' and 'rejected'. Task created by SignleTask, wait for task completion which means status field
should have value 'Completed' and then workflow will consider the task as complete. In your case I'm not sure if you have set the task status as completed or not. If you set the task status to completed only then workflow will consider the task as completed.
However, in your case you can set the property 'WaitForTaskCompletion' to false and just after SignleTask you can use other activity like - wait for item event or wait for field change, to find out if the task out field is 'approved' or 'rejected'. You can
put the activity in a loop and in the loop you can wait till due date or until the task-outcome is approved/rejected.
Thanks,
Sohel Rana
http://ranaictiu-technicalblog.blogspot.com

SharePoint 2013 Workflow Lookup Column Error

When I try to use the value from a lookup column (e.g. display the selected value in the body of a email) in a SharePoint 2013 workflow I receive the following error. It works fine if I use the SharePoint 2010 workflow platform, but I always receive a error
with 2013.
First Error:
Retrying last request. Next attempt scheduled in less than one minute. Details of last request: HTTP NotFound to http://portal.test.com/sites/Test/_vti_bin/client.svc/web/lists/getbyid(guid'00000000-0000-0000-0000-000000000000')/Items(10)?%24select=ID%2CLookupId%2CLookup%2FTitle&%24expand=Lookup
Correlation Id: 3fb1bac9-f4b6-bbf1-a664-b3748668ea3c Instance Id: e7b4064d-029d-4a8b-9a75-7939f10e8817
<script type="text/javascript">// <![CDATA[ var errorMessage = "Something went wrong. To try again, reload the page and then resume
the workflow."; var dlg = null; function RetryWorkflow4(instanceName) { showDialog(); var ctx = SP.ClientContext.get_current(); var wfManager = SP.WorkflowServices.WorkflowServicesManager.newObject(ctx, ctx.get_web()); var instanceService = wfManager.getWorkflowInstanceService();
var instance = instanceService.getInstance(instanceName); instanceService.resumeWorkflow(instance); ctx.executeQueryAsync( function(sender, args) { closeDialog(); theForm.submit(); }, function (sender, args) { closeDialog(); alert(errorMessage); } ); } //
]]> </script>
Error from SharePoint Logs:
Microsoft.SharePoint.SPException: List does not exist. The page you selected contains a list that does not exist.
It may have been deleted by another user. ---> System.Runtime.InteropServices.COMException: List does not exist.
The page you selected contains a list that does not exist.
It may have been deleted by another user.     at Microsoft.SharePoint.Library.SPRequestInternalClass.GetListsWithCallback(String bstrUrl, Guid foreignWebId, String bstrListInternalName, Int32 dwBaseType, Int32 dwBaseTypeAlt,
Int32 dwServerTemplate, UInt32 dwGetListFlags, UInt32 dwListFilterFlags, Boolean bPrefetchMetaData, Boolean bSecurityTrimmed, Boolean bGetSecurityData, Boolean bPrefetchRelatedFields, ISP2DSafeArrayWriter p2DWriter, Int32& plRecycleBinCount)
    at Microsoft.SharePoint.Library.SPRequest.GetListsWithCallback(String bstrUrl, Guid foreignWebId, String bstrListInternalName, Int32 dwBaseType, Int32 dwBaseTypeAlt, Int32 dwServerTemplate, UInt32 dwGetListFlags, UInt32
dwListFilterFlags, Boolean bPrefetchMetaData, Boolean bSecurityTrimmed, Boolean bGetSecurityData, Boolean bPrefetchRelatedFields, ISP2DSafeArrayWriter p2DWriter, Int32& plRecycleBinCount)
--- End of inner exception stack trace ---
at Microsoft.SharePoint.SPGlobal.HandleComException(COMException comEx)
at Microsoft.SharePoint.Library.SPRequest.GetListsWithCallback(String bstrUrl, Guid foreignWebId, String bstrListInternalName, Int32 dwBaseType, Int32 dwBaseTypeAlt, Int32 dwServerTemplate, UInt32 dwGetListFlags, UInt32 dwListFilterFlags, Boolean bPrefetchMetaData,
Boolean bSecurityTrimmed, Boolean bGetSecurityData, Boolean bPrefetchRelatedFields, ISP2DSafeArrayWriter p2DWriter, Int32& plRecycleBinCount)
at Microsoft.SharePoint.SPListCollection.EnsureListsData(Guid webId, String strListName)
at Microsoft.SharePoint.SPListCollection.ItemByInternalName(String strInternalName, Boolean bThrowException)
at Microsoft.SharePoint.SPListCollection.GetListById(Guid uniqueID, Boolean bThrowException)
at Microsoft.SharePoint.SPListCollection.get_Item(Guid uniqueID)
at Microsoft.SharePoint.SPListCollection.GetList(Guid uniqueId, Boolean fetchMetadata)
at Microsoft.SharePoint.SPListCollection.GetById(Guid uniqueId)
at Microsoft.SharePoint.ServerStub.SPListCollectionServerStub.InvokeMethod(Object target, String methodName, ClientValueCollection xmlargs, ProxyContext proxyContext, Boolean& isVoid)
at Microsoft.SharePoint.Client.ServerStub.InvokeMethodWithMonitoredScope(Object target, String methodName, ClientValueCollection args, ProxyContext proxyContext, Boolean& isVoid)
at Microsoft.SharePoint.Client.Rest.RestRequestProcessor.InvokeMethod(Boolean mainRequestPath, Object value, ServerStub serverProxy, EdmParserNode node, Boolean resourceEndpoint, MethodInformation methodInfo, Boolean isExtensionMethod, Boolean isIndexerMethod)
at Microsoft.SharePoint.Client.Rest.RestRequestProcessor.GetObjectFromPathMember(Boolean mainRequestPath, String path, Object value, EdmParserNode node, Boolean resourceEndpoint, MethodInformation& methodInfo)
at Microsoft.SharePoint.Client.Rest.RestRequestProcessor.GetObjectFromPath(Boolean mainRequestPath, String path, String pathForErrorMessage)
at Microsoft.SharePoint.Client.Rest.RestRequestProcessor.Process()
at Microsoft.SharePoint.Client.Rest.RestRequestProcessor.ProcessRequest()

Hi
XantosX5 ,
Thank you for your posting!
According to your description, I try to reproduce your scenario in my SharePoint Server 2013 environment.
I create a lookup column in a list and create a workflow 2013 for the list. In the workflow, I add Send an email action. Then I display the lookup column in the body of the email as the below figure:
When I start the workflow, it works fine.
Have you installed
the workflow manager 1.0 cumulative update 1 ? It can be the point. If not, please install it.
Thank you for your understanding and support.
Best Regards,
Eric
Eric Tao
TechNet Community Support

Custom SharePoint 2013 workflow activities in site template throw error on site creation

Hi all,
I have created a number of custom activities for SharePoint 2013 Workflows and I am using them on an Office 365 environment. The custom activities are packaged as a sandbox solution and deployed on my Office 365 site. Everything works as expected.
I have now created a site with all the functionality I need, including some Site and List workflows - all of them containing my custom activities. I saved the site as a template - including content - and the process was completed successfully.
My problem is that when I try to create a site based on that template, I get the following error:
Microsoft.Workflow.Client.ActivityNotFoundException: The activity named 'WorkflowXaml_66b9230b_823e_4783_82b8_daf481237847' from scope '/spo/d42a4487-9465-4347-9f2c-a2718e92fc02/74d0f9e7-fb35-493d-86fb-ab7aa27da7e0/c2e1bf45-cf67-4e13-9755-421cf92395f8'
was not found. HTTP headers received from the server - ActivityId: 0997496a-5a15-4b83-82eb-727881eefa67. NodeId: . Scope: . Client ActivityId : c82f6e9c-9f8f-808b-7679-f2c0f92a339d. ---> System.Net.WebException: The remote server returned an error
After a number of trials and errors, I am certain that this relates to my custom activities. i have already tested all of the following scenarios:
Delete the workflow with the custom actions: Site is created successfully.
Create a new workflow with no custom actions and save the site as a template:
Site is created successfully.
Save the site template including a workflow with my custom activities, but not including content:
Site is created successfully, but my workflow is not there.
Create a new custom workflow activities sandbox with one custom activity that just writes something to the history list - just to make sure that this is not related to any specific solution. Save the site as a template:
Site creation throws the same error.
Packaged my workflow (with my custom activities) as a wsp from SharePoint Designer and deployed it as a custom solution. Activated the feature in the target site. The workflow gets created and executing finally. Saved the site as template: Site
creation throws the same error.
Same as above, but without activating the feature in the target site: Site created successfully, workflow works fine after I activate the feature in the new site.
My custom activities feature is always enabled in the site I save as template - in all of the above scenarios.
I have tested all of the above scenarios both on SharePoint 2013 on-premise and Office 365. There is
a forum post regarding some inconsistencies in the wsp file, but unfortunately this is not my case. Am I doing something wrong? Are custom 2013 workflow activities not supported in site templates - which would not actually make any sense, as it would "break"
the fundamental concept of re-usability.
Any ideas/feedback/guidance?
Thanx in advance

Hi,
I am facing the same issue. Kindly help me out if any of them have solved similar issue.
Your help would be appreciated.
manikantan

SharePoint 2013 Workflow (SPD 2013) fails for Active Directory Group members

Hi
I have a SharePoint 2013 site called "Team Meetings". There are a number of lists and an InfoPath form library.
The site's SharePoint Group "Team Meeting Members" has two Active Directory groups (All Club Managers and All Club Police) as members. Those two AD groups contain all the people that I want to have access to the library and list, except for
a few additional folk who I have made individual members.
My PROBLEM:
I have created a SharePoint 2013 Workflow using SPD 2013 associated with the Form Library. Workflow is set to start on new or modified item. The first action is to write to history list, then determine the status (Submitted or Pending) of
the form and go to different Stages depending on that status.
The workflow works perfectly for any user who has been added directly to the SharePoint group (Team Meetings Members) BUT FAILS at the very first action for anyone who is a member of one of the AD groups. I know the Workflow is fine because I've tested it
with numerous people who are direct members of the SharePoint Group, but whenever a person who is a member of the AD group tries it the Workflow just fails.
Here's a print of the info from the Workflow Status page (I don't have access to server logs):
RequestorId: 4494760f-92ff-2e8c-90d2-cc7df0e6baa4. Details: System.ApplicationException: HTTP 401 {"Transfer-Encoding":["chunked"],"X-SharePointHealthScore":["0"],"SPRequestGuid":["4494760f-92ff-2e8c-90d2-cc7df0e6baa4"],"request-id":["4494760f-92ff-2e8c-90d2-cc7df0e6baa4"],"X-FRAME-OPTIONS":["SAMEORIGIN"],"MicrosoftSharePointTeamServices":["15.0.0.4420"],"X-Content-Type-Options":["nosniff"],"X-MS-InvokeApp":["1;
RequireReadOnly"],"Cache-Control":["max-age=0, private"],"Date":["Mon, 10 Mar 2014 01:31:42 GMT"],"Server":["Microsoft-IIS\/8.0"],"WWW-Authenticate":["NTLM"],"X-AspNet-Version":["4.0.30319"],"X-Powered-By":["ASP.NET"]}
The HTTP response content could not be read. 'Error while copying content to a stream.'. at Microsoft.Activities.Hosting.Runtime.Subroutine.SubroutineChild.Execute(CodeActivityContext context) at System.Activities.CodeActivity.InternalExecute(ActivityInstance
instance, ActivityExecutor executor, BookmarkManager bookmarkManager) at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor
Members of the SharePoint Group "Team Meetings Members" have Contribute Access to both the form library and another list that the workflow writes to as well as the Workflow History list (which in SP 2013 uses the credentials of the
user who started the workflow, unlike 2010 which used System Account).
All members of the Team Meetings Members group, whether they are individual members or part of one of the AD groups, have no problems opening and saving forms etc. It's just the Workflow that doesn't like them...
I am stumped. I've spent many hours searching for a reason for this. There are about 200 people in the two AD groups so I really don't want to have to add them all individually - especially when these groups are managed in AD for a whole bunch of other reasons
and using the AD groups means I'll basically never have to worry about modifying the SharePoint access permissions.
Does anyone have any ideas why this is happening and what I can try to fix it?
Mark

Hi Lars,
I'm afraid not so far but we are trying a few things today so I will post back with results.
First thing we are doing is making the AD Group universal because one of our (external provider) gurus remembers seeing something about that. He also sent me a link to a post where they were talking about earlier
versions but having similar issues and their solution was to make sure the app pool account has sufficient permissions in AD::
http://social.msdn.microsoft.com/Forums/sharepoint/en-US/27a547da-5cc0-49d7-8056-6eb40b4c3242/failed-to-start-workflow-access-is-denied-exception-from-hresult-0x80070005-eaccessdenied
This part of that thread looks interesting but we haven't checked it yet as were trying the universal setting first:
"If the users participating in the workflows have been added to the SharePoint site via Active Directory groups, SharePoint has to update the user’s security token periodically by connecting to
the domain controller. By default, the token times out every 24 hours. But if the application pool account did not have the right permissions on the domain controller to update the user’s token, user will keep getting the access denied error. The error was
intermittent because when the user browsed to any page other than the workflow form, the token was getting updated successfully.
You can try to fix it through granting the application pool account the appropriate permission by adding the account to the group “Windows Authorization Access Group” in Active Directory."
I'll update when we try these ideas. If you have any luck please do the same.
Mark
(sorry about formatting - using my phone....)
Mark

Problem refering to a custom activity in a SharePoint 2013 workflow

I have created a few custom activities to handle common tasks in a workflow. The activities are deployed in a separate sandbox solution from the workflows referencing them.
This has been working fine for a couple of months now, but suddenly I get an error when trying to activate the feature that provisions the workflow that refers to the custom activity (WriteMessage). The error is:
Error 1
Error occurred in deployment step 'Activate Features': Microsoft.Workflow.Client.ActivityValidationException: Workflow XAML failed validation due to the following errors:
Cannot create unknown type '{wf://workflow.windows.net/default/f0b36ec0-d40f-4df8-a99b-39f6dc4854a8/09e1bc2d-1cc8-4cff-ae22-32a52f54b685/$Activities}WriteMessage'. HTTP headers received from the server - ActivityId: ac291077-6536-4c63-b7b0-7701b6d29268. NodeId:
DKRDSSP15DEV03. Scope: /SharePoint/default/f0b36ec0-d40f-4df8-a99b-39f6dc4854a8/09e1bc2d-1cc8-4cff-ae22-32a52f54b685. Client ActivityId : e9d2bfd0-bb0e-4c28-bf55-8748368feb5b. ---> System.Net.WebException: The remote server returned an error: (400) Bad
Request.
at Microsoft.Workflow.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.Workflow.Client.HttpGetResponseAsyncResult`1.End(IAsyncResult result)
at Microsoft.Workflow.Client.ClientHelpers.SendRequest[T](HttpWebRequest request, T content)
--- End of inner exception stack trace ---
at Microsoft.Workflow.Client.ClientHelpers.SendRequest[T](HttpWebRequest request, T content)
at Microsoft.Workflow.Client.WorkflowManagementClient.SendRequest[T](HttpWebRequest request, T content)
at Microsoft.Workflow.Client.ActivityManager.Publish(ActivityDescription description, Boolean overwriteXClassName, Boolean terminateDependentInstances)
at Microsoft.SharePoint.WorkflowServices.FabricWorkflowManagementClient.PublishActivity(String serviceGroupName, ActivityDescription activity, Boolean overwriteXClass, Nullable`1 terminateInstances)
at Microsoft.SharePoint.WorkflowServices.FabricWorkflowDeploymentProvider.PublishActivity(FabricWorkflowManagementClient client, ActivityDescription activityDefinition, String serviceGroupName)
at Microsoft.SharePoint.WorkflowServices.FabricWorkflowDeploymentProvider.<>c__DisplayClass5.<PublishDefinition>b__4()
at Microsoft.SharePoint.WorkflowServices.WorkflowServiceContextExtensions.InvokeWithEcosystemRetry(WorkflowServicesContext context, EcosystemRequiredMethod method)
at Microsoft.SharePoint.WorkflowServices.FabricWorkflowDeploymentProvider.PublishDefinition(WorkflowDefinition workflowDefinition)
at Microsoft.SharePoint.WorkflowServices.WorkflowDefinitionStorageEventReceiver.PublishDefinition(SPItemEventProperties properties)
0 0
Vestas.SP.CMS.AlarmReports
I have tried creating a simple workflow using the custom activity, by referencing the sandbox solution. This works fine, if I create the simple workflow in a new project and deploys it and activate the workflow feature. However, if I create a similar simple
workflow in the original solution and omit the original workflows. Then I still get the above error when deploying / activating the workflow feature.
How do I clean up my original project so it does not give me this error when deploying and activating the workflow feature?
best regards
Lars Kohsel
Best regards Lars Kohsel

Hi,
As the error still occur when you create a simple workflow in the original project, maybe some configurations have been changed in the project.
You can check with the new created project whether there are some difference configurations in the project.
There is a similar article for your reference.
http://blogs.msdn.com/b/cliffgreen/archive/2013/03/11/sharepoint-2013-workflow-deployment-errors.aspx
What’s more, you can also copy your original project code to the new project, then check whether it works.
If it works, the we can use the new project instead of the original project.
Thanks,
Jason
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Jason Guo
TechNet Community Support

SharePoint 2013 workflow task gets canceled

Just wanted to share my solution to a problem that I was having when creating a SharePoint 2013 Workflow that includes creating a task and assigning it to a group of people. After publishing the workflow and initiating it you get:
Retrying last request. Next attempt scheduled in less than one minute.
Microsoft.SharePoint.Client.ResourceNotFoundException: Cannot find resource for the request sp.utilities.utility.ExpandGroupsToPrincipals
An unhandled exception occurred during the execution of the workflow instance.
  Exception details: System.ApplicationException: HTTP 404 {"error":{"code":"-1, Microsoft.SharePoint.Client.ResourceNotFoundException",
  "message":{"lang":"en-US","value":"Cannot find resource for the request sp.utilities.utility.ExpandGroupsToPrincipals."},
  "innererror":{"message":"Cannot find resource for the request sp.utilities.utility.ExpandGroupsToPrincipals.",
  "type":"Microsoft.SharePoint.Client.ResourceNotFoundException","stacktrace":" at
  Microsoft.SharePoint.Client.Rest.RestRequestProcessor.GetObjectFromPathRoot(Boolean mainRequestPath, EdmParserNode node, Boolean resourceEndpoint, MethodInformation& methodInfo)\u000d\u000a at
  Microsoft.SharePoint.Client.Rest.RestRequestProcessor.GetObjectFromPath(Boolean mainRequestPath, String path, String pathForErrorMessage)\u000d\u000a at
  Microsoft.SharePoint.Client.Rest.RestRequestProcessor.Process()\u000d\u000a at
  Microsoft.SharePoint.Client.Rest.RestRequestProcessor.ProcessRequest()\u000d\u000a at
  Microsoft.SharePoint.Client.Rest.RestService.ProcessQuery(Stream inputStream, IList`1 pendingDisposableContainer)"}}
  } {"Transfer-Encoding":["chunked"],"X-SharePointHealthScore":["0"],"SPClientServiceRequestDuration":["46"]
  ,"SPRequestGuid":["624f66f8-a70c-81db-bf0d-c042443f5435"],"request-id":["624f66f8-a70c-81db-bf0d-c042443f5435"],
  "X-FRAME-OPTIONS":["SAMEORIGIN"],"MicrosoftSharePointTeamServices":["15.0.0.4569"],"X-Content-Type-Options":["nosniff"],
  "X-MS-InvokeApp":["1; RequireReadOnly"],"Cache-Control":["max-age=0, private"],"Date":["Mon, 06 Apr 2015 22:17:23 GMT"],
  "Server":["Microsoft-IIS\/8.0"],"X-AspNet-Version":["4.0.30319"],"X-Powered-By":["ASP.NET"]} at
  Microsoft.Activities.Hosting.Runtime.Subroutine.SubroutineChild.Execute(CodeActivityContext context) at
   System.Activities.CodeActivity.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager) at
   System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)
I was not able to find any answer anywhere, so my solution was:
1. Simply upgrade SharePoint Server 2013 to the latest version which in turn updates Microsoft.Activities.Proxy.dll
2. Clear the SharePoint Designer cache
  Workflow Error - Sharepoint Designer cannot display the item
  http://community.office365.com/en-us/f/154/t/74327.aspx
I hope this is helpful to somebody
Thanks

Hi Amit,
According to your description, my understanding is that you want to approve workflow task using web service in SharePoint 2013.
For troubleshooting this issue, please provide the more detailed code.
Here are some similar posts, please check if they are useful:
http://social.msdn.microsoft.com/Forums/sharepoint/en-US/b999a417-dce3-4590-9173-89aea91f23a3/complete-workflow-after-approving-all-tasks?forum=sharepointdevelopment
http://www.sharepointblog.in/2013/07/programmatically-approvereject-task-in.html
http://aarebrot.net/blog/2011/10/how-sloppiness-and-spworkflowtask-altertask-could-inadvertantly-lock-your-workflow-task/
I hope this helps.
Thanks,
Wendy
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Wendy Li
TechNet Community Support

SharePoint 2013 Workflow created on SharePoint Designer gets canceled

Just wanted to share my solution to a problem that I was having when creating a SharePoint 2013 Workflow that includes creating a task and assigning it to a group of people. After publishing the workflow and initiating it you get:
Retrying last request. Next attempt scheduled in less than one minute.
Microsoft.SharePoint.Client.ResourceNotFoundException: Cannot find resource for the request sp.utilities.utility.ExpandGroupsToPrincipals
An unhandled exception occurred during the execution of the workflow instance.
   Exception details: System.ApplicationException: HTTP 404 {"error":{"code":"-1, Microsoft.SharePoint.Client.ResourceNotFoundException",
   "message":{"lang":"en-US","value":"Cannot find resource for the request sp.utilities.utility.ExpandGroupsToPrincipals."},
   "innererror":{"message":"Cannot find resource for the request sp.utilities.utility.ExpandGroupsToPrincipals.",
   "type":"Microsoft.SharePoint.Client.ResourceNotFoundException","stacktrace":" at
   Microsoft.SharePoint.Client.Rest.RestRequestProcessor.GetObjectFromPathRoot(Boolean mainRequestPath, EdmParserNode node, Boolean resourceEndpoint, MethodInformation& methodInfo)\u000d\u000a at
   Microsoft.SharePoint.Client.Rest.RestRequestProcessor.GetObjectFromPath(Boolean mainRequestPath, String path, String pathForErrorMessage)\u000d\u000a at
   Microsoft.SharePoint.Client.Rest.RestRequestProcessor.Process()\u000d\u000a at
   Microsoft.SharePoint.Client.Rest.RestRequestProcessor.ProcessRequest()\u000d\u000a at
   Microsoft.SharePoint.Client.Rest.RestService.ProcessQuery(Stream inputStream, IList`1 pendingDisposableContainer)"}}
   } {"Transfer-Encoding":["chunked"],"X-SharePointHealthScore":["0"],"SPClientServiceRequestDuration":["46"]
   ,"SPRequestGuid":["624f66f8-a70c-81db-bf0d-c042443f5435"],"request-id":["624f66f8-a70c-81db-bf0d-c042443f5435"],
   "X-FRAME-OPTIONS":["SAMEORIGIN"],"MicrosoftSharePointTeamServices":["15.0.0.4569"],"X-Content-Type-Options":["nosniff"],
   "X-MS-InvokeApp":["1; RequireReadOnly"],"Cache-Control":["max-age=0, private"],"Date":["Mon, 06 Apr 2015 22:17:23 GMT"],
   "Server":["Microsoft-IIS\/8.0"],"X-AspNet-Version":["4.0.30319"],"X-Powered-By":["ASP.NET"]} at
   Microsoft.Activities.Hosting.Runtime.Subroutine.SubroutineChild.Execute(CodeActivityContext context) at
    System.Activities.CodeActivity.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager) at
    System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)
I was not able to find any answer anywhere, so my solution was:
1. Simply upgrade SharePoint Server 2013 to the latest version which in turn updates Microsoft.Activities.Proxy.dll
2. Clear the SharePoint Designer cache
Workflow Error - Sharepoint Designer cannot display the item
   http://community.office365.com/en-us/f/154/t/74327.aspx
I hope this is helpful to somebody
Thanks

Hi,
I doubt its not possible.
http://stackoverflow.com/questions/17925555/windows-workflow-4-appfabrix-1-1-suspended-workflow-will-not-resume
http://social.msdn.microsoft.com/Forums/en-US/fd85c5f9-36dd-4be5-872f-9ba73b1eb0b8/appfabric-11-for-windows-server-versus-workflow-manager-10?forum=wfprerelease
http://seroter.wordpress.com/2012/11/02/interview-series-four-questions-with-jrgen-willis/
Please remember to click 'Mark as Answer' on the answer if it helps you

SPD 2013 Workflow not working

Hello,
I'm running into a very interesting issue, we have a 2013 custom list that has some 2010 and 2013 workflows associated with it. Just until recently the workflows were working fine, but now only 2010 workflows are working.
I updated one of the 2013, tried to publish it but then I canceled the process of publishing it because I had to make a new update.... not sure if this flipped the switch on these but now even if I create new ones in SPD they will not run. Also if
I try to run in manually I get a message - "Something went wrong. To try again, reload the page and then start the workflow"(the option for start manually is enabled in SPD 2013). Any help on this will be greatly appreciated!

Hi Ghabib05,
According to your description, my understanding is that you got an error when you ran a SharePoint 2013 workflow.
Afer you made some change in your workflow, whether you re-published the workflow. if not, please publish it, then test again, compare the result.
Please create a new SharePoint 2013 workflow on the list, then test, compare the result.
If this issue only occurred on the specifical workflow, I suggest you create a new workflow instead of the problematic one.
If this issue occurred on all SharePoint 2013 workflow, you can try to re-register workflow service.
Best Regards,
Wendy
Wendy Li
TechNet Community Support

SharePoint 2013 Workflow for MDS 2012 - Sample Code

Hi All, I want to integrate MDS 2012 with SharePoint 2013 workflow. I have read the whitepaper on this integration but I am looking for code samples on SharePoint 2013 workflow which can be used for this as I am not much into SharePoint development. If
not the source code, any good blog links to achieve this integration?
Thanks, Ashish Singh

If you want to avoid the SharePoint development, then use a custom IWorkflowTypeExtender and interact with SharePoint using the Lists OData service. That way your code runs on the MDS server, and you don't have to deploy custom code to SharePoint.
You would simply add an item to an existing or purpose-built SharePoint list, and that could kick off a standard list workflow (which can be built without custom code).
Otherwise you need to create a custom SharePoint Site Workflow in Visual Studio, and deploy it to SharePoint (yuck). Per:
http://msdn.microsoft.com/en-us/library/ee231573.aspx
David
David http://blogs.msdn.com/b/dbrowne/

SharePoint 2013 Workflow Not Updating on Deployment

Similar Messages

Maybe you are looking for