Start-Service: Failed to start the service "Microsoft Service Fabric Host Service (FabricHostSvc)"

Question

I want to get started with Azure Service Fabric technology.

I work in accordance with this document and install the latest version of the SDK. After installation, I opened the PowerShell command prompt windows ("Run as administrator") and wrote these lines:

# Set-ExecutionPolicy -ExecutionPolicy Unrestricted -Force -Scope CurrentUser # cd "$env:ProgramW6432\Microsoft SDKs\Service Fabric\ClusterSetup" # .\DevClusterSetup.ps1 

As an answer, this error was received:

 Cleaning existing cluster ... NOTE: If this powershell command window exits, please re-run the script in a new powershell command window. Stopping service FabricHostSvc. This may take a few minutes... Removing cluster configuration Remove node configuration succeeded Cleaning existing certificates Stopping all logman sessions Cleaning log and data folder, the powershell window may close automatically. ClusterPath not provided, will use C:\SfDevCluster FabricDataRoot not provided, will use C:\SfDevCluster\Data FabricLogRoot not provided, will use C:\SfDevCluster\Log Directory: C:\ Mode LastWriteTime Length Name ---- ------------- ------ ---- d---- 4/11/2015 12:47 PM SfDevCluster Directory: C:\SfDevCluster Mode LastWriteTime Length Name ---- ------------- ------ ---- d---- 4/11/2015 12:47 PM Manifests True Create node configuration succeeded Starting service FabricHostSvc. This may take a few minutes... Start-Service : Failed to start service 'Microsoft Service Fabric Host Service (FabricHostSvc)'. At C:\Program Files\Microsoft SDKs\Service Fabric\ClusterSetup\DevClusterSetup.ps1:167 char:1 + Start-Service FabricHostSvc -WarningAction SilentlyContinue + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : OpenError: (System.ServiceProcess.ServiceController:ServiceController) [Start-Service], ServiceCommandException + FullyQualifiedErrorId : StartServiceFailed,Microsoft.PowerShell.Commands.StartServiceCommand WARNING: Could not start FabricHostSvc 

The bottom line is " Failed to start the service ." This output is printed on the screen after 3 minutes of waiting.

Things I've already tried:

• Restart your computer several times (I read somewhere that this solves the problem).
• Disable my antivirus software.

Attached screenshot of the PowerShell command line. I use:

• Visual Studio 2015 Enterprise Edition
• Windows 8.1
• Azure Service Fabric SDK v1.0.328

Answer 1

I also struggled with this problem only this morning. I did not have to reinstall Windows.

I also found events in the event log talking about corrupted performance counters. I'm not sure if this is related or not, but I ran this command from cmd windows as an administrator to rebuild performance counters and fix the error:

lodctr / r

Then I went to “Programs and Features” and deleted everything that was mentioned in the Service Fabric.

Then I reinstalled the Service Fabric SDK and followed the instructions on the setup page of the Azure Service environment , and my cluster started working normally.

Answer 2

I ran into the same problem and tried one evening many times, and the next morning I got an answer. Well, the answer is "Make sure the firewall is turned on."

Answer 3

UPDATE2: This is a very old problem, and I have not seen this repeat since November 2015. (added so that this post no longer disappears - voted: - /).

UPDATE: I have not had this problem since the update in November.

ORIGINAL: I had this problem the other day and everything was tried. I uninstalled, rebooted, reinstalled everything from Service Fabric to the Azure SDK and Visual Studio.

The fix is ​​pretty bad. Reinstall the windows.

At some point, I found a trace that indicated a registry corruption. Something about the inability to find a performance counter.

Now I have a new problem (which I will publish separately), but I just repeat here so that people know that this service now has some infrastructure with errors ... My application for checking status / without state. A stateless application is deployed and launched. A stateful service is deployed but not replicated. If I run the exact same code on another machine (and I mean copying / pasting to another machine and then starting it), it all works.