Microsoft Service Fabric host service (FabricHostSvc) freezes

I have been working with Microsoft Service Fabric since November 2015 and have encountered many problems, but now Service Fabric is not working fully on my development machine. Removing / reinstalling does not help.

I used 1.5 preview and since then I tried 2.0 to no avail.

The problem started when I tried to start the Service Fabric application from Visual Studio 2015 Update 1 (as I have done hundreds of times over the past few months).

My car is blue (the first time I saw the blue screen of Windows 10). After rebooting, I was unable to get the Application Fabric application to deploy through Visual Studio. The PowerShell script failed to execute the following message:

Starting the FabricHostSvc service. This may take several minutes ... Start-Service: The service 'Microsoft Service Fabric Host Host Service (FabricHostSvc)' failed to start.

I went into SCM and found that the "Microsoft Service Fabric Host Service" is in a start state. This went on for an hour. I tried to stop and start the service several times and every time it hangs.

I uninstalled Service Fabric (Service Fabric, SDK and Tools for VS) and reinstalled with the latest version 2.0 and found the same problem.

Reboot, same problem.

Deleted folder c: \ SfDevCluster, same problem.

Based on some other articles, I looked for any random performance counters after deletion, but none were there.

I tried to look at the registry, but there are other Azure components with "Fabric" in the name. If I remove them, I will probably pull out the rest of my Azure dev installation.

Now ... when I tried to start the service again, he again created the SfDevCluster folder and gave me some logs. It seems to be creating two trace log files per minute, and they have EXACTLY the same contents.

Each time it fails, the final line of the trace is:

Info, 11176, General.FabricSetup.Main, operation completed with error 0xffffffff

Early tracing (SF 1.5) showed that a constant is used for the error, not a hexadecimal value. It seems to indicate an invalid argument.

Whatever the failure, this is apparently the cause of my misfortune. Unfortunately, the error is completely useless.

I try to avoid reinstalling Windows because it will kill all day of performance.

Any help is greatly appreciated.

+8
source share
4 answers

Using an elevated session, run: Unregister-ScheduledTask FabricCounters.

This will fix the problem.

+3
source

I observed very similar behavior, reinstalling the factory SDK and runtime, deleting scheduled tasks, deleting the contents of SfDevCluster, etc. Everything did not work.

I saw Docker repeating errors in the event log, and when I tried to remove Docker for Windows SF, I woke up instantly. I have no idea what the interaction is between them, but it's worth checking to see if you are both installed.

+1
source

It seems that some parameters related to the cluster went into an inconsistent state on your computer. This will require examining the traces of the Fabric service and determining the actual cause. I am an engineer on the Service Fabric team. I can help you if you can send me Fabric service traces (from the logs folder) to harahma [at] microsoft [dot] com.

If you are familiar with Azure registration support tickets, I would suggest you do this so that we can track this issue until resolved. In the meantime, I will continue to work on this to see how we can unlock you.

0
source

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

You will get a similar error if the Windows Firewall service is not working when Service Fabric is trying to start.

Check and verify that the Windows Firewall service is configured to be automatic and working.

0
source

All Articles