Workflow Manager Farm-Failed Registration Clean Up

2017-12-11T14:47:05+00:00 September 23rd, 2013|Azure, Cloud, Sharepoint|

This is a follow-up post of my previous “SharePoint 2013 and Workflow Manager Farms” blog back May 2013. When certain activities fail in the SharePoint world, some actions are not always rolled back fully. This can leave a messy trail, for this post we will take a failed attempt to execute the Register-SPWorkflowService cmdlet as an example.

  • Navigate to Central Administration > Security > Manage Trust
  • You will be presented with a bunch of Trusted Service Consumer entries without friendly names, such as in the image below

image

I was recently charged with finding the root cause of these “unknown” entries. Sure enough, there were problems implementing the Workflow Manager Farm and (showing off now) my blog post was followed to get it working. As it turns out, these entries were simply a result of the previous failed attempts. As only one site was registered, with no critical Workflows being used, we simply removed it then¬†cleaned up the Manage Trust entries and re-registered it.

Clean Up

The clean up process is pretty easy, but as always I warn you against making changes to your systems if you are unsure of the repercussions of doing it incorrectly. Additionally, removing / un-registering Workflow Services can halt, break, etc Workflows in the Farm.

  1. Un-register the Workflow Service for the site
  2. Navigate to Central Administration > Security > Manage Trust
  3. Highlight the row by clicking the anchor link, it doesn’t work like other row selections in SharePoint (rather annoyingly)
  4. Click Delete from the ribbon
  5. Repeat steps 2 and 3 until all the “unfriendly” entries (assuming you’re not already using some)
  6. Enjoy the nice clean Manage Trust pane

image

Now all that’s left it to re-register those Workflow Services!