Ask Learn
Preview
Ask Learn is an AI assistant that can answer questions, clarify concepts, and define terms using trusted Microsoft documentation.
Please sign in to use Ask Learn.
Sign inThis browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
After delivering the internal Workflow trainings, I have compiled a list of troubleshooting actions for workflow support with SharePoint 2013. The actions below apply to the “new” workflows (workflows living in the Workflow Manager, based on Windows Workflow Foundation 4.0). These actions are not relevant for the “legacy” workflows (SharePoint 2010, using .NET Framework 3.5).
1. Look in the Workflow History list, eg "https://sp2013/Lists/Workflow History". Do you find any errors in there?
2. Is the user account starting the workflow correctly synchronized in the user profile database?
3. Is the user account starting the workflow different from the Worflow Manager setup account? (more info at https://technet.microsoft.com/en-us/library/jj658588.aspx#section7)
4. Are the User Profile Service and App Management Service started? See the green frames in the screenshot below, taken from Central Administration \ Manage Services on Server:
5. Are the App Management Service Application and User Profile Service Application started? Their proxies should be started as well. See the green frames in the screenshot below, taken from Central Administration \ Manage Services on Server:
Note that this is unsupported in a production environment, but very useful in a test environment!
In the SharePoint page workstat.aspx, copy the field requestor id
1. In the URL query parameter from the worsktat.aspx page, copy the instanceid field
2. Open the WFInstanceManagementDB database with SQLManagement Studio, then request from the DebugTrace table
3. The exception is in the WorkflowStatusDetail column
In Central Admin\ Service Applications \ Workflow Service Application Proxy: check the status. Does it read Workflow is Connected as in the below screenshot?
On a server member of the Workflow Manager farm:
1. Start Workflow Manager PowerShell
2. Run the get-WFStatus command
3. Are the statuses Running, as on the screenshot below?
On the SharePoint 2013 server, start Internet Explorer, and check whether the Oauth metadata is accessible. The url is like https://wfm1:12291/$SYSTEM/$Metadata/json/1 . Below an example:
It is possible to check from Internet Explorer that the scopes are registered. It is also possible to navigate the workflow data. The example URLs below allow to check these elements:
The GUIDs in the above URLs are not static.
The tool below provides an easy navigation in the workflow manager data:
https://code.msdn.microsoft.com/windowsdesktop/Workflow-Resource-Browser-a67b1d27
On a Workflow Manager server, you have to run the Workflow-Resource-Browser as administrator.
I hope this checklist will help you while setting up and troubleshooting workflow!
For French readers, the French version of this post is accessible at https://blogs.technet.com/b/french_sharepoint_gbs_blog/archive/2014/01/06/diagnostique-des-workflows-2013.aspx
Anonymous
June 04, 2014
How do I find the SharePoint page workstat.aspx?
Anonymous
October 19, 2015
Typo - "get-WFStatus" should be "Get-WFFarmStatus". This is correct in the screenshot but wrong in the text.
Ask Learn is an AI assistant that can answer questions, clarify concepts, and define terms using trusted Microsoft documentation.
Please sign in to use Ask Learn.
Sign in