%3CLINGO-SUB%20id%3D%22lingo-sub-1144460%22%20slang%3D%22en-US%22%3ERe%3A%20Azure%20Service%20Fabric%207.0%20Second%20Refresh%20Release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1144460%22%20slang%3D%22en-US%22%3E%3CP%3EIn%20the%20release%20notes%20there%20was%20a%20mention%20of%20this%20new%20ephemeral%20disks%20support%20and%20a%20recommendation%3A%3C%2FP%3E%3CP%3E%22%3CSPAN%3EThey%20are%20recommended%20for%20all%20Service%20Fabric%20node%20types.%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EWould%20the%20stateful%20service%20data%20still%20be%20stored%20on%20temporary%20disk%20when%20using%20this%20feature%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EAt%20the%20moment%20we're%20using%20D2%20v2%20machines%20(non-premium%20disk%20SKU).%20These%20are%20nice%20machines%20for%20stateful%20workloads%20because%20they%20have%20100%20GB%20of%20temporary%20storage%20available.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThe%20premium%20disk%20SKU%20of%20the%20same%20size%26nbsp%3BDS2%20v2%20has%20only%2014%20GB%20of%20temporary%20storage%20available%20and%20maximum%20of%2086%20GB%20of%20cache%20for%20ephemeral%20disk.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThat%20sounds%20like%20a%20terrible%20deal%20compared%20to%20D2%20v2%20where%20there%20is%20plenty%20of%20temporary%20storage%20available%20for%20data.%20Is%20there%20something%20I%20am%20missing%3F%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1147293%22%20slang%3D%22en-US%22%3ERe%3A%20Azure%20Service%20Fabric%207.0%20Second%20Refresh%20Release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1147293%22%20slang%3D%22en-US%22%3E%3CP%3EThere%20seems%20to%20be%20a%20breaking%20change%20-%20atm%20I've%20left%20our%20SF%20cluster%20apps%20on%20version%206.5%20of%20SDK%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%3CBR%20%2F%3EBelow%20line%3A%3CBR%20%2F%3E%3CSTRONG%3Enew%20FabricClient()%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSTRONG%3EThrows%3A%3C%2FSTRONG%3E%3CBR%20%2F%3ESystem.InvalidCastException%3A%20Unable%20to%20cast%20COM%20object%20of%20type%20'System.__ComObject'%20to%20interface%20type%20'IFabricClusterManagementClient11'.%20This%20operation%20failed%20because%20the%20QueryInterface%20call%20on%20the%20COM%20component%20for%20the%20interface%20with%20IID%20'%7B254FD06B-792A-4233-B9A5-94019A36EAE9%7D'%20failed%20due%20to%20the%20following%20error%3A%20No%20such%20interface%20supported%20(0x80004002%20(E_NOINTERFACE)).at%20System.Fabric.FabricClient.CreateNativeClient(IEnumerable%601%20connectionStringsLocal)at%20System.Fabric.FabricClient.%3CINITIALIZEFABRICCLIENT%3Eb__106_0()at%20System.Fabric.Interop.Utility.%26lt%3B%26gt%3Bc__DisplayClass28_0.%3CWRAPNATIVESYNCINVOKE%3Eb__0()at%20System.Fabric.Interop.Utility.WrapNativeSyncInvoke%5BTResult%5D(Func%601%20func%2C%20String%20functionTag%2C%20String%20functionArgs)at%20System.Fabric.Interop.Utility.WrapNativeSyncInvoke(Action%20action%2C%20String%20functionTag%2C%20String%20functionArgs)at%20System.Fabric.Interop.Utility.%26lt%3B%26gt%3Bc__DisplayClass26_0.%3CWRAPNATIVESYNCINVOKEINMTA%3Eb__0()at%20System.Fabric.Interop.Utility.RunInMTA(Action%20action)at%20System.Fabric.Interop.Utility.WrapNativeSyncInvokeInMTA(Action%20action%2C%20String%20functionTag)at%20System.Fabric.FabricClient.InitializeFabricClient(SecurityCredentials%20credentialArg%2C%20FabricClientSettings%20newSettings%2C%20String%5B%5D%20hostEndpointsArg)at%20System.Fabric.FabricClient..ctor()at%20ANGen.Core.ServiceFabric.Deployment.DeployerContext..ctor(FabricClient%20fabricClient)at%20ANGen.Core.ServiceFabric.Deployment.BootstrapperService.RunAsync(CancellationToken%20cancellationToken)at%20Microsoft.ServiceFabric.Services.Runtime.StatelessServiceInstanceAdapter.ExecuteRunAsync(CancellationToken%20runAsyncCancellationToken)%3C%2FWRAPNATIVESYNCINVOKEINMTA%3E%3C%2FWRAPNATIVESYNCINVOKE%3E%3C%2FINITIALIZEFABRICCLIENT%3E%3C%2FP%3E%3CP%3ESystem.InvalidCastException%3A%20Unable%20to%20cast%20COM%20object%20of%20type%20'System.__ComObject'%20to%20interface%20type%20'IFabricClusterManagementClient11'.%20This%20operation%20failed%20because%20the%20QueryInterface%20call%20on%20the%20COM%20component%20for%20the%20interface%20with%20IID%20'%7B254FD06B-792A-4233-B9A5-94019A36EAE9%7D'%20failed%20due%20to%20the%20following%20error%3A%20No%20such%20interface%20supported%20(0x80004002%20(E_NOINTERFACE)).%3CBR%20%2F%3Eat%20System.Fabric.FabricClient.CreateNativeClient(IEnumerable%601%20connectionStringsLocal)%3CBR%20%2F%3Eat%20System.Fabric.FabricClient.%3CINITIALIZEFABRICCLIENT%3Eb__106_0()%3CBR%20%2F%3Eat%20System.Fabric.Interop.Utility.%26lt%3B%26gt%3Bc__DisplayClass28_0.%3CWRAPNATIVESYNCINVOKE%3Eb__0()%3CBR%20%2F%3Eat%20System.Fabric.Interop.Utility.WrapNativeSyncInvoke%5BTResult%5D(Func%601%20func%2C%20String%20functionTag%2C%20String%20functionArgs)%3CBR%20%2F%3Eat%20System.Fabric.Interop.Utility.WrapNativeSyncInvoke(Action%20action%2C%20String%20functionTag%2C%20String%20functionArgs)%3CBR%20%2F%3Eat%20System.Fabric.Interop.Utility.%26lt%3B%26gt%3Bc__DisplayClass26_0.%3CWRAPNATIVESYNCINVOKEINMTA%3Eb__0()%3CBR%20%2F%3Eat%20System.Fabric.Interop.Utility.RunInMTA(Action%20action)%3CBR%20%2F%3Eat%20System.Fabric.Interop.Utility.WrapNativeSyncInvokeInMTA(Action%20action%2C%20String%20functionTag)%3CBR%20%2F%3Eat%20System.Fabric.FabricClient.InitializeFabricClient(SecurityCredentials%20credentialArg%2C%20FabricClientSettings%20newSettings%2C%20String%5B%5D%20hostEndpointsArg)%3CBR%20%2F%3Eat%20System.Fabric.FabricClient..ctor()%3CBR%20%2F%3Eat%20ANGen.Core.ServiceFabric.Deployment.DeployerContext..ctor(FabricClient%20fabricClient)%3CBR%20%2F%3Eat%20ANGen.Core.ServiceFabric.Deployment.BootstrapperService.RunAsync(CancellationToken%20cancellationToken)%3CBR%20%2F%3Eat%20Microsoft.ServiceFabric.Services.Runtime.StatelessServiceInstanceAdapter.ExecuteRunAsync(CancellationToken%20runAsyncCancellationToken)%3C%2FWRAPNATIVESYNCINVOKEINMTA%3E%3C%2FWRAPNATIVESYNCINVOKE%3E%3C%2FINITIALIZEFABRICCLIENT%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1150978%22%20slang%3D%22en-US%22%3ERe%3A%20Azure%20Service%20Fabric%207.0%20Second%20Refresh%20Release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1150978%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F424127%22%20target%3D%22_blank%22%3E%40debeerisgreat%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThis%20issue%20is%20not%20related%20to%20this%20release%20version.%20It%20is%20due%20to%20a%20mismatch%20between%20the%20native%20and%20managed%20binaries.%20This%20is%20most%20likely%20happening%20because%20your%20carrying%20the%20native%20runtime%20binaries%20with%20the%20application.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1151700%22%20slang%3D%22en-US%22%3ERe%3A%20Azure%20Service%20Fabric%207.0%20Second%20Refresh%20Release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1151700%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F387597%22%20target%3D%22_blank%22%3E%40servicefabric%3C%2FA%3E%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EMy%20mistake%20as%20I%20misunderstood%20the%20way%20to%20upgrade%20app%20SDK%20versions%20vs%20cluster%20runtime%20version%2C%20as%20per%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fservice-fabric%2Fservice-fabric-versions%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fservice-fabric%2Fservice-fabric-versions%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1137690%22%20slang%3D%22en-US%22%3EAzure%20Service%20Fabric%207.0%20Second%20Refresh%20Release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1137690%22%20slang%3D%22en-US%22%3E%3CP%3E%3CFONT%20size%3D%223%22%3E%3CSTRONG%3EUPDATE%202%2F6%3A%26nbsp%3B%3C%2FSTRONG%3EWe%20resolved%20regression%20found%20with%26nbsp%3B%20this%207.0%20refresh%20release%20version%20in%20the%20most%20current%20refresh%20release%20of%207.0.%20%3CA%20title%3D%227.0%20Third%20refresh%20release%22%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fazure-service-fabric%2Fazure-service-fabric-7-0-third-refresh-release%2Fba-p%2F1156508%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3EBlogpost%3C%2FA%3E%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%223%22%3E%3CSTRONG%3EUPDATE%202%2F3%3A%26nbsp%3B%20%3C%2FSTRONG%3EWe%20encountered%20issue%20with%20this%20release%20and%20have%20stopped%20the%20roll-out.%20We%20are%20working%20on%20resolving%20it%20and%20will%20publish%20new%20version%20by%20end%20of%20this%20week.%20Will%20provide%20an%20update%20soon.%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%223%22%3EAzure%20Service%20Fabric%207.0%20Second%20refresh%20release%20which%20includes%20bug%20fixes%2C%20and%20performance%20enhancements%20has%20started%20rolling%20out%20to%20the%20various%20Azure%20regions.%20The%20updates%20for%20.NET%20SDK%2C%20Java%20SDK%20and%20Service%20Fabric%20Runtime%20is%20available%20through%20Web%20Platform%20Installer%2C%20NuGet%20packages%20and%20Maven%20repositories%20in%207-10%20days%20within%20all%20regions.%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CFONT%20size%3D%223%22%3EService%20Fabric%20Runtime%3C%2FFONT%3E%3C%2FLI%3E%0A%3CUL%3E%0A%3CLI%3E%3CFONT%20size%3D%223%22%3EWindows%20%E2%80%93%26nbsp%3B%3CI%3E%26nbsp%3B%3CSPAN%3E7.0.464.9590%3C%2FSPAN%3E%3C%2FI%3E%26nbsp%3B%3C%2FFONT%3E%3C%2FLI%3E%0A%3CLI%3E%3CFONT%20size%3D%223%22%3EUbuntu%20-%26nbsp%3B%3CI%3E%26nbsp%3B%26nbsp%3B%3CSPAN%3E7.0.464.1%3C%2FSPAN%3E%3C%2FI%3E%3C%2FFONT%3E%3C%2FLI%3E%0A%3CLI%3E%3CFONT%20size%3D%223%22%3EService%20Fabric%20for%20Windows%20Server%20Service%20Fabric%20Standalone%20Installer%20Package%20-%26nbsp%3B%3CI%3E%3CSPAN%3E7.0.464.9590%3C%2FSPAN%3E%3C%2FI%3E%3CI%3E%26nbsp%3B%26nbsp%3B%3C%2FI%3E%3C%2FFONT%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FUL%3E%0A%3CUL%3E%0A%3CLI%3E%3CFONT%20size%3D%223%22%3E.NET%20SDK%3C%2FFONT%3E%3C%2FLI%3E%0A%3CUL%3E%0A%3CLI%3E%3CFONT%20size%3D%223%22%3EWindows%20.NET%20SDK%20-%26nbsp%3B%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CI%3E%20%3CSPAN%3E4.0.464%3C%2FSPAN%3E%3C%2FI%3E%20%3C%2FFONT%3E%3C%2FLI%3E%0A%3CLI%3E%3CFONT%20size%3D%223%22%3EMicrosoft.ServiceFabric%20-%26nbsp%3B%3CI%3E%26nbsp%3B%26nbsp%3B%3CSPAN%3E7.0.464%3C%2FSPAN%3E%3C%2FI%3E%20%3C%2FFONT%3E%3C%2FLI%3E%0A%3CLI%3E%3CFONT%20size%3D%223%22%3EReliable%20Services%20and%20Reliable%20Actors%20-%26nbsp%3B%3CI%3E%20%3CSPAN%3E4.0.464%3C%2FSPAN%3E%3C%2FI%3E%20%3C%2FFONT%3E%3C%2FLI%3E%0A%3CLI%3E%3CFONT%20size%3D%223%22%3EASP.NET%20Core%20Service%20Fabric%20integration%20-%26nbsp%3B%3CI%3E%26nbsp%3B%3CSPAN%3E4.0.464%3C%2FSPAN%3E%3C%2FI%3E%20%3C%2FFONT%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CLI%3E%3CFONT%20size%3D%223%22%3EJava%20SDK%20%E2%80%93%26nbsp%3B%201.0.5%3C%2FFONT%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%225%22%3E%3CSTRONG%3EKey%20Announcements%3C%2FSTRONG%3E%3C%2FFONT%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CFONT%20size%3D%224%22%3E%3CSTRONG%3ECluster%20Upgrade%3C%2FSTRONG%3E%3A%3C%2FFONT%3E%20We%20had%20found%20regression%20issues%20in%207.0%20release.%20Hence%2C%20recommend%20to%20upgrade%20to%20this%20latest%20version%20of%207.0%20release%20for%20clusters%20on%20version%206.5%20and%20above.%3C%2FLI%3E%0A%3CLI%3E%3CFONT%20size%3D%224%22%3E%3CSTRONG%3EPreview%20Feature%3C%2FSTRONG%3E%3A%3C%2FFONT%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fazure%2Fservice-fabric%2Fservice-fabric-application-upgrade-advanced%23avoid-connection-drops-during-planned-downtime-of-stateless-services%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3EAvoid%20connection%20drops%20during%20planned%20downtime%20of%20stateless%20services%3C%2FA%3E.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSPAN%3EFor%20more%20details%2C%20please%20read%20the%3C%2FSPAN%3E%3CSPAN%3E%20%3CA%20title%3D%22SF%2070CU2%20release%20notes%22%20href%3D%22https%3A%2F%2Fgithub.com%2FAzure%2Fservice-fabric%2Fblob%2Fmaster%2Frelease_notes%2FService-Fabric-70CU2-releasenotes.md%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3Erelease%20notes%3C%2FA%3E.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%2C%3C%2FP%3E%0A%3CP%3EService%20Fabric%20Team%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1137690%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EAzure%20Service%20Fabric%207.0%20Second%20refresh%20release%20includes%20bug%20fixes%2C%20preview%20features%20and%20performance%20enhancements.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-TEASER%3E
Senior Member

UPDATE 2/6: We resolved regression found with  this 7.0 refresh release version in the most current refresh release of 7.0. Blogpost

 

UPDATE 2/3:  We encountered issue with this release and have stopped the roll-out. We are working on resolving it and will publish new version by end of this week. Will provide an update soon.

 

Azure Service Fabric 7.0 Second refresh release which includes bug fixes, and performance enhancements has started rolling out to the various Azure regions. The updates for .NET SDK, Java SDK and Service Fabric Runtime is available through Web Platform Installer, NuGet packages and Maven repositories in 7-10 days within all regions.

 

  • Service Fabric Runtime
    • Windows –  7.0.464.9590 
    • Ubuntu -   7.0.464.1
    • Service Fabric for Windows Server Service Fabric Standalone Installer Package - 7.0.464.9590  
  • .NET SDK
    • Windows .NET SDK -   4.0.464
    • Microsoft.ServiceFabric -   7.0.464
    • Reliable Services and Reliable Actors -  4.0.464
    • ASP.NET Core Service Fabric integration -  4.0.464
  • Java SDK –  1.0.5

 

Key Announcements

For more details, please read the release notes.

 

Thanks,

Service Fabric Team

4 Comments
Senior Member

In the release notes there was a mention of this new ephemeral disks support and a recommendation:

"They are recommended for all Service Fabric node types."

 

Would the stateful service data still be stored on temporary disk when using this feature?

 

At the moment we're using D2 v2 machines (non-premium disk SKU). These are nice machines for stateful workloads because they have 100 GB of temporary storage available.

 

The premium disk SKU of the same size DS2 v2 has only 14 GB of temporary storage available and maximum of 86 GB of cache for ephemeral disk.

 

That sounds like a terrible deal compared to D2 v2 where there is plenty of temporary storage available for data. Is there something I am missing?

Established Member

There seems to be a breaking change - atm I've left our SF cluster apps on version 6.5 of SDK
  
Below line:
new FabricClient()

Throws:
System.InvalidCastException: Unable to cast COM object of type 'System.__ComObject' to interface type 'IFabricClusterManagementClient11'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{254FD06B-792A-4233-B9A5-94019A36EAE9}' failed due to the following error: No such interface supported (0x80004002 (E_NOINTERFACE)).
at System.Fabric.FabricClient.CreateNativeClient(IEnumerable`1 connectionStringsLocal)
at System.Fabric.FabricClient.<InitializeFabricClient>b__106_0()
at System.Fabric.Interop.Utility.<>c__DisplayClass28_0.<WrapNativeSyncInvoke>b__0()
at System.Fabric.Interop.Utility.WrapNativeSyncInvoke[TResult](Func`1 func, String functionTag, String functionArgs)
at System.Fabric.Interop.Utility.WrapNativeSyncInvoke(Action action, String functionTag, String functionArgs)
at System.Fabric.Interop.Utility.<>c__DisplayClass26_0.<WrapNativeSyncInvokeInMTA>b__0()
at System.Fabric.Interop.Utility.RunInMTA(Action action)
at System.Fabric.Interop.Utility.WrapNativeSyncInvokeInMTA(Action action, String functionTag)
at System.Fabric.FabricClient.InitializeFabricClient(SecurityCredentials credentialArg, FabricClientSettings newSettings, String[] hostEndpointsArg)
at System.Fabric.FabricClient..ctor()
at ANGen.Core.ServiceFabric.Deployment.DeployerContext..ctor(FabricClient fabricClient)
at ANGen.Core.ServiceFabric.Deployment.BootstrapperService.RunAsync(CancellationToken cancellationToken)
at Microsoft.ServiceFabric.Services.Runtime.StatelessServiceInstanceAdapter.ExecuteRunAsync(CancellationToken runAsyncCancellationToken)

System.InvalidCastException: Unable to cast COM object of type 'System.__ComObject' to interface type 'IFabricClusterManagementClient11'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{254FD06B-792A-4233-B9A5-94019A36EAE9}' failed due to the following error: No such interface supported (0x80004002 (E_NOINTERFACE)).
at System.Fabric.FabricClient.CreateNativeClient(IEnumerable`1 connectionStringsLocal)
at System.Fabric.FabricClient.<InitializeFabricClient>b__106_0()
at System.Fabric.Interop.Utility.<>c__DisplayClass28_0.<WrapNativeSyncInvoke>b__0()
at System.Fabric.Interop.Utility.WrapNativeSyncInvoke[TResult](Func`1 func, String functionTag, String functionArgs)
at System.Fabric.Interop.Utility.WrapNativeSyncInvoke(Action action, String functionTag, String functionArgs)
at System.Fabric.Interop.Utility.<>c__DisplayClass26_0.<WrapNativeSyncInvokeInMTA>b__0()
at System.Fabric.Interop.Utility.RunInMTA(Action action)
at System.Fabric.Interop.Utility.WrapNativeSyncInvokeInMTA(Action action, String functionTag)
at System.Fabric.FabricClient.InitializeFabricClient(SecurityCredentials credentialArg, FabricClientSettings newSettings, String[] hostEndpointsArg)
at System.Fabric.FabricClient..ctor()
at ANGen.Core.ServiceFabric.Deployment.DeployerContext..ctor(FabricClient fabricClient)
at ANGen.Core.ServiceFabric.Deployment.BootstrapperService.RunAsync(CancellationToken cancellationToken)
at Microsoft.ServiceFabric.Services.Runtime.StatelessServiceInstanceAdapter.ExecuteRunAsync(CancellationToken runAsyncCancellationToken)

Senior Member

@debeerisgreat 

This issue is not related to this release version. It is due to a mismatch between the native and managed binaries. This is most likely happening because your carrying the native runtime binaries with the application.

 

Established Member

Thanks @servicefabric 

My mistake as I misunderstood the way to upgrade app SDK versions vs cluster runtime version, as per https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-versions