Rob Potter

Hello.

This is all running on BizTalk 2004 SP1. I have an orchestration with 3 send ports, 2 using the FILE adapter and 1 using the HTTP adapter. The send ports cannot be enlisted due to the error:

Could not enlist Send Port 'DX.SendDataSourceResponseIMS'.Exception from HRESULT: 0xC0C01B22

I have another orch with a dynamic solicit-response port (adapter defined at execution-time) which I can enlist ok, and other FILE send ports that are enlisted. As all send handlers are configured against one host, I assume it cannot be a host related issue, as I have enlist the other FILE send ports ok.

I have tried enlisting through both WMI (VB script) and the BizTalk Admin Console, but to no avail. Any ideas..




Re: BizTalk R2 General BizTalk Admin Console - "unable to enlist send port 'X'. Exception from HRESULT: 0xC0C01B22"

Leonid Ganeline

Do you have the ports with the same name in your host group
Not sure that encapsulating ports with the same name into different applications is enough.
Try to rename ports (port shape names).
And look at the Port types too.





Re: BizTalk R2 General BizTalk Admin Console - "unable to enlist send port 'X'. Exception from HRESULT: 0xC0C01B22"

Rob Potter

Hello.

Both logical (orch) and physical port names are all unique across the whole system, and the port types are all uniquely named and implemented 1:1 with logical ports. It all looks ok to me.






Re: BizTalk R2 General BizTalk Admin Console - "unable to enlist send port 'X'. Exception from HRESULT: 0xC0C01B22"

Leonid Ganeline

Do your host account has read-write permissions for the folder of this port For host under wich the adapter handler works




Re: BizTalk R2 General BizTalk Admin Console - "unable to enlist send port 'X'. Exception from HRESULT: 0xC0C01B22"

Rob Potter

Ok, we got to the bottom of it... it turns out the send port had a filter on it, which was using a custom filter property (i.e. promoted from the message). Now, we've all managed to route based on promoted properties before, and I couldn't understand what the problem was with this particular promotion.

In the end, we could live without the filter property, so I removed it in the bindings file and re-imported, and now the send port enlists ok. The question still remains as to what was wrong with the promoted property, but at least we worked around the problems it was causing. Hope this helps someone else!





Re: BizTalk R2 General BizTalk Admin Console - "unable to enlist send port 'X'. Exception from HRESULT: 0xC0C01B22"

Leonid Ganeline

If port cannot be enlisted you are getting the event with description why.
Could you, please, copy here this event





Re: BizTalk R2 General BizTalk Admin Console - "unable to enlist send port 'X'. Exception from HRESULT: 0xC0C01B22"

Mick Badran - MVP

Hi Rob, great you've got a solution.

Agreed - by all means you should have no problems using promoted props etc. as filters on Send Ports/Send Port Groups and Activating Receives within Orchs.

I've had this problem when my property schema with the promoted props wasnt deployed yet - hence bts didnt know about them.

Can you confirm that the properties to filter for the Send Port in question - your Promoted Prop came up also the operation is valid

(so this has to be an exact match on the name)

Cheers,