The following forum(s) have migrated to Microsoft Q&A (Preview): Azure Service Fabric!
Visit Microsoft Q&A (Preview) to post new questions.

Learn More

 locked
Service Fabric Standalone install on Windows Servers RRS feed

  • General discussion

  • I had service fabric in a Multi-Machine environment all of a sudden stop working. Now if I run:

    PS F:\Temp\Microsoft.Azure.ServiceFabric.WindowsServer.6.0.232.9494>> .\CreateServiceFabricCluster.ps1 -ClusterConfigFil
    ePath .\ClusterConfig.Unsecure.MultiMachine.MamProd.json -AcceptEULA

    Security warning
    Run only scripts that you trust. While scripts from the internet can be useful, this script can potentially harm your
    computer. If you trust this script, use the Unblock-File cmdlet to allow the script to run without this warning
    message. Do you want to run
    F:\Temp\Microsoft.Azure.ServiceFabric.WindowsServer.6.0.232.9494\CreateServiceFabricCluster.ps1?
    [D] Do not run  [R] Run once  [S] Suspend  [?] Help (default is "D"): r
    Trace folder already exists. Traces will be written to existing trace folder: F:\Temp\Microsoft.Azure.ServiceFabric.Wind
    owsServer.6.0.232.9494\DeploymentTraces
    Creating Service Fabric Cluster...
    If it's taking too long, please check in Task Manager details and see if Fabric.exe for each node is running. If not, p
    lease look at: 1. traces in DeploymentTraces directory and 2. traces in FabricLogRoot configured in ClusterConfig.json.
    Trace folder already exists. Traces will be written to existing trace folder: F:\Temp\Microsoft.Azure.ServiceFabric.Wind
    owsServer.6.0.232.9494\DeploymentTraces
    Running Best Practices Analyzer...
    Best Practices Analyzer completed successfully.
    Creating Service Fabric Cluster...
    Processing and validating cluster config.
    Configuring nodes.
    Default installation directory chosen based on system drive of machine 'xx.200.83.18'.
    Copying installer to all machines.
    Configuring machine 'xx.200.83.18'.
    Configuring machine 'xx.150.83.18'.
    Configuring machine 'xx.200.83.19'.
    Configuring machine 'xx.150.83.19'.
    Machine 10.200.83.18 configured.
    Machine 10.200.83.19 configured.
    Machine 10.150.83.18 configured.
    Machine 10.150.83.19 configured.
    Running Fabric service installation.
    Successfully started FabricInstallerSvc on machine xx.200.83.18
    Successfully started FabricInstallerSvc on machine xx.150.83.18
    Successfully started FabricInstallerSvc on machine xx.150.83.19
    Successfully started FabricInstallerSvc on machine xx.200.83.19

    But once it starts to do FabricHostSvc, it gets on 3 of 4 machines, then

    If I run TestConfiguration, IsCabValid doesn't return any value, but somehow says it's valid. 

    message. Do you want to run F:\Temp\Microsoft.Azure.ServiceFabric.WindowsServer.6.0.232.9494\TestConfiguration.ps1?
    [D] Do not run  [R] Run once  [S] Suspend  [?] Help (default is "D"): r
    Trace folder already exists. Traces will be written to existing trace folder: F:\Temp\Microsoft.Azure.ServiceFabric.Wind
    owsServer.6.0.232.9494\DeploymentTraces
    Running Best Practices Analyzer...
    Best Practices Analyzer completed successfully.


    LocalAdminPrivilege        : True
    IsJsonValid                : True
    IsCabValid                 :
    RequiredPortsOpen          : True
    RemoteRegistryAvailable    : True
    FirewallAvailable          : True
    RpcCheckPassed             : True
    NoConflictingInstallations : True
    FabricInstallable          : True
    DataDrivesAvailable        : True
    Passed                     : True

    If I run

    PS F:\Temp\Microsoft.Azure.ServiceFabric.WindowsServer.6.0.232.9494>> .\RemoveServiceFabricCluster.ps1 -ClusterConfigFil
    ePath .\ClusterConfig.Unsecure.MultiMachine.MamProd.json

    Security warning
    Run only scripts that you trust. While scripts from the internet can be useful, this script can potentially harm your
    computer. If you trust this script, use the Unblock-File cmdlet to allow the script to run without this warning
    message. Do you want to run
    F:\Temp\Microsoft.Azure.ServiceFabric.WindowsServer.6.0.232.9494\RemoveServiceFabricCluster.ps1?
    [D] Do not run  [R] Run once  [S] Suspend  [?] Help (default is "D"): r
    Do you want to remove the cluster? [Y] Yes  [N] No (default is 'N'): y
    Removing Microsoft Azure Service Fabric Cluster...
    Trace folder already exists. Traces will be written to existing trace folder: F:\Temp\Microsoft.Azure.ServiceFabric.Wind
    owsServer.6.0.232.9494\DeploymentTraces
    Running Best Practices Analyzer...
    None of the machines have Fabric installed.
    Run Test-ServiceFabricConfiguration or TestConfiguration.ps1 to validate configuration & environment state. Best Practic
    es Analyzer hit validation error(s).
    FabricRoot not found in registry of target machine xx.200.83.18.
    FabricRoot not found in registry of target machine xx.200.83.19.
    FabricRoot not found in registry of target machine xx.150.83.18.
    FabricRoot not found in registry of target machine xx.150.83.19.
    The cluster is successfully removed.

    Tuesday, December 12, 2017 7:29 PM

All replies