locked
Workflow Start "Failed But Not Blocking Correlation" - Project Server workflow for Demand Management RRS feed

  • Question

  • Hi,

    I'm trying to "Create a Project Server workflow for Demand Management" with project server 2013 just like is explained here.

    But when I try to create a new project the implemented workflow failed to start with the follow state message in the job queue: Failed But Not Blocking Correlation.

    The detailed error display the follow message:

    • Exception Starting Workflow: The scope _/SharePoint/default/139e833f-7a85-4ccf-b7a2-b3fea9ce50b9/6799b7e5-e519-40f4-9371-0b3bc3d5c208_ has no workflows under it. HTTP headers received from the server - ActivityId: 52fef415-409b-4545-a9f6-ed75519b425c. NodeId: My-Computer-Name. Scope: /SharePoint/default/139e833f-7a85-4ccf-b7a2-b3fea9ce50b9/6799b7e5-e519-40f4-9371-0b3bc3d5c208. Client ActivityId : 9ded4d9c-7733-7004-2661-c8977270af98.. Trace:    at Microsoft.Workflow.Client.ClientHelpers.SendRequest[T](HttpWebRequest request, T content)   at Microsoft.Workflow.Client.WorkflowManager.StartInternal(String workflowName, WorkflowStartParameters startParameters)   at Microsoft.SharePoint.WorkflowServices.FabricWorkflowManagementClient.StartInstance(String serviceGroupName, String workflowName, String monitoringParam, String activationKey, IDictionary`2 payload)   at Microsoft.SharePoint.WorkflowServices.FabricWorkflowInstanceProvider.StartWorkflow(WorkflowSubscription subscription, IDictionary`2 payload)   at Microsoft.Office.Project.Server.BusinessLayer.Workflow.StartWorkflow(Guid projectGuid, Guid enterpriseProjectTypeUid, Boolean isNewProject, Guid previousEntepriseProjectTypeUid, Boolean skipStage, Guid stageToSkipTo):
      • WorkflowExceptionStartingWorkflow (35115). Details: id='35115' name='WorkflowExceptionStartingWorkflow' uid='e3bbb06b-1d38-e311-940a-001cc094718e'.
    • Error:
      • WorkflowCannotStartWorkflow (35100). Details: id='35100' name='WorkflowCannotStartWorkflow' uid='e4bbb06b-1d38-e311-940a-001cc094718e'.
    • Queue:
      • GeneralQueueJobFailed (26000) - WorkflowStartWorkflow.WorkflowStartWorkflowMessage. Details: id='26000' name='GeneralQueueJobFailed' uid='e5bbb06b-1d38-e311-940a-001cc094718e' JobUID='68ee1040-1d38-e311-940a-001cc094718e' ComputerName='90f7432c-fbc8-4ebd-86f3-0236ce62661c' GroupType='WorkflowStartWorkflow' MessageType='WorkflowStartWorkflowMessage' MessageId='1' Stage='' CorrelationUID='9ded4d9c-7733-7004-2661-c8977270af98'. For more details, check the ULS logs on machine 90f7432c-fbc8-4ebd-86f3-0236ce62661c for entries with JobUID 68ee1040-1d38-e311-940a-001cc094718e.

    with this detailed entries in the log file

    10/18/2013 13:47:57.38  Microsoft.Office.Project.Server (0x0948) 0x14F0 Project Server                 Queue                          ad3fy Critical Standard Information:PSI Entry Point: <unknown>  Project User: <unknown>  Correlation Id: <unknown>  PWA Site URL:   SA Name: <unknown>  PSError: <unknown> A queue job has failed. This is a general error logged by the Project Server Queue everytime a job fails - for effective troubleshooting use this error message with other more specific error messages (if any), the Operations guide (which documents more details about queued jobs) and the trace log (which could provide more detailed context). More information about the failed job follows. GUID of the failed job: 68ee1040-1d38-e311-940a-001cc094718e. Name of the computer that processed this job: 90f7432c-fbc8-4ebd-86f3-0236ce62661c (to debug further, you need to look at the trace log from this computer). Failed job type: WorkflowStartWorkf... 9ded4d9c-7733-7004-2661-c8977270af98
    10/18/2013 13:47:57.38* Microsoft.Office.Project.Server (0x0948) 0x14F0 Project Server                 Queue                          ad3fy Critical ...low. Failed sub-job type: WorkflowStartWorkflowMessage. Failed sub-job ID: 1. Stage where sub-job failed:  (this is useful when one sub-job has more than one logical processing stages). 9ded4d9c-7733-7004-2661-c8977270af98
    10/18/2013 13:47:57.38  Microsoft.Office.Project.Server (0x0948) 0x14F0 Project Server                 Queue Jobs                     ad3fy Medium   Error is: GeneralQueueJobFailed. Details: Queue Attributes:  68ee1040-1d38-e311-940a-001cc094718e  90f7432c-fbc8-4ebd-86f3-0236ce62661c  WorkflowStartWorkflow  WorkflowStartWorkflowMessage  1    9ded4d9c-7733-7004-2661-c8977270af98  . Standard Information: , LogLevelManager Warning-ulsID:0x000DD158 has no entities explicitly specified. 9ded4d9c-7733-7004-2661-c8977270af98

    Any idea?

    Thanks in advance,

    Alexander.

    Friday, October 18, 2013 6:12 PM

Answers

All replies

  • Hi Alexander,I have seen that error when the workflow manager has not been registered correctly with the PowerShell command - that should be in the docs referenced - or http://technet.microsoft.com/en-us/library/jj663115.aspx.  Let me know if that doesn't appear to be the issue here and I can dig deeper.  Best regards,  Brian

    Blog | Facebook | Twitter | Posting is provided "AS IS" with no warranties, and confers no rights.
    Project Server TechCenter | Project Developer Center | Project Server Help | Project Product Page

    Saturday, November 2, 2013 10:18 AM
  • Thanks,

    I just re-run

    Register-SPWorkflowService -SPSite http://my-dev-computer/PWA -WorkflowHostUri https://my-dev-computer:12290/ -AllowOAuthHttp -Force

    and re-publish (seems required) the workflow and the workflow started.

    Tuesday, November 5, 2013 8:09 PM
  • Any tips for solving this when working with Project Online as i can't run powershell commnads.  My specific error is:

    Queue:
    • GeneralQueueJobFailed (26000) - ReportWorkflowProjectDataSync.ReportWorkflowProjectDataSyncMessage. Details: id='26000' name='GeneralQueueJobFailed' uid='9d6dc743-ceeb-e311-9b5c-00155d106622' JobUID='1c9e882f-ceeb-e311-af4a-00155d108023' ComputerName='02b0f3f8-f77e-456d-a9ac-05661d71fa92' GroupType='ReportWorkflowProjectDataSync' MessageType='ReportWorkflowProjectDataSyncMessage' MessageId='1' Stage='' CorrelationUID='05c2bf83-6ec1-d424-8aeb-6d212d0a5b39'. For more details, check the ULS logs on machine 02b0f3f8-f77e-456d-a9ac-05661d71fa92 for entries with JobUID 1c9e882f-ceeb-e311-af4a-00155d108023.

    Cheers

    Matt

    Wednesday, June 4, 2014 11:27 AM
  • Matt - we have been experiencing workflow bad behavior since day 1. Unexplained or non-traceable errors, stalls, custom field issues, etc.  very poor performance as well.

    Are you still using PWA ?

    As of today, Microsoft had admitted an issue and a fix is planned;...we'll see about that.

    Tuesday, November 3, 2015 3:29 PM
  • Hi Alexander,

    I am facing the same issue as you faced before<gs class="GINGER_SOFTWARE_mark" ginger_software_uiphraseguid="a04fb5a8-46dc-4c5b-bfc8-dd0d48c0aea4" id="a4cdd661-f57c-488d-8cd5-46b37fc19bd5">.</gs> I have created the Same workflow as you mentioned above.

    Did the issue resolved once we re-run the workflow manager?

    Kindly do let me know.

    Thanks


    Soumya T | EPM Consultant

    Wednesday, January 13, 2016 9:22 AM
  • Hi all, I'm facing a similar issue.

    The Workflow can save and publish still from SharePoint Designer.

    The Workflow services are all running as per normal on all nodes (2x nodes)

    No specific errors in the event log.

    I can access 12291 site successfully.

    I have restarted the workflow services on all nodes after running the command with the correct site my details:

    Register-SPWorkflowService -SPSite http://my-dev-computer/PWA -WorkflowHostUri http://my-dev-computer:12291/ -AllowOAuthHttp -Force

    I have also done an IIS reset, and restarted the app pools, and restarted the workflow site.

    I had no success thus far and would greatly appreciate assistance with resolving the issue, as I cannot track where this is going wrong, and what I need to do to get it resolved without rebuilding everything.

    Regards

    Hendrik

    All the logs give me is the following:

    Microsoft.Workflow.Client.WorkflowCommunicationException:
    The request was aborted: The request was canceled.

    SharePoint.WorkflowServices.FabricWorkflowManagementClient.StartInstance(String serviceGroupName, String workflowName, String monitoringParam, String activationKey, IDictionary`2 payload)     at Microsoft.SharePoint.WorkflowServices.FabricWorkflowInstanceProvider.StartWorkflow(WorkflowSubscription subscription, IDictionary`2 payload) StackTrace:  at microsoft.office.server.native.dll: (sig=678c0f87-966f-4d99-9c94-b49e788d2672|2|microsoft.office.server.native.pdb, offset=131CE) at microsoft.office.server.native.dll: (offset=21BE5)     2a26149e-53f4-2073-8316-6a08b794ee5d

    08/30/2017 00:57:13.85          Microsoft.Office.Project.Server (0x05EC)    0x16A8            SharePoint Server                         Unified Logging Service         c91s    Monitorable     Watson bucket parameters: SharePoint Server 2013, ULSException14, 044806dd "sharepoint server", 0f0011db "15.0.4571.0", 09d02580 "microsoft.workflow.client", 01009cc3 "1.0.40131.0", 52ef34cc "mon feb 03 08:18:52 2014", 0000005e "0000005e", 00000144 "00000144", 3e6aa606 "workflowcommunicationexception", 0021c2c4 "ai2le"            2a26149e-53f4-2073-8316-6a08b794ee5d

    08/30/2017 00:57:13.85          Microsoft.Office.Project.Server (0x05EC)    0x16A8            Project Server                            Project Server Workflow       ai7z      Medium           Error is: WorkflowExceptionStartingWorkflow. Details: Exception Starting Workflow: The request was aborted: The request was canceled. Client ActivityId : 2a26149e-53f4-2073-8316-6a08b794ee5d.. Trace:    at Microsoft.Workflow.Client.ClientHelpers.SendRequest[T](HttpWebRequest request, T content)     at Microsoft.Workflow.Client.WorkflowManager.StartInternal(String workflowName, WorkflowStartParameters startParameters)     at Microsoft.SharePoint.WorkflowServices.FabricWorkflowManagementClient.StartInstance(String serviceGroupName, String workflowName, String monitoringParam, String activationKey, IDictionary`2 payload)     at Microsoft.SharePoint.WorkflowServices.FabricWorkflowInstanceProvider.StartWorkflow(WorkflowSubscription subscription, IDictionary`2 payload)     at Microsoft.Office.Pr...        2a26149e-53f4-2073-8316-6a08b794ee5d

    08/30/2017 00:57:13.85*         Microsoft.Office.Project.Server (0x05EC)    0x16A8            Project Server                            Queue                                     ad3fy   Critical ...low. Failed sub-job type: WorkflowStartWorkflowMessage. Failed sub-job ID: 1. Stage where sub-job failed:  (this is useful when one sub-job has more than one logical processing stages).          2a26149e-53f4-2073-8316-6a08b794ee5d

    08/30/2017 00:57:13.85          Microsoft.Office.Project.Server (0x05EC)    0x16A8            Project Server                            Queue Jobs                            ad3fy   Medium           Error is: GeneralQueueJobFailed. Details: Queue Attributes:  db58f345-0d8d-e711-9489-00505683a4d7  6aba3e1c-091a-4cf6-b7fa-15ab78608d56  WorkflowStartWorkflow  WorkflowStartWorkflowMessage  1    2a26149e-53f4-2073-8316-6a08b794ee5d  . Standard Information: , LogLevelManager Warning-ulsID:0x000DD158 has no entities explicitly specified.            2a26149e-53f4-2073-8316-6a08b794ee5d

    Thursday, September 7, 2017 5:13 AM