Install a local cluster. \ DevClusterSetup.ps1 does not work. Pending Naming Service Availability

Question

When I try to configure a local powershell script cluster, I get the following error:

Is there any way to continue the installation or to establish the cause of this error?

Greetings

Mike

---

I completely uninstalled the SDK and got started, but I still have the same problems. It all comes down to "Connect-ServiceFabricCluster", it just doesn’t work at all (I followed all the suggestions I provided).

Surely naming service warnings should point to something?

In every attempt, I see the following:

A WARNING. Failed to contact naming service. Attempting to contact the Failover Manager service ... 2> WARNING: Failed to connect to the Failover Manager service, trying to contact FMM ... 2> Connect-ServiceFabricCluster: a communication error caused the operation to fail. 2> In D: \ Source \ Play \ ServiceFabricApplication \ ServiceFabricApplication \ Scripts \ Deploy-FabricApplication.ps1: 158 char: 16 2> + ... [void] (Connect-ServiceFabricCluster @ClusterConnectionParameters ... 2> + ~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2> + CategoryInfo: InvalidOperation: (:) [Connect-ServiceFabricCluster], FabricTransientException 2> + FullyQualifiedErrorId: CreateClusterConnectionErrorId, Microsoft.ServiceFabric.Powershell.ConnectCluster

Attempt to reset from tray: Tray exit

Answer 1

In my case, Cluster did not execute (i.e. there are no Fabric.exe processes in the task manager).

I was able to get my Powershell discovery working as administrator again and it works:

 & "$ENV:ProgramFiles\Microsoft SDKs\Service Fabric\ClusterSetup\DevClusterSetup.ps1" 

After that, close the powershell window and open a new one (like Admin). Then worked Connect-ServiceFabricCluster .

Answer 2

This usually indicates that the main host of the service is not running. If this is the just released public SDK preview, you can usually resolve these situations by resetting the cluster (just right-click on the icon in the taskbar and press reset). If this is an old rev, well then you should upgrade first :) But besides that you can check inside services.msc and make sure FabricHostSvc is running.

Answer 3

Error is a temporary communication error. Open the task manager, go to the "Details" tab and check if "FabricHost.exe" and "Fabric.exe" are running. This indicates whether the cluster has been installed and started.

Open a new PowerShell admin window and try connecting to the cluster using Connect-ServiceFabricCluster .

If the connection still fails, try deleting the cluster using "CleanCluster.ps1" and configure it again using "DevClusterSetup.ps1". This should solve the problem.

Please visit Eliminate Local Development Cluster Configuration .

Answer 4

I recently had a similar situation where all TCP connections failed with a FabricTransientException exception.

The main reason turned out to be Windows Firewall. As soon as I turned off the firewall for the domain network, the connections were successful and the services were available again.

PS> In case someone is faced with the same problem: initially the problem was that after installation the Fabric host service simply got into a dead end with the status of "Startup". The main reason for this problem was that the Windows Firewall service was disabled on the server. After enabling and starting the Windows service, the Fabric host service started as expected.