部署期间Azure中的Service Fabric错误 [英] Service Fabric Error in Azure during deployment

查看:64
本文介绍了部署期间Azure中的Service Fabric错误的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

将群集部署到Azure时出现问题.一切都在本地运行,但是当部署到Azure时,尝试调用其中一项服务时出现错误.

Having issues when deploying my cluster to Azure. Everything works locally but when deploying to Azure I get an error when trying to call one of the services.

在Azure中,服务结构为 6.1.480.9494 ,并且无法升级.但是我的本地版本是6天前发布的 6.2.262.9494 .

In Azure the service fabric is 6.1.480.9494, and it cannot be upgraded. But my local version is 6.2.262.9494 that was released 6 days ago.

由于版本不同,我会收到此错误吗?

Am I getting this error due to the different versions?

无法将类型为"System .__ ComObject"的COM对象转换为接口类型为"IFabricTestManagementClient4".此操作失败,因为具有以下错误的IID为'{B96AA7D4-ACC0-4814-89DC-561B0CBB6028}'的COM组件上的QueryInterface调用由于以下错误而失败:不支持此类接口(HRESULT的异常:0x80004002(E_NOINTERFACE))

Unable to cast COM object of type 'System.__ComObject' to interface type 'IFabricTestManagementClient4'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{B96AA7D4-ACC0-4814-89DC-561B0CBB6028}' failed due to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)).

推荐答案

失败的QueryInterface调用通常是由于在较旧的运行时之上使用了较新的SDK.但是,在本地使用6.2运行时,对于.net,您可以继续引用相应的NuGet包装(3.0),它们与6.1运行时兼容.我们保持SDK库和运行时之间的向后兼容性.

A failing QueryInterface call is usually because of using a newer SDK on top of older runtime. However, using 6.2 runtime locally, for .net you can keep referencing the corresponding NuGet pakages (3.0), they are compatible with the 6.1 runtime. We keep backward compatibility between SDK libraries and runtimes.

由于召回类错误,Azure中的6.2部署已延迟:

6.2 roll-out in Azure has been delayed due to a recall class bug: https://blogs.msdn.microsoft.com/azureservicefabric/2018/04/25/update-on-the-service-fabric-6-2-release-roll-out/

这篇关于部署期间Azure中的Service Fabric错误的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆