Release of Service Fabric for Windows Server package version 5.6.220

We have released the Service Fabric for Windows Server (Standalone) package version 5.6, which is a rollup of all the changes from the Runtime 5.6.204 & SDK 2.6.204 release and Runtime 5.6.210 & SDK 2.6.210 refresh, and includes Standalone specific updates. This version also includes additional bug fixes which will be rolled out to Azure soon. Look out for an announcement in the coming weeks that contains more details on bug fixes in that release.

Here are the download links for the Standalone package, and the (runtime) cab file.

A few highlights that are specific to Standalone in this release:

Add/Remove Nodes in a Standalone cluster

We are adding functionality for adding and removing nodes in production clusters. The package contains the "AddNode.ps1" script to add nodes of a specific NodeType to your cluster, making the requisite changes to your cluster configuration automatically. To remove nodes, the node description has to be removed from the cluster configuration, and the list of nodes being removed should be added to "FabricSettings" in the following manner:

    "name": "NodesToBeRemoved",
    "value": "<node name(s)>"

Reliability Level

For standalone clusters, the reliability level can now be upgraded via a configuration upgrade. Modify the "ReliabilityLevel" parameter in your cluster configuration and initiate an upgrade using "Start-ServiceFabricClusterConfigurationUpgrade -ClusterConfigPath <Path to modified JSON>." The current supported reliability levels are Bronze, Silver, Gold, and Platinum.

Enabled Add-on Features: Repair Manager and DNS Service

This release includes the ability to add the Repair Manager and DNS Service to your cluster, as part of the overall runtime changes. The Repair Manager is required for the Patch Orchestration Services, and the DNS Service is required for enabling Container related features.


Be sure to read through the full release notes for a complete list of new features and bug fixes.



The Service Fabric Team

Comments (15)

  1. Matt Corr says:

    Should we assume that future releases will have the same version numbers for the SDK, Azure SF runtime and the on prem Runtime/Cab file?
    At the moment it seems a bit staggered?

    1. Max Burlik says:

      The standalone release has the incremented version since the runtime required some changes since the earlier SDK release. SDK does not require the changes, and is compatible with this release. Generally the following pattern is supported where SDK targets a different version runtime: [SDK version] <= [Runtime version].

    2. Yes, we will try to keep future releases for Azure SF and On-prem runtimes at the same version. As Max mentioned, the SDK version will be <= the runtime version.

  2. Jean-Jacques Lafay says:

    Warning !
    This release introduces a dependency on VC++ redistribuable VS2015, at least for the FabricInstallerService. So if this redistribuable isn’t installed, the FabricInstallerService won’t launch (and won’t be able to rollback either), meaning you have a dead node until fixed.

    1. Matt Snider says:

      We’ve always had a dependency on the C++ Runtime, afaik that’s not new. Good to call it out though as it is a dependency. Most of the time I don’t notice since I’m installing SF on environments where the runtime already exists. How did you install it so that you ran into this?

    2. Max Burlik says:

      As of 5.6 the installer carries the dependent VC++ redistributable dlls for first launch, and now installs both VC++11 and VC++14. Please email if you have any deployment issues.

      1. Jean-Jacques Lafay says:

        I simply tried to upgrade my on-prem cluster (Windows Server 2012 R2 VMs) as usual (, no internet access on the cluster), so there is no installer directly involved. I noticed the first node staying down, and “in progress” as per Get-ServiceFabricClusterUpgradeStatus, and after a bit of investigation found that the reason was the new dependency (it is indeed a new dependency for the VS2015 version). I grabbed the redistribuable, installed it on the nodes of the cluster, and from then everything went sailing. Seemed worth a warning though…

        1. Max Burlik says:

          Please send further details of the steps followed to attempt the upgrade, and the mitigation steps taken to resolve the issue to, since this scenario is expected to work. We had validated this on Server 2012 R2 machines.

          Please include logs from the time of upgrade.

          1. Jean-Jacques Lafay says:

            There’s not much more that I can say, but even if there had been, I wouldn’t be able to say it, since the address doesn’t accept mails…

  3. Hans Ravnaas says:

    I have to agree with Matt below. The versioning is a bit confusing, the *.220 part not lining with up anything else I’m aware of.

    Follow up question – seems that standalone package 5.6.220 packages up SDK 2.6.204 and runtime 5.6.204. When can we expect a standalone package with SDK 2.6.210 and runtime: 5.6.210?


    1. Max Burlik says:

      Please see the reply to Matt’s post regarding compatible versions.

      The standalone 5.6.220 release has all the runtime changes including those from v5.6.204 & v5.6.210. As well the SDK runtime MSI is only used for development scenarios, so the runtime changes up to 5.6.220 should not be necessary here.

      1. Hans Ravnaas says:

        Max, thanks for the speedy reply and for updating the blog post with further clarification!

  4. Sandro Pedrocchi says:

    Unprovisioning an application type does not automatically „delete“ the DNS name. Therefore, it is not possible to publish the same app again. I am always getting the error “##[error]Service DNS name in use by another service.”. Is there any powershell command to flush the DNS server manually?

  5. Nick Randell says:

    Any news when this will be automatically deployed to azure clusters? I can see it is in the manual list at the moment, but as far as I can tell it has not been automatically upgraded.

  6. Phillipp says:

    Would Becoming A Freelancе Paraⅼegal Be A Good Ⲥhoice For You?

Skip to main content