SharePoint 2013 Workflow goes into cancelled state

I want to test a workflow that copys current list item to a new libary. But as soon as
it starts it goes into cancelled state like this:
what could be the problem?

Hi Marcsimm,
Try this
The error text that pasted indicates that you're getting access denied on workflow calling back to SharePoint.
Workflow uses signed security tokens to authenticate. The SharePoint Web Application must be claims enabled and not use Forms Based Authentication (which is a requirement of SharePoint OAuth).
Because the response header only includes WWW-Authenticate: NTLM it would seem that SharePoint is not configured for server-to-server authentication (http://technet.microsoft.com/en-us/library/jj219546.aspx)
Thanks
Sivakarunanithi

Similar Messages

  • 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

  • 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

  • 401 Unauthorized Error When calling a SharePoint REST web service from SharePoint 2013 Workflow

    We have our Workflow Manger installed on the same server as our SharePoint 2013 WFE development environment. When creating a SharePoint 2013 Workflow all Calls to a SharePoint 2013 REST web service results in a 401 Unauthorized error.
    As an example I created a simple workflow that should return a JSON result. The REST Url returns the results in the browser without error.
    Set Variable:webServiceUrl to https://<hostnamedsitecollection>/_vti_bin/client.svc/web/lists/getbytitle('ISR%20Approvers')/Items?$select=Title&$filter=Title%20eq%20%27General%27
    then Build{...} Dictionary (Output to Variable:requestHeaders)
    then Call [%Variable:webServiceUrl%] HTTP web service with request (ResponseContent to Variable:responseContent |ResponseHeaders to responseHeaders | ResponseStatusCode to Variable:responseCode)
    The RequestHeader is set to the requestHeaders variable though the web service call properties
    then Log Variable:responseCode to the workflow history list
    After manually running the workflow in SharePoint on a list item in the ISR Approvers list it Logs "Unauthorized" in the Workflow History Log. It does this with every SharePoint REST web service call that I have tried through the workflow.
    It doesn't have anything to do with the Workflow Manger being installed on the same machine as the SharePoint WFE does it?
    Thank You for any insight

    Hi,
    According to your post, my understanding is that you had 401 Unauthorized Error when calling a SharePoint REST web service from SharePoint 2013 Workflow.
    Please make sure you use the ‘Call HTTP Web Service’ correctly.
    You can enter the URL into the brower to check whether it is correctly.
    You need to
    create the Request header requestHeaders
    using a Dictionary:
    Accept : application/json;odata=verbose
    Content-Type : application/json;odata=verbose
    To associate the
    requestHeaders variable, select the Call action
    property, set the RequestHeaders property to
    requestHeaders.
    Please refer to the following articles:
    Working with Web Services in SharePoint 2013 Workflows using SharePoint Designer 2013
    Calling the SharePoint 2013 Rest API from a SharePoint Designer
    Workflow
    In addtion, you need to make sure you install the workflow manager correctly.
    More information:
    Install and configure workflow for SharePoint Server 2013
    Known Issues in Workflow Manager 1.0
    Troubleshooting Workflow Manager 1.0 Management and Execution
    Best Regards,
    Linda Li
    Linda Li
    TechNet Community Support

  • SharePoint 2013 Workflow Permission

    We are running into a problem with SharePoint 2013 and workflows.
    We have the following site collection setup:
    Site Collection
        Subsite A
        Subsite B
    The following are the permissions:
    [Site Collection] Owners
    [Site Collection] Members
    [Site Collection] Vistors
    The members of these SharePoint groups are Active Directory security groups. If we put these AD groups into the SharePoint group we get the following error when trying to run a workflow:
    RequestorId:
    171a693d-7b50-a70a-0000-000000000000. Details: RequestorId: 171a693d-7b50-a70a-0000-000000000000.
    Details: An unhandled exception occurred during the execution of the workflow
    instance. Exception details: System.ApplicationException: HTTP 401
    {"error":{"code":"-2147024891, System.UnauthorizedAccessException","message":{"lang":"en-US","value":"Access
    denied. You do not have permission to perform this action or access this
    resource."}}}
    {"Transfer-Encoding":["chunked"],"X-SharePointHealthScore":["0"],"SPRequestGuid":["171a693d-7b50-a70a-ba75-67ea8bc83fb4"],"request-id":["171a693d-7b50-a70a-ba75-67ea8bc83fb4"],"X-FRAME-OPTIONS":["SAMEORIGIN"],"MicrosoftSharePointTeamServices":["15.0.0.4481"],"X-Content-Type-Options":["nosniff"],"X-MS-InvokeApp":["1;
    RequireReadOnly"],"Cache-Control":["max-age=0,
    private"],"Date":["Tue, 16 Jul 2013 15:28:13
    GMT"],"Server":["Microsoft-IIS\/8.0"],"WWW-Authenticate":["NTLM"],"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
    Obviously, this is a permissions issue. I am able to resolve the issue by adding individuals to the SharePoint group 1 by 1, however, I don't want to do this. Can anyone explain why this is acting the way it is?

    Hi,
    I am also running into this issue and am stuck in solving it.
    I have a list workflow that runs on item change event, checks if a certain value is true and then should create a new list item in a list on a different site.
    Site structure is the same as Hhancocks:
    Site Collection
       Subsite A => workflow
       Subsite B => list where new item should be created
    With the same HTTP REST call I can create a new item on any list of Subsite A, but as soon as I try to create the item on a list in Subsite B, I get the response Code "Unautherized" and the response:
    {"error":{"code":"-2147024891, System.UnauthorizedAccessException","message":{"lang":"en-US","value":"Access denied. You do not have permission to perform this action or access this
    resource."}}}
    I found the following blogs on the internet, none of which solved my issue:
    http://www.sharepointviking.com/system-unauthorizedaccessexception-when-running-sharepoint-2013-workflows/
    http://www.sharepointmaestra.com/Blog/Post/1/Workflow-2013-Not-Starting-on-Incoming-Email
    According to this thread:
    http://community.office365.com/en-us/forums/148/p/178921/527970.aspx the REST calls don't work in SharePoint online which would explain the behaviour in one of our environments, but the error also occurs for our on prem environment. The user triggering
    the workflow has full control on both subsites.
    Any hints would be really appreciated.

  • 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

  • Workflow goes into incorrect status RESERVED

    Hi,
    We have gone live with the MSS (PCRs) in June and we have a situation where the manager is trying to approve a PCR and when he clicks on the link (which takes him to the approval screen), he receives a NULL error and in the backend the workflow goes into the status 'RESERVED'.
    Has anybody come across this situation? Can this be security related?
    Any information related to this will be appreciated.
    Regards,
    SC

    Hi Intekhab,
    If you are working with workflows for the first time, you can follow below approach
    (To add to the statements of Murali and Abdullah)
    1. If you are able to track the related workflow log, Extras->Technical Data will give you the workflow template number
    2. Next take this template number and open it through SWDD transaction and analyze the IDOC process setup in your system. Please goto the step where they are checking the IDOC success/failure, the next steps will have the notifications setup.
    (In case you are unable to track the workflow log, try to identify the business process / workflow template related to IDOC errors/notifications in your system, your functional consultant can also help to identify the object involved-> go through the object docs to understand the process)
    - For further info, please paste WF log screenshot
    Hope it helps ...
    ~Haider~

  • 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.

  • SharePoint 2013 Workflows

    Hi there
    I seem to be having trouble running any workflows using the 2013 engine in SharePoint Designer. The 2010 workflows work fine, however I cannot seem to get the 2013 ones to even start. Looking at the list/library settings, I can see the workflow has been
    added but for whatever reason it doesn't seem to start.
    I cannot even go back into a list item to view the workflow either...
    Where to I even begin to try to unravel this mystery? HELP!! :-)
    Many thanks in advance.

    SharePoint 2013 Workflow engine has undergone a drastic change. Before you begin developing workflows in SharePoint 2013 you must ensure you
    have taken care of the pre-requisites.
    Ensure you have gone through each points in this article in configuring your Workflow Manager 2013:
    https://technet.microsoft.com/en-us/library/jj658588.aspx
    Before you start installing/developing SharePoint Workflows in 2013 you should to know few important points:
    Never use ‘System Account’ to develop/run workflow, the workflow will fail to run.
    You should not use ‘System Account’ to test the workflow.
    You need to make sure User Profile Service (UPS) is running and the user who is running workflow has a profile created in UPS. Workflow Manager use UPS under
    the hood.
    Make sure App Management Service is created and running. You don’t need to configure SharePoint 2013 App settings in the server, just creating App Management
    service (with proxy) will do.
    Make sure the hidden feature WorkflowServiceStore is enabled.
    Enable-SPFeature -Identity WorkflowServiceStore –Url $yourUrl
    Note: To register Workflow Server with SharePoint, a SharePoint site collection URL is provided. Apparently it seems, each and every site collection need to be registered
    with workflow server. But it’s not, registering a single SharePoint site collection, will enable workflow manager for all SharePoint web applications/site collections.
    Now you can check from above listed points, which points resolves your issue.
    More detailed troubleshooting steps on SP workflows 2013:
    http://blogs.msdn.com/b/vincent_runge/archive/2014/01/07/troubleshooting-actions-for-sharepoint-2013-workflows.aspx
    Please remember to click 'Mark as Answer'
    if the reply answers your query or 'Upvote' if it helps you.

  • 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 for page publishing

    Hi Folks,
    I need to implement a page publishing workflow.I am going in brief to explain scenario.
    When a page is getting created by a user from a specific group it needed to be approved by four different group of people in a sequential approach.
    After getting approval from all group only last user group member should be authorized to publish the page.
    There could be a scenario where once page is created it will require to be directly published without any approval
    Kindly suggest me which approach i should follow ? 
    Either of SharePoint designer workflow or Visual Studio Workflow ?
    Appreciate if can provide some tutorial kind link or suggestion.
    Keshav Roy

    There's not really too many examples out there to share for SharePoint 2013 workflows. Personally I believe SharePoint Designer workflow is an quick and easy of developing workflows but it has limitations - like it's tightly integrated with the SharePoint
    site/list. However if you have an existing Visual Studio project then I don't see any reason to use SharePoint Designer (SPD) workflow. Visual Studio workflow is more like developer tools and you can do more with VS than SPD. So if you have developer
    skills (or someone in your team), have already a VS project and need more customisation (as per your requirements, you have complex one), I would prefer to go for Visual Studio workflow.
    Thanks,
    Sohel Rana
    http://ranaictiu-technicalblog.blogspot.com

  • 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 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

  • Sharepoint 2010 Workflow successful: Sharepoint 2013 Workflow UNsuccessful:

    Observation 1 
    1. I created 2 workflows that write "completed" to the workflow history 
    a. 1 workflow uses sp2010 workflow manager 
    b. 1 workflow uses sp2013 workflow manager 
    2. sp2010 workflow works fine; it will start either manually or automatically (when a new item is created ) without issue; "completed' is written to the log as expected. Good. 
    3. sp2013 does not start automatically (when a new item is created ); when trying to start manually I get error message "Something went wrong. To try again, reload the page and then start the workflow." Which I do, but still fails.
    Bad. 
    4.On Workflows.aspx I can see the links to start the 2 workflows manually. 
    a. When I hover over the sp2010 workflow link I can see something that look like this: 
    http://playground/sites/falcontt/_layouts/15/IniWrkflIP.aspx?List={ae95de8e-508b-4aa6-b4b6-490288e35e9f}&ID=53&ItemGuid={697E4218-D889-4FB8-A27B-D188F5D93250}&TemplateID={199c3d86-89a8-4286-b285-37e2d2067b52}&Source=http%3A%2F%2Fplayground%2Fsites%2Ffalcontt%2FLists%2FTrouble%2520Tickets%2Fall%2520requests%2Easpx 
    b. But when I hover over the sp2013 workflow link I can see something that look like this: 
    javascript:StartWorkflow4('949cb889-9b46-4959-9673-842e60cc5a42', '53', '{697E4218-D889-4FB8-A27B-D188F5D93250}') 
    Should this link also look similar to the sp2010 workflow link? If so, do you have any idea why it is different? 
    Observation 2 
    In Sharepoint Designer 2013, when I goto Navigation -> Workflows and click on the 2010 workflow, I see a file listed under "Forms" that looks like this "sp2010 test workflow.xsn". By the way the name of the workflow happens
    to be "sp2010 test workflow". 
    But when I goto Navigation -> Workflows and click on the 2013 workflow, I see a NO file listed under "Forms". Should I see "sp2013 test workflow.xsn" listed there? If yes, can you think of why it is not listed there? 
    I saved the workflow debug logs from Event Viewer but won't share that info here unless necessary, to avoid making things look more complicated than they have to be. 
    Thanks for any comments suggestions, tips, questions, anything, etc. 
    Thanks and have a great weekend. 
    George 

    Hi George,
    First of all, I'd like to clarify that workflow manager is dedicated for SharePoint 2013 workflow platform. SharePoint 2010 workflow is integrated in SharePoint server, while 2013 workflow is based on a new platform named workflow manager server.
    In SharePoint 2013 designer, 2010 workflow has forms while 2013 workflow doesn't have forms.
    For this issue, I suspect there is something incorrect with workflow manager. From the error message "Something went wrong. To try again, reload the page and then start the workflow",  please flush the DNS cache via executing
    IPCONFIG /FLUSHDNS, and restart workflow manager related services such as below, then recreate 2013 workflow to test the issue:
    Service Bus Gateway
    Service Bus Message Broker
    http://blog.houratious.com/2014/05/sharepoint-2013-workflow-something-went.html
    Regards,
    Rebecca Tu
    TechNet Community Support

Maybe you are looking for