Header Ads Widget

Responsive Advertisement

Workflow Service Front End is not starting/ Struck on Stating / Stopped.

 Workflow Service Front End is not starting/ Struck on Stating / Stopped. 

Error 1:

 SharePoint 2013 workflows are not running

Error 2:

Workflow Service Front End Stopped.

Error 3:

Workflow ServiceFrontEnd service is failing to start, HTTP 9003, 9335, 32845, 32846, 808 port opened

Error 4:

Workflow ServiceFrontEnd service and Workflow ServiceBackEnd service Stopped

Error 5:

The Underlying connection was closed.

 

1.       Verified that Workflow Front end service Stopped.

2.       Verified all backend services is running.

3.       All service bus services are up and running.

 

Solution 1:

1.       Verify .NET Framework version installed workflow manager farm in Registry editor.

Open Registry editor -->

 Click on start -->

Open Run--> Type "Regedit" Click on enter--> Go to the below path you can find the .NET framework installed version.

 

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319\SKDUs]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\Setup\NDP\v4.0\Client]

You can able find the latest version of the .NET framework Installed in a server or machine.

2.       Verify If the current version is an older version of .NET 4.7.2 and update the .NET version.

.NET 4.7.2 Version:  https://dotnet.microsoft.com/en-us/download/dotnet-framework/net472

3.       Verify Workflow Front end service stated/ Stopped.

4.       IF stopped proceed to the Next steps.

5.       Go to SharePoint central administrator --> Application management --> Service Applications--> Select workflow Management Proxy service --> Delete.

6.       Register the using below command

Register WFM to SharePoint farm Administrative SharePoint Management Shell, run the below command

Example:

Register-SPWorkflowService -SPSite "http://Webapplicationurl.com" -WorkflowHostUrl "http://WFM.SharePoint.com:12290/SharePoint " -AllowOAuthhttp -force

Or

Register-SPWorkflowService -SPSite "http://Webapplicationurl.com" -WorkflowHostUrl "http://WFM.SharePoint.com:12290/SharePoint " -scopename" " -AllowOAuthhttp -force

 

7.       Run Get-WFFarmStatus on Workflow Management PowerShell.

8.       Verify Workflow Front end service stated/ Stopped.

9.       IF stopped proceed to the Next steps.

10.   Go to Workflow Manager Server.

11.   Click on Run and type Regedit.

12.   Go to the below path and update the key value.

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa]

Add DWARD Value "DisableLoopbackCheck" with a value "1"

And Reboot the server.

13.   Run Get-WFFarmStatus on Workflow Management PowerShell.

14.   Verify Workflow Front end service stated/ Stopped.

15.   IF stopped proceed to the Next steps.

16.   Go to Workflow Manager Server.

17.   Enable TLS 1.0 and TLS 1.1 in the registry under the path

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Client]

"DisabledByDefault"=dword:00000000

"Enabled"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Server]

"DisabledByDefault"=dword:00000000

"Enabled"=dword:00000001

 

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Client]

"DisabledByDefault"=dword:00000000

"Enabled"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Server]

"DisabledByDefault"=dword:00000000

"Enabled"=dword:00000001

18.   And Reboot the server.

19.   Verify Workflow Front end service stated/ Stopped.

20.   IF stopped proceed to the Next steps.

21.   Go to Workflow Manager Server.

 

Error: Workflow ServiceFrontEnd service and Workflow ServiceBackEnd service Stopped

Solution 2:

 

1.       This issue occurs because of the Workflow Resource Management Store version value at [WFResourceManagementDB].[dbo].[StoreVersionTable] is still 1.0.2.0 despite you have installed CU3 which should work with Workflow Resource Management Store version 1.3.0.0.

2.       To resolve this issue you will need to make the two versions identical at [WFResourceManagementDB].[dbo].[StoreVersionTable] and wfServerUpgradePolicy.config to be 1.3.0.0 as the following :

1. Go to C:\Program Files\Workflow Manager\1.0\Workflow

2. Open wfServerUpgradePolicy.config and make sure that <wfupgrade targetVersion="1.3.0.0">

3. Copy below two files from the Workflow Manager server  C:\Program Files\Workflow Manager\1.0\Workflow

WorkflowServiceInstanceManagementDBUpgradeScript.sql

WorkflowServiceResourceManagementDBUpgradeScript.sql

4.       Paste in to SQL server desktop or C drive.

5.       IF SQL and workflow manager are configured on same server then no need to copy to any where

6. Double-click on these files, and It will open in SSMS (SQL server management studio).

7.       Run the following two script

WorkflowServiceInstanceManagementDBUpgradeScript.sql

WorkflowServiceResourceManagementDBUpgradeScript.sql

 


8.       Now the Workflow Resource Management Store version value at [WFResourceManagementDB].[dbo].[StoreVersionTable] should be 1.3.0.0, the workflow manager backend should be started.

9.       Start workflow manager and service bus using the below commands.

10.   To start the workflow manager services execution run the below command in workflow manager PowerShell with Run as administrator

Start-WFHost

11.   To start the Service Bus execution run the below command in workflow manager PowerShell with Run as administrator

 Start-SBFarm 

Reference Articles:

https://www.spjeff.com/2018/01/18/fixed-workflow-manager-backend-error-1067-http-500/

https://sharepoint.stackexchange.com/questions/196303/workflow-manager-backend-stop-after-insalling-cu3-update

https://docs.microsoft.com/en-us/archive/blogs/biztalknotes/workflow-manager-backend-service-failure-after-upgrade-to-1-0-refresh

 


Post a Comment

0 Comments