Microsoft Service Fabric Host Service (FabricHostSvc) Hangs on Start

Question

I\'ve been working with Microsoft Service Fabric since November 2015 and have encountered many issues but now Service Fabric has become completely non-functional on my devel

Answer 1

From an elevated powershell session please run: Unregister-ScheduledTask FabricCounters.

This will fix the issue.

Answer 2

I was seeing very similar behaviour and reinstalls of the fabric SDK and runtime, deleting scheduled tasks, deleting the SfDevCluster contents etc. all didn't work.

I was seeing repeated Docker errors in the event log and when I tried uninstalling Docker for Windows SF instantly woke up. I have no idea what the interaction is between the two but worth checking if you have both installed.

Answer 3

For the benefit of searchers, this is the Powershell script I use to fix my local cluster. It was adapted from this issue fix on github.

#
# WARNING: YOU MUST STOP 'SERVICE FABRIC HOST SERVICE' IN SERVICES FIRST
#          IF THE APPLICATION IS STUCK IN 'STARTING', RESTART YOUR MACHINE
# 
# This script will completely reset the local cluster
# 

Remove-Item 'C:\SfDevCluster' -Recurse -Force -ErrorAction Stop 

New-Item -ItemType directory -Path 'C:\SfDevCluster'

Set-Location 'C:\Program Files\Microsoft SDKs\Service Fabric\ClusterSetup'

./DevClusterSetup.ps1 -PathToClusterDataRoot 'C:\SfDevCluster\Data' -PathToClusterLogRoot 'C:\SfDevCluster\Log'

Answer 4

I know this is an old and question, but maybe my pain can help someone else out.

You'll get a similar error if the Windows Firewall service is not running when Service Fabric attempts to start.

Check and make sure that the Windows Firewall service is set for Automatic and is running.

Answer 5

It seems like some cluster related settings have gone into an inconsistent state on your machine. This will require looking at Service Fabric traces and figure out the actual cause. I am an engineer on the Service Fabric team. I can help you out if you can email me the Service Fabric traces (from logs folder) at harahma[at]microsoft[dot]com.

If you are familiar with logging support tickets on Azure, I would suggest you do that too so we can track this issue to resolution. In the meantime I will continue to work on this to see how we can unblock you.