Release of Service Fabric SDK 2.1.163 and Runtime 5.1.163


Today, we released a small refresh to our 2.1 SDK and 5.1 runtime. This update fixes a series of bugs in those releases, which are described in the detailed release notes. If you already have the 2.1.150 SDK, you can install the update from here. If you are new to Service Fabric or upgrading from an earlier release, you should perform a full upgrade to get the latest Service Fabric tools, either for Visual Studio 2015 or Visual Studio "15" Preview.

The updated runtime (5.1.163) has been rolled out to all Azure clusters worldwide. If your cluster was not upgraded, it likely means that your cluster or one of your deployed applications is unhealthy or that it became unhealthy during the upgrade and was automatically rolled back. You can read more about the cluster upgrade process here.

Going forward, we intend to release new minor versions of the runtime, SDK, and tools every 2-3 months. These releases will include new platform and tooling features, potentially including additions to the API surface. Between these larger releases, you should watch out for smaller refreshes like this one that fix bugs reported and discovered after we've shipped.

Cheers,

The Service Fabric Team

Comments (13)

  1. DickP says:

    I can’t get this to work at all. I’m trying to install a local cluster on my home Windows 10 pc. I was previous running 2.0.135 / 5.0.135, although getting that up and running was a trial. I am using VS 2015 Update 3. I tried to upgrade to 2.1.150 / 5.1.150 with VS tools. Installation succeeded but deployment of a dummy SF app to initialize the cluster failed. I then tried to install 2.1.163 / 5.1.163 runtime and SDK only with same result.

    Default cluster is successfully set up. SetClusterReady succeeds. Cluster Manager is running but cannot connect to the cluster. FabricHostSvc is running but Fabric.exe crashes.
    Deploy fails:
    2>WARNING: Failed to contact Naming Service. Attempting to contact Failover Manager Service…
    2>WARNING: Failed to contact Failover Manager Service, Attempting to contact FMM…
    2>Connect-ServiceFabricCluster : A communication error caused the operation to fail.
    2>At C:\Users\richard\documents\visual studio
    2>2015\Projects\Application5\Application5\Scripts\Deploy-FabricApplication.ps1:178 char:16
    2>+ … [void](Connect-ServiceFabricCluster @ClusterConnectionParameters …
    2>+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    2> + CategoryInfo : InvalidOperation: (:) [Connect-ServiceFabricCluster], FabricTransientException
    2> + FullyQualifiedErrorId : TestClusterConnectionErrorId,Microsoft.ServiceFabric.Powershell.ConnectCluster
    2>
    2>WARNING: Unable to Verify connection to Service Fabric cluster.
    2>Test-ServiceFabricClusterConnection : Cluster connection instance is null
    2>At C:\Program Files\Microsoft SDKs\Service
    2>Fabric\Tools\PSModule\ServiceFabricSDK\Publish-NewServiceFabricApplication.ps1:129 char:16
    2>+ [void](Test-ServiceFabricClusterConnection)
    2>+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    2> + CategoryInfo : ResourceUnavailable: (:) [Test-ServiceFabricClusterConnection], NullReferenceException
    2> + FullyQualifiedErrorId : GetClusterConnectionErrorId,Microsoft.ServiceFabric.Powershell.TestClusterConnection
    2>
    2>Finished executing script ‘Deploy-FabricApplication.ps1’.

    Please help

  2. Nick Randell says:

    Since this update has come out, all the issues I’ve seen with services stuck and needing to be manually killed have gone away! I take it this is due to the bug fix where replicas would get stuck in different states. Nice work. It’s making my life easier now.

  3. Still not fixed.
    FabricTypeHost.exe crashed always on Windows 7. But runs on Windows 10.
    The problem is ese.dll. It looks for AddVectoredExceptionHandler function in api-ms-win-core-debug-l1-1-0.dll. But does not find it, because it does not exists there. Then it unloads the library with FreeLibrary() and crashes there.
    Is there any place where I could create an issue?

  4. Arun says:

    Do you have any example of how to convert/host a wcf service in Service Fabric?

  5. Chad says:

    Link to download is a WPI download link and the version is not pulling up for me. This is a common issue I have been having with WPI, not having the version available that I’m needing. You should provide an install option outside of WPI.

    1. We are now including direct links to the runtime, SDK, and tools downloads in the release notes.

      1. amitesh rathore says:

        Can you share direct download link here ?

  6. CostasZ says:

    Trying to update our on-premises test cluster with this. It is failing and I am not sure why…I uninstalled the original cluster. Trying to install this just throws an exception.

    Using .\CreateServiceFabricCluster.ps1

    Create Cluster failed. For more information please look at traces in FabricLogRoot.
    Create Cluster failed with exception: System.AggregateException: One or more errors occurred. —> System.Fabric.WRPComm
    on.WrpException
    at System.Fabric.WRPServiceCommon.Common.DeployAnywhereSettingsValidator.ValidatNodeTypes()
    at System.Fabric.WRPServiceCommon.Common.DeployAnywhereSettingsValidator.Validate()
    at System.Fabric.JsonImpl.ManifestConverter.ConstructClusterManifestBuilder(String jsonClusterConfigPath)
    at System.Fabric.JsonImpl.ManifestConverter.ConvertFromJsonToXml(String jsonClusterConfigPath)
    at System.Fabric.DeploymentManager.d__a.MoveNext()
    — End of stack trace from previous location where exception was thrown —
    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at System.Fabric.DeploymentManager.d__0.MoveNext()
    — End of inner exception stack trace —
    at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
    at Microsoft.ServiceFabric.Powershell.ClusterCmdletBase.NewCluster(String clusterConfigurationFilePath, String fabric
    PackageSourcePath, Boolean rollbackOnFailure)
    —> (Inner Exception #0) System.Fabric.WRPCommon.WrpException
    at System.Fabric.WRPServiceCommon.Common.DeployAnywhereSettingsValidator.ValidatNodeTypes()
    at System.Fabric.WRPServiceCommon.Common.DeployAnywhereSettingsValidator.Validate()
    at System.Fabric.JsonImpl.ManifestConverter.ConstructClusterManifestBuilder(String jsonClusterConfigPath)
    at System.Fabric.JsonImpl.ManifestConverter.ConvertFromJsonToXml(String jsonClusterConfigPath)
    at System.Fabric.DeploymentManager.d__a.MoveNext()
    — End of stack trace from previous location where exception was thrown —
    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at System.Fabric.DeploymentManager.d__0.MoveNext()<—

    In DeploymentTraces, the file says:

    2016/08/17-15:25:21.406,Verbose,7916,SystemFabricDeployer.SFDeployer,Creating Service Fabric Cluster…
    2016/08/17-15:25:21.594,Info,7916,SystemFabricDeployer.SFDeployer,Verifying remote procedure call access against cluster machines.
    2016/08/17-15:25:21.891,Info,7916,SystemFabricDeployer.SFDeployer,Processing and validating cluster config.
    2016/08/17-15:25:22.313,Info,7916,WRP.FabricSettingsMetadata,Creating FabricSettingsMetadata from C:\Temp\sfinstallnew\ServiceFabricPackage\bin\Fabric\Fabric.Code\Configurations.csv

    1. Can you post this to our GitHub issues page? We will follow up there.

  7. athurner says:

    I have a on-premise cluster successfully running (1.5.156) and I wanted to upgrade to 1.5.163. I cannot find a document that describes how to upgrade all nodes on the cluster.

    How would I do that? Thank you

    1. athurner says:

      OK, I think I understand and still there is one question:

      I opened powershell as administrator:

      PS C:|>Connect-ServiceFabricCluster :19000
      PS C:|>copy-ServiceFabricClusterPackage -Code -CodePackagePath .\MicrosoftServiceFabric.5.1.163.9590.msi -ImageStoreConnectionString “fabric:ImageStore”
      PS C:|>Register-ServiceFabricClusterPackage -Code -CodePackagePath “MicrosoftServiceFabric.5.1.163.9590.msi”
      PS C:|>Start-ServiceFabricClusterUpgrade -Code -CodePackageVersion “5.1.163.9590” -UnmonitoredAuto

      But this gives me the following error
      Start-ServiceFabricClusterUpgrade : The first Fabric upgrade must specify both the code and config versions. Requested value: 5.1.163.9590:
      At line:1 char:1
      + Start-ServiceFabricClusterUpgrade -Code -CodePackageVersion “5.1.163.9590” -Unmo …
      + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      + CategoryInfo : InvalidOperation: (Microsoft.Servi…usterConnection:ClusterConnection) [Start-ServiceFabricClusterUpgrade], FabricException
      + FullyQualifiedErrorId : UpgradeClusterErrorId,Microsoft.ServiceFabric.Powershell.StartClusterUpgrade

      My second and now successful way is to update also the cluster configuration file

      PS C:|>Connect-ServiceFabricCluster :19000
      PS C:|>Copy-ServiceFabricClusterPackage -ClusterManifestPath .\ClusterManifest.1.0.1.0.xml -CodePackagePath .\MicrosoftServiceFabric.5.1.163.9590.msi -ImageStoreConnectionString “fabric:ImageStore”
      PS C:|>Register-ServiceFabricClusterPackage -ClusterManifestPath “ClusterManifest.1.0.1.0.xml” -CodePackagePath “MicrosoftServiceFabric.5.1.163.9590.msi”
      PS C:|>Start-ServiceFabricClusterUpgrade -CodePackageVersion “5.1.163.9590” -ClusterManifestVersion “1.0.1.0” -UnmonitoredAuto

      this seams to work well (currently my cluster has one upgrade domain pending)

      So my question remains: How will I do the upgrade if I don’t want to upgrade the cluster manifest as well?
      – Do I misunderstand something or is there a bug?

  8. We have been running the 5.1.150.9590 version of the runtime that was distributed with the standalone. Is this release compatible with that? If not, how do we update the runtime of the standalone?

  9. Leo says:

    Is there a stand alone installer (for Visual Studio 2015)?

Skip to main content