A quick tip today – I came across an error while trying to enlist one of my send ports while deploying a BizTalk application using the amazing BizTalk Deployment Framework.
“Could not enlist Send Port ‘X’. Exception from HRESULT: 0xC00CE557 (Microsoft.BizTalk.SnapIn.Framework)
This error is commonly caused by a erroneous carriage return and line feed in the send port <Filter> element of an imported binding file – In this case, the PortBindingsMaster.xml binding file in my BTDF deployment configuration.
Below is the original filter expression.
<Filter>
<?xml version=”1.0″ encoding=”utf-16″?>
<Filter xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance” xmlns:xsd=”http://www.w3.org/2001/XMLSchema”>
<Group>
<Statement Property=”BTS.MessageType” Operator=”0″ Value=”http://schemas.microsoft.com/Sql/2008/05/TypedProcedures/dbo#uspUpdateBatchStatus” />
</Group>;
<Group>
<Statement Property=”BTS.MessageType” Operator=”0″ Value=”http://schemas.microsoft.com/Sql/2008/05/TypedProcedures/dbo#uspUpdateRecordStatus” />
<Group>
</Filter>
</Filter>
Next is the fixed filter expression with the line break after the <Filter> tag removed.
<Filter><?xml version=”1.0″ encoding=”utf-16″?>
<Filter xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance” xmlns:xsd=”http://www.w3.org/2001/XMLSchema”>
<Group>
<Statement Property=”BTS.MessageType” Operator=”0″ Value=”http://schemas.microsoft.com/Sql/2008/05/TypedProcedures/dbo#uspUpdateBatchStatus“ />
</Group>;
<Group>
<Statement Property=”BTS.MessageType” Operator=”0″ Value=”http://schemas.microsoft.com/Sql/2008/05/TypedProcedures/dbo#uspUpdateRecordStatus” />
<Group>
</Filter>
</Filter>
Importing the binding file anew, or redeploying using BTDF will then update the binding in the deployed BizTalk application and allow for the successful start of the application.
5 Comments.
[…] http://blog.tallan.com/2014/07/25/could-not-enlist-send-port-hresult-0xc00ce557/ […]
Really it works..
Thanks a lott…!!!
Hi,
Great thanks, saved my day 🙂
Thanks A lot it is really helpful
Thank you 🙂