为什么终止挂起的(不可恢复的)服务实例会返回“失败",但是却终止了 [英] Why does terminating a suspended (not resumable) service instance return Failed, yet it is terminated

查看:89
本文介绍了为什么终止挂起的(不可恢复的)服务实例会返回“失败",但是却终止了的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

为什么终止挂起的(不可恢复的)服务实例报告失败,却又终止了?

在挂起(可恢复)"实例和挂起(不可恢复)"实例(路由失败报告)上使用Microsoft.BizTalk.Operations BizTalkOperations.TerminateInstance()

检查返回Microsoft.BizTalk.Operations.CompletionStatus,已暂停的状态为成功",但已暂停的不可恢复的返回状态为失败"

但是,当我签入BizTalk Admin和/或BizTalkOperations.GetServiceInstances()时,两个实例都消失了!

那么这是怎么回事?

解决方案

非可恢复实例通常与其可恢复实例相关联.您必须先终止挂起(可恢复)实例,然后再终止其相应的挂起(不可恢复)实例,否则,由于不可恢复实例失败,因为不可恢复实例作为可恢复实例的一部分而终止.这与您在管理控制台中看到的行为相同.

Why does terminating a suspended (not resumable) service instance report failed, yet it is terminated?

Using the Microsoft.BizTalk.Operations BizTalkOperations.TerminateInstance() on a "Suspended (resumable)" and a "Suspended (not resumable)" instance (a routing failure report)

Checking the return Microsoft.BizTalk.Operations.CompletionStatus, the suspended is "Succeeded", but the suspended not resumable returns "Failed"

Yet when I check in the BizTalk Admin and/or BizTalkOperations.GetServiceInstances(), both instances have gone!

So what is happening here?

解决方案

Non Resumable instance typically is associated with its resumable instance. You must have terminated the suspended (resumable) prior to its corresponding suspended (non resumable) instance as a result you get a failure on non resumable because it got terminated as part of resumable instance. This is same behavior as you see in Admin Console.

这篇关于为什么终止挂起的(不可恢复的)服务实例会返回“失败",但是却终止了的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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