SharePoint 2016, Sharepoint 2013, Sharepoint 2010, Windows Server 2012, Sql Server 2012,2014,IIS, Active Directory,User Profile Service, Managed MetaData Service, Search Service, Topology, Web Application, IIS, Site collection, List, Library, PowerShell, office web app, Windows Authentication, NTLM, Kerberos, Saml, ADFS, Active Directory Import, MIM, UnRegister and Register Workflow Manager with SharePoint 2013 /2016 – SharePoint

UnRegister and Register Workflow Manager with SharePoint 2013 /2016

We had an issue where Workflow manager proxy is not working and getting the following error

“SharePoint 2013 workflow requires a compatible workflow service configured with SharePoint such as Workflow Manager. The workflow service is either not installed or not configured.” Like this

I am not sure who it happens, we did some certificate update and all of sudden this happen.

I decide to run the Register-SPworkflowService one time to register the proxy. But I ends up with the following error:

“Register-SPWorkflowService : Failed to register because the farm or partition is already registered with a workflow service

At line:1 char:1
+ Register-SPWorkflowService -SPSite
https://ke-sit.krossfarm.com/sites/Workfl
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidData: (Microsoft.Share…WorkflowService:
RegisterSPWorkflowService) [Register-SPWorkflowService], ConfigurationExce  ption   + FullyQualifiedErrorId : Microsoft.SharePoint.WorkflowServices.PowerShell
.RegisterSPWorkflowService ”

I run the command with –Force parameter, this time, is successfully completed but still I am getting the same error in the Central admin.

Resolution:

Clearly, we have to unregister and re-register the Workflow Proxy.

  • Un-Register Workflow proxy
    • Go to Central Admin > Application Management > Manage Service Application > Click on the Workflow Service Application Proxy
    • Select it and from Ribbon click delete
  • Register the Workflow Proxy
    • Now run the Register-SPWorkflowService in the PowerShell window, I would recommend to use –Force parameter.

You may also like...

Leave a Reply

Your email address will not be published. Required fields are marked *