{"id":2168,"date":"2020-10-02T21:03:33","date_gmt":"2020-10-02T19:03:33","guid":{"rendered":"https:\/\/tointegrationandbeyond.com\/blogs\/?p=2168"},"modified":"2020-10-06T13:38:39","modified_gmt":"2020-10-06T11:38:39","slug":"biztalk-server-2020-logic-apps-ibttransportcontrol-error","status":"publish","type":"post","link":"https:\/\/tointegrationandbeyond.com\/blogs\/index.php\/2020\/10\/02\/biztalk-server-2020-logic-apps-ibttransportcontrol-error\/","title":{"rendered":"BizTalk 2020 Logic App Adapter receive issue"},"content":{"rendered":"

Introduction<\/h3>\n

In this article I look into a BizTalk Server 2020 Logic App Adapter configuration issue leading to failure in the Adapter when used in receive locations, and I will show one way to resolve this issue.<\/p>\n

I had an environment with BizTalk Server 2020 Enterprise CU1, it was the first time to use the Logic App adapter in BizTalk Server 2020 as part of a hybrid integration solution with Azure Logic Apps. After conducting all the required port-level and receive location configurations, I tried to enable the Logic App receive location, however the Logic App adapter failed with the following errors:<\/p>\n

The receive location “Receive Location2” with URL “\/ReceiveWCFService\/Service1.svc” is shutting down. Details:”The Messaging Engine failed while notifying an adapter of its configuration. “.<\/span><\/p>\n

The Messaging Engine failed to add a receive location “Receive Location2” with URL “\/ReceiveWCFService\/Service1.svc” to the adapter “LogicApp”. Reason: “80070057”.<\/span><\/p>\n

The Messaging Engine encountered an error when creating the receive adapter “LogicApp”. The Assembly is: “Microsoft.BizTalk. Adapter.LogicApp. Runtime.LogicAppReceiver, Microsoft.BizTalk. Adapter.LogicApp.Runtime”. The error occurred because the component does not implement the mandatory interface “IBTTransportControl”.<\/span><\/p>\n

\"\"<\/p>\n

At first, it seemed like there is a missing interface implementation in the Logic App adapter DLLs, as indicated in the last error message.<\/p>\n

The Logic App adapter DLLs seemed to be the same as the ones in the adapter used with BizTalk 2016, I tried reflecting the DLL looking for clues and tried re-installing the Logic App adapter DLLs, however, the same issue persisted. Further, the Logic App adapter was working fine on another environment with BizTalk Server 2016 which pointed me to the right direction.<\/p>\n

The issue<\/h3>\n

The root cause of this issue was simple and can get easily overlooked; apparently the BizTalk 2020 configuration assigned the in-process host to the Logic App Adapter Handler Receive settings, instead it should have been bound to the isolated host.<\/p>\n

\"\"<\/p>\n

The error indicating the missing interface implementation now made sense, as the receive adapter is not implemented for in-process host in the first place.<\/p>\n

Resolution<\/h3>\n

The resolution is simple. First, I had to remove the adapter from all assigned send ports and receive locations in my applications, afterwards, I Removed the Logic App adapter from BizTalk and then I Added it again using using the VB scripts (RemoveLogicAppAdapter.vbs<\/strong>, AddLogicAppAdapter.vbs<\/strong>).<\/p>\n

These VB scripts ships with the Microsoft BizTalk Server Adapter for Logic Apps<\/a> installer used for BizTalk 2016, the scripts should be available in “C:\\Program Files (x86)\\Microsoft BizTalk Server\\LogicApp Adapter<\/em>“.<\/p>\n

This resolved the adapter handler configuration issue, now the Logic App Adapter Handler Receive configuration in BizTalk Server 2020 was correctly bound to the isolated host and it worked fine.<\/p>\n

\"\"<\/p>\n

One final note, I was able to reproduce the same issue on other environments with BizTalk Server 2020 Developer and Enterprise editions with and without CU1.<\/p>\n","protected":false},"excerpt":{"rendered":"

Introduction In this article I look into a BizTalk Server 2020 Logic App Adapter configuration issue leading to failure in the Adapter when used in receive locations, and I will show one way to resolve this issue. I had an environment with BizTalk Server 2020 Enterprise CU1, it was the first time to use the<\/p>\n","protected":false},"author":1,"featured_media":2182,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_uf_show_specific_survey":0,"_uf_disable_surveys":false,"footnotes":""},"categories":[6,4,1892,7],"tags":[9,1894,1893,21],"class_list":["post-2168","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-azure","category-biztalk","category-bug","category-logic-apps","tag-biztalk","tag-bug","tag-issue","tag-logic-apps"],"_links":{"self":[{"href":"https:\/\/tointegrationandbeyond.com\/blogs\/index.php\/wp-json\/wp\/v2\/posts\/2168","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/tointegrationandbeyond.com\/blogs\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/tointegrationandbeyond.com\/blogs\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/tointegrationandbeyond.com\/blogs\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/tointegrationandbeyond.com\/blogs\/index.php\/wp-json\/wp\/v2\/comments?post=2168"}],"version-history":[{"count":17,"href":"https:\/\/tointegrationandbeyond.com\/blogs\/index.php\/wp-json\/wp\/v2\/posts\/2168\/revisions"}],"predecessor-version":[{"id":2185,"href":"https:\/\/tointegrationandbeyond.com\/blogs\/index.php\/wp-json\/wp\/v2\/posts\/2168\/revisions\/2185"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/tointegrationandbeyond.com\/blogs\/index.php\/wp-json\/wp\/v2\/media\/2182"}],"wp:attachment":[{"href":"https:\/\/tointegrationandbeyond.com\/blogs\/index.php\/wp-json\/wp\/v2\/media?parent=2168"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/tointegrationandbeyond.com\/blogs\/index.php\/wp-json\/wp\/v2\/categories?post=2168"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/tointegrationandbeyond.com\/blogs\/index.php\/wp-json\/wp\/v2\/tags?post=2168"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}