I sometimes have the pleasure to making the bridge between the Portuguese/Brazilian BizTalk community and the “international” community, and this is one of these opportunities.
On an old BizTalk Forum thread, someone found the solution to his problem in one of the BizTalk Brasil posts written by Ruth Resende and asked to help translating it into English.
📝 One-Minute Brief
When debugging BizTalk orchestrations in HAT, you may encounter the error: “This remoting proxy has no channel sink.” This typically happens when COM+ components are referenced in the project. The fix involves adding a specific
This is the original post in English:
Problem
When trying to debug an orchestration in HAT (Health and Activity Tracking), the following message appears:
This remoting proxy has no channel sink wich means either the server has no registered server channels that are listening, or this application has no suitable client channel to talk to the server.. The instance may have been completed or terminated already.
Cause
This error may occur because you may have referenced a COM+ component inside your project.
Solution
Place the following tag inside the BTSNTSvc.exe.config file:
<system.runtime.remoting>
<channelSinkProviders>
<serverProviders>
<provider id="sspi" type="Microsoft.BizTalk.XLANGs.BTXEngine.SecurityServerChannelSinkProvider, Microsoft.XLANGs.BizTalk.Engine" securityPackage="ntlm" authenticationLevel="packetPrivacy" />
</serverProviders>
</channelSinkProviders>
<application>
<channels>
<channel ref="tcp" port="0" name="">
<serverProviders>
<provider ref="sspi" />
<formatter ref="binary" typeFilterLevel="Full"/>
</serverProviders>
</channel>
</channels>
</application>
</system.runtime.remoting>
Important Note: The changes in this file are picked up when the host instance restarts. So, for this to take effect, you need to restart the BizTalk host instance

Very nice! I have not seen this thread.. Tks for the credits! =D
I am still getting the same error even after updating the “BTSNTSvc.exe.config” file. and restarted the host instance as well. still error is occuring.